Semgrep

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

Connect with an API token

1. In Semgrep:

   1. Sign in to Semgrep AppSec Platform (https://semgrep.dev/login) as an admin.
   2. Go to Settings › Tokens › API tokens (https://semgrep.dev/orgs/-/settings/tokens/api).
   3. Click Create new token.
   4. Copy the Secrets name and the Secrets value. The Secrets value is your token and is only shown at this time.
   5. Under Token scopes, select Read-only (read APIs only; a subset of Web API). Select Web API only if Safeguard needs an endpoint the read-only scope does not cover.
   6. Optionally change the Name of the token, then click Save.

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

   Source: docs.semgrep.dev, docs.semgrep.dev, checked 2026-10-07.

   The permissions Safeguard needs: Web API. Safeguard's compliance tests for Semgrep need the credential on the API token tab: an OAuth connection cannot read everything they check.

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

   Field	What to enter
   API token	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

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

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

Related

• Vulnerability Scanning connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks