Rapid7 InsightCloudSec
Connect Rapid7 InsightCloudSec to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Rapid7 InsightCloudSec connection as cspm evidence. Automated collection is not available for this provider yet.
| Category | CSPM |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Rapid7 InsightCloudSec:
- Sign in to InsightCloudSec as a Domain Admin or Organization Admin.
- Go to Administration › User Management › API Keys and generate a key (alternatively, generate a personal API key from your user profile).
- Copy the key and paste it into Safeguard's API token / Personal access token field; Safeguard sends it in the
Api-Keyheader. - To use a Basic (non-admin) user, an admin must grant that user the API Key Generation Allowed permission before they can generate a key from their user profile.
Where to find the other values:
- Base URL (optional): The address of your InsightCloudSec console, for example
https://cloudsec.insight.rapid7.com; some deployments still use a DivvyCloud-based URL such ashttps://<customer-name>.customer.divvycloud.com.
Rapid7 InsightCloudSec's public documentation does not cover every step.
An API-only user can also be created through the API (/v2/public/user/create_api_only_user). Not sourced: button labels on the API Keys tab, a documented read-only role for the key, whether the key is shown only once, and where an organization identifier appears.
Source: docs.rapid7.com, checked 2026-10-07.
-
On Compliance › Connectors, open Rapid7 InsightCloudSec, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
Rapid7 InsightCloudSec publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC7.1 | 1 |
| ISO/IEC 27001 | Attestation | A.8.8 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(1) | 1 |
| PCI DSS | Attestation | 6.3.3, 11.3.1 | 1 |
| NIST CSF 2.0 | Attestation | ID.RA-01 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- CSPM 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