Linking Intruder as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Intruder connector syncs targets, scans, scan schedules, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your Intruder API access token to pull your attack-surface and vulnerability data.
Create an access token under My account > API Access Tokens in your Intruder account. The token is shown only once, so copy it immediately. API scanning of targets requires the appropriate Intruder plan license.
You'll be asked for:
- API access token
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Some Intruder tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API access token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
targets | A system (host, IP, URL, cloud account, or container image) that Intruder scans for vulnerabilities. | Full refresh | — | — |
scans | A vulnerability scan run against your targets. | Full refresh | — | — |
scan_schedules | A recurring schedule that automatically starts scans against your targets. | Full refresh | — | — |
issues | A distinct type of security weakness Intruder has found, aggregating all of its occurrences across your targets. | Full refresh | — | — |
occurrences | A single instance of an issue found on a specific target. Fanned out per issue and tagged with its parent issue_id. | Full refresh | — | — |
fixed_occurrences | An occurrence of an issue that has since been resolved (remediated). | Full refresh | — | — |
tags | A tag used to group and filter targets. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API access token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.