Rapid7 InsightVM
Configure Rapid7 InsightVM integration with RAD Security for live vulnerability management.
This guide walks you through integrating Rapid7 InsightVM with RAD Security for live vulnerability management and risk assessment, allowing you to correlate vulnerability data with runtime security events.
Rapid7 InsightVM provides continuous vulnerability monitoring with live dashboards, risk-based prioritization, and automated remediation tracking.
Prerequisites
Before you begin, ensure you have:
- Admin access to Rapid7 InsightVM
- Ability to create users in your Rapid7 organization
- Access to the email account you'll use for the service user
- Access to RAD Security workspace with integration permissions
Service Account Recommended: Create a dedicated service user for this integration rather than using a personal account. This ensures continuity when team members change roles.
Step 1: Log in to Rapid7 InsightVM
Access Rapid7 Console
Log in to Rapid7 InsightVM with an administrator account
Navigate to User Management
Click the settings gear icon in the top right corner and select Users
Step 2: Create Service User with Minimum Permissions
API Keys inherit the same permissions as the user they're associated with. While you can use an existing user, it's recommended to create a dedicated service user with only the necessary permissions.
Create New User
Click the Create User button in the Users interface
Enter User Details
Fill in the user information:
- First Name (e.g., "RAD Security")
- Last Name (e.g., "Integration")
- Email Address (use a service email account)
You'll need access to this email to activate the account. In production, use a service account email (e.g., security-integrations@company.com) to ensure the integration remains active when employees change roles.
Assign Product Access
Under Manage Individual Permissions > Products tab:
- Assign the user to the InsightVM product
- Select Your Organization name
Assign Roles
Under Manage Individual Permissions > Roles tab:
Assign the following role:
- Read Only (shared)
Read Only (shared) is the minimum role required for vulnerability data access. RAD Security only reads vulnerability findings, assets, and scan status from InsightVM — it never launches scans or writes back — so no administrative or scan-capable role is required. This follows the principle of least privilege.
Create User
Click Add User to confirm creation
Log Out
Log out of your administrator account
Activate Service Account
- Open the email account associated with the new user
- Find the activation link from Rapid7
- Click the link to activate the account
- Complete the activation process and set a password
Save the activation link! Make sure to activate the account promptly. If you lose the activation email, you may need to request a new one from your administrator.
Step 3: Create Platform API Key
Log in as Service User
Log in to Rapid7 InsightVM using the service user credentials you just created
Navigate to API Keys
Click the settings gear icon in the top right corner and select API Keys
Access Organization Keys
In the left navigation, go to:
API KEY MANAGEMENT > Organization Keys
Create Platform API Key
Follow the Rapid7 documentation for creating an Organization Platform API key
- Click New Organization Key
- Enter a descriptive name (e.g., "RAD Security Integration")
- Click Generate
Copy and Save API Key
Immediately copy the API key to a secure location
This is your only chance to view the key! If you lose it, you cannot retrieve it and will need to generate a new one.
Step 4: Configure in RAD Security
Navigate to your RAD Security workspace and configure the Rapid7 InsightVM integration with the following parameters:
Required Parameters
| Parameter | Description | Example |
|---|---|---|
| Base URL | Regional base URL for Rapid7 InsightVM API (no path components) | https://us.api.insight.rapid7.com |
| Secret | Platform API key from Step 3 | your-api-key-here |
Regional URLs
Select the appropriate regional URL for your Rapid7 instance:
https://us.api.insight.rapid7.com
https://us2.api.insight.rapid7.com
https://us3.api.insight.rapid7.com
https://eu.api.insight.rapid7.com
https://ca.api.insight.rapid7.com
https://au.api.insight.rapid7.com
https://ap.api.insight.rapid7.com
Make sure to use the base URL without any path components. For example, use https://us.api.insight.rapid7.com not https://us.api.insight.rapid7.com/vm/v4.
Verify Integration
After completing the setup, verify your integration is working:
- Navigate to Data Sources > Integrations > Vulnerabilities in RAD Security
- Locate your Rapid7 InsightVM integration
- Check the connection status shows as Connected
- Verify vulnerability data is being synced
Your Rapid7 InsightVM integration is now configured! RAD Security can now import live vulnerability data and correlate it with runtime security events.
What Data is Synced
Once configured, RAD Security will sync the following data from Rapid7 InsightVM:
Use Cases
Live Vulnerability Monitoring Monitor vulnerabilities in real-time as they're discovered, with continuous updates from InsightVM.
Risk-Based Prioritization Prioritize vulnerabilities using InsightVM's real risk scores combined with RAD's runtime context.
Remediation Tracking Track remediation efforts across your environment with automated validation.
Exploit Correlation Identify when vulnerabilities are actively exploited by correlating with runtime security events.
Troubleshooting
Security Best Practices
Use Service Accounts Create a dedicated service account with a service email address to ensure continuity.
Least Privilege Access Assign only the Read Only (shared) role. RAD reads vulnerability data and never writes back, so no administrative or scan-capable role is required.
Secure Key Storage Store API keys securely in a password manager. Never commit them to version control.
Regular Key Rotation Periodically rotate API keys as part of your security hygiene practices.
Monitor API Usage Review API key usage in Rapid7 to detect any anomalous activity.
Audit User Access Regularly review service user permissions and ensure they remain appropriate.