Safeguard Docs
Compliance ConnectorsSetup by categoryVulnerability Scanning

Bright Security

Connect Bright Security to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Connect Bright Security to collect vulnerability scanning evidence with automated compliance tests, switched on per workspace.

CategoryVulnerability Scanning
Connect withAPI token
What a connection producesAutomated compliance tests
Bright Security's guidedocs.brightsec.com

Connect with an API token

  1. In Bright Security:

    1. In Bright, open the organization Settings page.
    2. Go to the API Keys tab and click + Create API key.
    3. Assign the API key a name and select the scopes projects:read and scans:read (read actions only). Optionally set an expiration date.
    4. Click Create.
    5. Copy the generated key now. As soon as you navigate away from the popup you cannot restore it.

    Bright Security shows the secret only once, so copy it before you leave the page.

    Source: docs.brightsec.com, docs.brightsec.com, docs.brightsec.com, checked 2026-10-07.

    The permissions Safeguard needs: projects:read, scans:read.

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

    FieldWhat to enter
    API keyRequired. Stored encrypted and never shown again.
  3. Click Connect with token.

Frameworks

Safeguard's automated tests read Bright Security 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.

FrameworkEvidenceControlsTests
SOC2Automated testsCC7.14
ISO/IEC 27001Automated testsA.8.84
HIPAA Security RuleAutomated tests164.308(a)(1)4
PCI DSSAutomated tests6.3.3, 11.3.14
NIST CSF 2.0Automated testsID.RA-01, ID.RA-064

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

On this page