Safeguard Docs
Compliance ConnectorsSetup by categoryCompliance As Code

Strike Graph

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

Record your Strike Graph connection as compliance as code evidence. Automated collection is not available for this provider yet.

CategoryCompliance As Code
Connect withAPI token
What a connection producesConnection record

Connect with an API token

  1. In Strike Graph:

    1. In Strike Graph, open the Integration Manager and find the Public Evidence API card.
    2. Open the card and click Connect to generate credentials: Client ID, Client Secret, Auth0 Domain and API Audience (typically urn:sg:public-api).
    3. Store the Client Secret right away; it cannot be retrieved again.
    4. Exchange the credentials for an access token with a POST to https://login.grc.strikegraph.com/oauth/token (client credentials), and paste the access token into API token / Personal access token.

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

    Strike Graph's public documentation does not cover every step.

    Strike Graph's public API is the Evidence API, aimed at posting evidence; no read-only option is documented. Access tokens are valid for 2 hours by default, so a pasted token expires quickly; the connector would need the client credentials to refresh. Access to the Evidence API depends on the subscription plan (ask your Customer Success Manager).

    Source: help.strikegraph.com, checked 2026-10-07.

  2. On Compliance › Connectors, open Strike Graph, 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

No automated compliance test reads Strike Graph yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

On this page