Tenable Vulnerability Management
Configure Tenable VM integration with RAD Security for comprehensive vulnerability assessment.
This guide walks you through integrating Tenable Vulnerability Management (formerly Tenable.io) with RAD Security, enabling you to import vulnerability findings and correlate them with runtime security events.
Tenable VM provides comprehensive vulnerability assessment, asset discovery, and continuous monitoring across your entire attack surface.
Prerequisites
Before you begin, ensure you have:
- Admin access to Tenable Vulnerability Management
- Ability to create users or access to an existing user account
- Access to RAD Security workspace with integration permissions
Service Account Recommended: For production environments, create a dedicated service user with an email not tied to a specific employee to ensure continuity.
Step 1: Log in to Tenable Vulnerability Management
Access Tenable Console
Log in to Tenable Vulnerability Management with an administrator account
Navigate to Access Control
Click the Settings gear icon in the top right corner and select Access Control
Step 2: Create or Select Service User
You have two options for setting up the integration:
Create Service User
In the Access Control section, create a new user account for the integration
Configure User Details
Enter the following information:
- Username (e.g., "RAD Security Integration")
- Email - Use a service email not tied to a specific employee (e.g.,
security-integrations@company.com) - Name (e.g., "RAD Security Service Account")
Using a service email ensures the integration continues working when employees change roles or leave the organization.
Assign User Role
Assign the Basic User role to the account
Basic User is the minimum role required for reading vulnerability data. This follows the principle of least privilege.
Save User
Click Save to create the user account
Switch to Service User
- Log out of your administrator account
- Log in using the newly created service user account
Verify Role
Ensure the existing user has at least Basic User role assigned
Switch User
If you're not already logged in as this user:
- Log out of your current account
- Log in with the user account you want to use for the integration
Using a personal user account is not recommended for production. If the user leaves or changes roles, the integration will break.
Step 3: Generate API Keys
Access User Profile
Click on the profile avatar in the top right corner and select My Profile
Navigate to API Keys
In the left-side navigation menu, select API KEYS
Generate New Keys
In the bottom-right corner, click the Generate button
Important: A warning will appear stating that this operation will overwrite any previously generated keys. If you're regenerating keys, make sure no other integrations are using the existing keys.
Confirm Generation
Click Continue to proceed with key generation
Copy and Save Keys
You will be provided with two keys:
- Access Key - Copy this value
- Secret Key - Copy this value
Save both keys immediately in a secure password manager or vault
Store these keys securely! You'll need both for the integration configuration. If you lose them, you'll need to generate new keys.
Step 4: Configure in RAD Security
Navigate to your RAD Security workspace and configure the Tenable VM integration with the following parameter:
Required Parameter
| Parameter | Description | Example |
|---|---|---|
| Base URL | Base URL for the Tenable Cloud API | https://cloud.tenable.com |
| API Keys | Combined access key and secret key in the format: accessKey=YOUR_ACCESS_KEY;secretKey=YOUR_SECRET_KEY | accessKey=abc123...;secretKey=xyz789... |
Formatting the Secret Parameter
The secret parameter must be formatted exactly as shown below:
accessKey=YOUR_ACCESS_KEY;secretKey=YOUR_SECRET_KEY
accessKey=1a2b3c4d5e6f7g8h9i0j1k2l3m4n5o6p;secretKey=A1B2C3D4E5F6G7H8I9J0K1L2M3N4O5P6
- There are no spaces in the format
- Use a semicolon (
;) to separate the two key-value pairs - Replace
YOUR_ACCESS_KEYwith your actual Access Key - Replace
YOUR_SECRET_KEYwith your actual Secret Key
Verify Integration
After completing the setup, verify your integration is working:
- Navigate to Data Sources > Integrations > Vulnerabilities in RAD Security
- Locate your Tenable VM integration
- Check the connection status shows as Connected
- Verify vulnerability data is being synced
Your Tenable Vulnerability Management integration is now configured! RAD Security can now import vulnerability findings and correlate them with runtime security events.
What Data is Synced
Once configured, RAD Security will sync the following data from Tenable VM:
Use Cases
Attack Surface Visibility Maintain comprehensive visibility of your attack surface with continuous vulnerability assessments.
Predictive Prioritization Use Tenable's VPR scores combined with RAD's runtime context for intelligent vulnerability prioritization.
Compliance Monitoring Track compliance posture and policy violations across your infrastructure.
Exploit Detection Correlate Tenable vulnerability data with runtime exploitation attempts detected by RAD Security.
Troubleshooting
Security Best Practices
Use Service Accounts Create dedicated service users with service email addresses for integrations, not personal accounts.
Least Privilege Access Use Basic User role for integrations. Only escalate permissions if absolutely necessary.
Secure Key Storage Store API keys in a secure password manager or secrets vault. Never commit them to version control.
Regular Key Rotation Periodically rotate API keys as part of your security hygiene. Update all integrations when rotating.
Document Key Usage Maintain documentation of which integrations use which API keys to avoid accidental key regeneration.
Monitor API Activity Review API usage in Tenable to detect anomalous activity and ensure compliance with rate limits.
Important Notes
Key Regeneration Warning: Generating new API keys will immediately invalidate the previous keys. Make sure to update all integrations using those keys to avoid service disruptions.
One User, One Set of Keys: Each Tenable user can only have one active set of API keys at a time. If you need multiple integrations, create separate service users for each.
Rate Limits: Tenable enforces API rate limits. If you have multiple integrations or heavy API usage, monitor your usage to avoid hitting limits.