Safeguard
Connect Safeguard to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Safeguard connection as vulnerability scanning evidence. Automated collection is not available for this provider yet.
| Category | Vulnerability Scanning |
| Connect with | API token, MCP server |
| What a connection produces | Connection record |
Connect with an API token
-
In Safeguard:
- Sign in to the Safeguard tenant you want to connect as a user with read-only access (a user API key inherits that user's role).
- Go to Settings › API Keys and generate a user API key. There is no CLI command for this yet.
- Copy the key.
Where to find the other values:
- Account / Org / Workspace (optional): The Safeguard organization (the top-level tenant boundary) the key's user belongs to.
Safeguard's public documentation does not cover every step.
Source: docs.safeguard.sh, checked 2026-10-07.
-
On Compliance › Connectors, open Safeguard, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Connect with the MCP server
Choose MCP server: the address https://mcp.safeguard.sh/mcp is filled in. Sign in to Safeguard when asked. It lets Griffin AI search Safeguard.
Frameworks
No automated compliance test reads Safeguard yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
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