Safeguard Docs
Compliance ConnectorsSetup by categoryCSPM

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.

CategoryCSPM
Connect withAPI token
What a connection producesConnection record

Connect with an API token

  1. In Rapid7 InsightCloudSec:

    1. Sign in to InsightCloudSec as a Domain Admin or Organization Admin.
    2. Go to Administration › User Management › API Keys and generate a key (alternatively, generate a personal API key from your user profile).
    3. Copy the key and paste it into Safeguard's API token / Personal access token field; Safeguard sends it in the Api-Key header.
    4. 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 as https://<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.

  2. On Compliance › Connectors, open Rapid7 InsightCloudSec, click Connect, choose API token and fill in:

    FieldWhat to enter
    API token / Personal access tokenRequired. Stored encrypted and never shown again.
    Base URL (optional)—
    Account / Org / Workspace (optional)—
  3. 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.

FrameworkEvidenceControlsTests
SOC2AttestationCC7.11
ISO/IEC 27001AttestationA.8.81
HIPAA Security RuleAttestation164.308(a)(1)1
PCI DSSAttestation6.3.3, 11.3.11
NIST CSF 2.0AttestationID.RA-011

These tests are switched on per workspace by the Safeguard team.

On this page