DatriseAI-first ETL

Intruder to Spotfire Integration

AI-first ETL from Intruder into Spotfire. Governed entities, incremental sync, typed landing tables.

How Datrise loads Intruder into Spotfire

Datrise syncs Intruder's scans, issues, targets, severities, occurrences, and remediation statuses into Spotfire as warehouse tables or in-memory data for Spotfire analyses. Flexible or custom fields land in flattened columns for visualizations, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables or in-memory data, so re-runs update only what changed. Date-partitioned facts. Spotfire can load data in-memory, so Datrise keeps the backing tables incremental so analyses refresh without full reloads.

Ideal for interactive analytical visualization and data science.

Endpoints

Intruder: Continuous vulnerability scanning for internet assets.

Spotfire: Visual analytics platform for interactive dashboards and data science workflows.

How Intruder entities map to Spotfire

Intruder entitySpotfire objectNotes
scansintruder_scansid PK · custom fields → flattened columns for visualizations
issuesintruder_issuesid PK · linked to intruder_scans
targetsintruder_targetsid PK · linked to intruder_scans
severitiesintruder_severitiesid PK · linked to intruder_scans

FAQ

How does Datrise handle Intruder's custom fields in Spotfire?

Flexible values are stored as flattened columns for visualizations, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Spotfire types.

How does the Intruder to Spotfire sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables or in-memory data.

Related pipelines

Early access

Connect Intruder to Spotfire the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.