Safeguard Docs
Compliance ConnectorsSetup by categoryVulnerability Scanning

Detectify

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

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

CategoryVulnerability Scanning
Connect withAPI token
What a connection producesAutomated compliance tests
Detectify's guidesupport.detectify.com

Connect with an API token

  1. In Detectify:

    1. In Detectify, as a team admin, go to Team settings in the user menu, then open the API-keys tab.
    2. Click Generate API key (if keys already exist, the button is in the upper right corner).
    3. In the modal, optionally enter a name and description for the key; the key is then generated. Copy it.
    4. Select the key, click the actions button and select Edit (confirm the edit).
    5. Under API Setting Permissions, enable only the read permissions Safeguard needs and save. Leave message signature disabled unless Safeguard is configured with the secret key.

    Detectify's public documentation does not cover every step.

    Source: support.detectify.com, developer.detectify.com, checked 2026-10-07.

    The permissions Safeguard needs: vulnerabilities: read.

  2. On Compliance › Connectors, open Detectify, 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 Detectify 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.13
ISO/IEC 27001Automated testsA.8.83
HIPAA Security RuleAutomated tests164.308(a)(1)3
PCI DSSAutomated tests6.3.3, 11.3.13
NIST CSF 2.0Automated testsID.RA-01, ID.RA-063

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

On this page