> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Tenable Vulnerability Management as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/tenable-vulnerability-management

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Tenable Vulnerability Management connector syncs vulnerabilities, assets, scans, 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

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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 Tenable Vulnerability Management API keys to automatically pull your vulnerability and asset data.

Generate an API key pair (access key and secret key) from **Settings > My Account > API Keys** in Tenable Vulnerability Management. API keys inherit the permissions of the user who generated them: exporting requires at least a **Basic** user role (or the `VM.VM_EXPLORE.EXPORT` privilege) plus **Can View** permission on the assets you want to sync.

You'll be asked for:

-   **Access key**
-   **Secret key**
-   **Region**: choose between Tenable Cloud (cloud.tenable.com) and FedRAMP (fedcloud.tenable.com).

## 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_at` timestamp). 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](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

All Tenable Vulnerability Management tables are full refresh. Each sync replaces the contents of the table.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Access key` | password | Yes |
| `Secret key` | password | Yes |
| `Region` | select | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `vulnerabilities` | One row per vulnerability finding (asset, plugin, port, protocol). Synced via Tenable's asynchronous export API; incremental syncs pick up newly found and newly fixed findings | Incremental, Full refresh | last\_found | — |
| `assets` | One row per asset Tenable has discovered or scanned. Synced via Tenable's asynchronous export API; incremental syncs pick up assets updated since the last run | Incremental, Full refresh | updated\_at | — |
| `scans` | Scan configurations with their schedule and latest run status | Full refresh | — | — |
| `plugins` | One row per Tenable plugin with its name, family, CVEs, CVSS and VPR. Incremental syncs pick up plugins modified since the last run, but not plugins whose only change is a new VPR | Incremental, Full refresh | plugin\_modification\_date | — |
| `scan_history` | One row per run of each scan, with its status and start and end times | Full refresh | — | — |
| `compliance_findings` | One row per compliance check result (asset, check, audit file). Synced via Tenable's asynchronous export API; incremental syncs pick up findings indexed since the last run | Incremental, Full refresh | indexed\_at | — |
| `tag_values` | Asset tag values with their tag category | Full refresh | — | — |

## Troubleshooting

-   If the connection fails with an authorization error, the access key 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](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.