Tenable Vulnerability Management
Outline
Introduction
The SAFE integration with Tenable Vulnerability Management (VM) ingests assets, associated vulnerabilities, software entities, and controls data, as well as operational or business data.
What SAFE Imports from Tenable VM
| Data | Details |
|---|---|
| Assets | • Device information, including hostnames, IPs, and MAC addresses • Operating system details • Asset metadata (tags, first/last seen dates) |
| Vulnerabilities | • CVE information • Software vulnerabilities • Custom (non-CVE) vulnerabilities • Severity and status information |
| Compliance Findings | • Compliance benchmark data • Control status and details • Policy information |
How does SAFE process Tenable VM data?
SAFE uses AI to aggregate, normalise, and deduplicate the ingested data from Tenable, along with information from your existing IT and cybersecurity tools. This creates a unified view of your entire asset inventory, including vulnerabilities and their operational and business context.
SAFE's AI models analyse this data to deliver insights such as:
- Identify areas lacking security coverage.
- Provide detailed ranking and scoring of vulnerabilities based on risk.
- Assess risk at the asset, group, or enterprise level.
Prerequisites and Permissions
To set up the SAFE connector, you must first create Tenable API credentials with the necessary permissions. These credentials are required to complete the configuration process.
Required permissions:
- Service account in Tenable VM with the configuration scopes required to read asset datasets, vulnerabilities details, and compliance configurations.
Generate Connection Details
To connect Tenable VM to SAFE, you will need to generate your Access Key and Secret Key from the Tenable platform settings.
- Log in to your Tenable Vulnerability Management portal.
- Navigate to Settings > Users or Service Accounts.
- Select your integration user or create a new service account dedicated to SAFE.
- Generate API Keys. Copy and securely store both the Access Key and Secret Key for input during configuration in SAFE.
Configure Tenable VM in SAFE
- Log in to SAFE as an admin and navigate to Integrations on the left navigation.
- Click on the + icon on the top right of the page.
- Click Tenable VM from the list.
- Enter a unique Integration Name.
- Enter the API Base URL, Access Key, and Secret Key obtained from your configuration step.
- Enter the Auto Sync frequency in number of days.
- Click Test Connection.
- Once the connection is verified, click Save.
- Once the integration is saved, click on Sync Now to trigger an on-demand sync.
API Details
| Export | Endpoints |
|---|---|
| Asset Export | /assets/export, /assets/export/{export_uuid}/status, /assets/export/{export_uuid}/chunks/{chunk_id} |
| Vulnerability Export | /vulns/export, /vulns/export/{export_uuid}/status, /vulns/export/{export_uuid}/chunks/{chunk_id} |
| Compliance Export | /compliance/export, /compliance/export/{export_uuid}/status, /compliance/export/{export_uuid}/chunks/{chunk_id} |
FAQs
Q: How frequently does SAFE sync data from Tenable VM?
A: SAFE syncs data based on the auto sync frequency configured for the Tenable VM connector.
Q: Does SAFE support both CVE and non-CVE findings from Tenable VM?
A: Yes. SAFE ingests both CVE-based and non-CVE vulnerability findings from Tenable VM.
Q: What happens if API rate limits are exceeded?
A: SAFE automatically handles API rate limits by pausing requests and retrying them after the required wait period.
Q: How does SAFE handle duplicate assets or findings?
A: SAFE deduplicates assets and findings using unique identifiers.
Q: Can SAFE re-ingest historical data?
A: Yes. SAFE can re-ingest historical data by re-running the integration.
API reference documentation
To learn more about the Tenable Vulnerability Management API, see the references listed below:
To check sync status and errors for this integration, see Integration History.
Did this article help?
Let us know by leaving a star rating at the top of this article.