Tenable
Tenable Vulnerability Management connects your device inventory and vulnerability findings into Navigator.
At a glance
| Data provided | Devices, Vulnerabilities |
| Authentication | API key pair (Access Key + Secret Key) |
| Where to configure | Connectors → Add a Connector → Tenable |
Required permissions
| Credential | Required access |
|---|---|
| API Access Key + Secret Key | Generated by a Tenable.io user with read access to Assets and Vulnerability Management (exports). No write access is needed. Navigator only reads data from Tenable; it never modifies anything in your Tenable instance. |
Setup
- In Tenable.io, go to Settings → My Account → API Keys (or generate a key pair for a dedicated service account, recommended over using a personal account’s key).
- Generate a new Access Key and Secret Key pair.
- In Navigator, go to Connectors → Add a Connector → Tenable.
- Enter the Access Key and Secret Key.
- Save. Navigator validates the credentials and enqueues a first sync immediately.
Vendor documentation
Tenable’s own instructions for this step: Generate an API Key (Tenable Vulnerability Management documentation).
What data this connector provides
- Devices: via Tenable’s asset inventory. Tenable reports OS information as a single free-text string, so Navigator can determine the general OS platform from it but not always a precise version breakdown the way some other connectors can.
- Vulnerabilities: via Tenable’s vulnerability export workflow. Tenable reports its own per-asset “has agent” signal directly, which Navigator uses as-is.
Known limitations
- Tenable’s OS field doesn’t reliably distinguish OS major version/build in every case, since it’s reported as one descriptive string rather than structured fields.