Intruder connector
Set up the Intruder connector in Kaivo: authentication, configuration, the 4 BigQuery tables it syncs, and answers to common questions.
Intruder connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Intruder data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your data from Intruder instead of moving it.
What is the Intruder connector
Section titled “What is the Intruder connector”Sync your Intruder security data into BigQuery with Kaivo to track vulnerabilities and scan results over time.
| Category | Tech |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Intruder connector
Section titled “Getting started with the Intruder connector”- Sign up for Kaivo and create a workspace.
- Connect your Intruder account.
- Choose which tables to sync.
- Wait for the initial sync to finish.
- Query your data in BigQuery or your favourite AI or BI tool.
Authenticating Intruder
Section titled “Authenticating Intruder”Authenticate with your API Access token.
| Field | Description |
|---|---|
| API Access token | |
| Your API Access token. See here. |
|
Tables and columns synced from Intruder
Section titled “Tables and columns synced from Intruder”Kaivo syncs 4 tables from Intruder into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
issues (11 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
description |
STRING |
|
id |
INT64 |
|
occurrences |
STRING |
|
remediation |
STRING |
|
severity |
STRING |
|
snooze_reason |
STRING |
|
snooze_until |
STRING |
|
snoozed |
BOOL |
|
title |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
occurrences_issues (9 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
age |
STRING |
|
id |
INT64 |
|
port |
INT64 |
|
snooze_reason |
STRING |
|
snooze_until |
STRING |
|
snoozed |
BOOL |
|
target |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
scans (5 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
created_at |
STRING |
|
id |
INT64 |
|
status |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
targets (4 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
address |
STRING |
|
id |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: targets__tags
Section titled “Subtable: targets__tags”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Intruder sync works
Section titled “How the Intruder sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Intruder supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.
Frequently asked questions
Section titled “Frequently asked questions”How long does the initial sync take for Intruder?
Section titled “How long does the initial sync take for Intruder?”It depends on how much history is in your Intruder account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.
Can I sync only some tables or columns?
Section titled “Can I sync only some tables or columns?”Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.
What happens when Intruder’s schema changes?
Section titled “What happens when Intruder’s schema changes?”New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Intruder, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.
How do I handle GDPR or data deletion requests?
Section titled “How do I handle GDPR or data deletion requests?”Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Intruder instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Intruder connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Intruder data
Section titled “Common use cases for Intruder data”Vulnerability trends
Section titled “Vulnerability trends”Use issues and occurrences_issues to track open vulnerabilities over time.
Scan coverage
Section titled “Scan coverage”Join scans with targets to confirm your assets are being scanned.
Remediation tracking
Section titled “Remediation tracking”Use issues to monitor how quickly vulnerabilities get fixed.
Use Intruder data in your AI and BI tools
Section titled “Use Intruder data in your AI and BI tools”Once Intruder data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Intruder data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “Data Studio”Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →
Tableau
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for Intruder connector pricing and plan details.