Rapid7 InsightVM
Connect Rapid7 InsightVM to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Rapid7 InsightVM to collect vulnerability scanning evidence with automated compliance tests.
| Category | Vulnerability Scanning |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Rapid7 InsightVM's guide | docs.rapid7.com |
Connect with an API token
-
In Rapid7 InsightVM:
- Sign in to the Rapid7 Command Platform as a user whose role gives read-only access to InsightVM (a user key inherits the permissions of its owner).
- From Command Home, go to Administration › User API Keys.
- Select Generate New User Key, select the organization and provide a name for the key, then select Save.
- Copy the key from the window that opens (you won't be able to view it again after closing the window), then select Done.
Where to find the other values:
- Region: Open InsightVM (or any Rapid7 product) and read the region code from the URL: it is the first two letters of the domain name (for example us in us.idr.insight.rapid7.com). The API endpoint is https://<REGION_CODE>.api.insight.rapid7.com.
Rapid7 InsightVM shows the secret only once, so copy it before you leave the page.
Avoid an Organization key: Rapid7 describes it as a super key that can do everything across all products (Administration › Administrator API Keys › Generate New Organization Key, platform admins only). A user key's access is whatever its owner can do at the time of use, so read-only access depends on that user's InsightVM role; the role name was not on the fetched pages.
Source: docs.rapid7.com, docs.rapid7.com, checked 2026-10-07.
The permissions Safeguard needs:
InsightVM read-only. -
On Compliance › Connectors, open Rapid7 InsightVM, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. Region Required. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Rapid7 InsightVM and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC7.1 | 4 |
| ISO/IEC 27001 | Automated tests | A.8.8 | 4 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1) | 4 |
| PCI DSS | Automated tests | 6.3.3, 11.3.1 | 4 |
| NIST CSF 2.0 | Automated tests | ID.RA-01, ID.RA-06 | 4 |
Related
- Vulnerability Scanning connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks