Safeguard Docs
Compliance ConnectorsSetup by categoryObservability

SigNoz

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

Connect SigNoz to collect observability evidence with automated compliance tests, switched on per workspace.

Step-by-step guide: Connect SigNoz.

CategoryObservability
Connect withAPI token
What a connection producesAutomated compliance tests
SigNoz's guidesignoz.io

Connect with an API token

  1. In SigNoz:

    1. In SigNoz, go to Settings › Service Accounts and click New Service Account.
    2. Enter a name (lowercase letters, numbers and hyphens, up to 50 characters) and click Create.
    3. Click the service account to open it, and in the Overview tab use the Roles dropdown to assign a role, then click Save.
    4. Switch to the Keys tab, click Add Key, enter a descriptive name, optionally set an expiration date, and click Create.
    5. Copy the key value now; it is shown only once at creation time.

    Where to find the other values:

    • Base URL: The https address of your SigNoz instance.

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

    SigNoz's public documentation does not cover every step.

    Source: signoz.io, checked 2026-10-07.

    The permissions Safeguard needs: SigNoz-Viewer, SigNoz-Admin (optional elevated grant, for the account tests). A service account key with SigNoz-Viewer verifies the connection and runs the alert and log-retention tests. The account tests (accounts linked to people, leavers, admin count) list users and roles, which only the SigNoz-Admin role can do: custom roles cannot grant user management. SigNoz-Admin also grants write, so give it as an elevated grant, or keep the key as Viewer and attest those tests.

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

    FieldWhat to enter
    Base URLRequired. Your own server: an https address reachable from the internet.
    API keyRequired. Stored encrypted and never shown again.

  3. Click Connect with token.

Frameworks

Safeguard's automated tests read SigNoz 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 testsCC6.1, CC6.2, CC6.3, CC7.27
ISO/IEC 27001Automated testsA.5.16, A.5.17, A.5.18, A.6.5, A.8.2, A.8.15, A.8.167
HIPAA Security RuleAutomated tests164.308(a)(3), 164.308(a)(4), 164.308(a)(5), 164.312(b)7
PCI DSSAutomated tests7.2.2, 7.2.4, 8.2.5, 8.6.3, 10.4.1, 10.5.17
NIST CSF 2.0Automated testsDE.CM-01, PR.AA-01, PR.AA-05, PR.PS-047

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

Sentry

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

Site24x7

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

On this page

Connect with an API tokenFrameworksRelated