Sentry
Connect Sentry to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Sentry to collect observability evidence with automated compliance tests, switched on per workspace.
| Category | Observability |
| Connect with | API token, MCP server |
| What a connection produces | Automated compliance tests |
| Sentry's guide | docs.sentry.io |
Connect with an API token
-
In Sentry:
- In sentry.io, open the Account dropdown in the top left and go to the Personal Tokens page.
- Create a new personal token and select only read scopes in the scope selection.
- Copy the token. Personal tokens can currently be viewed in the UI after creation.
Where to find the other values:
- Organization: Your organization slug, as it appears in your Sentry address; not described on the fetched page.
- Region (optional): Not described on the fetched page (Sentry's US and DE regions).
Sentry's public documentation does not cover every step.
Source: docs.sentry.io, checked 2026-10-07.
The permissions Safeguard needs:
org:read,project:read,alerts:read,member:read. Safeguard's compliance tests for Sentry need the credential on the API token tab: an OAuth connection cannot read everything they check. -
On Compliance › Connectors, open Sentry, click Connect, choose API token and fill in:
Field What to enter Auth token Required. Stored encrypted and never shown again. Organization Required. Region (optional) — -
Click Connect with token.
Connect with the MCP server
Choose MCP server: the address https://mcp.sentry.dev/mcp is filled in. Sign in to Sentry when asked. It lets Griffin AI search Sentry; the compliance evidence comes from the API token connection.
Frameworks
Safeguard's automated tests read Sentry 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.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | C1.1, CC6.1, CC6.2, CC6.3, CC7.2 | 6 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2, A.8.5, A.8.11, A.8.12, A.8.16 | 6 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1), 164.308(a)(3), 164.308(a)(4), 164.312(a)(1), 164.312(d) | 6 |
| PCI DSS | Automated tests | 3.5.1, 7.2.2, 7.2.4, 8.2.5, 8.4.2 | 5 |
| NIST CSF 2.0 | Automated tests | DE.CM-09, PR.AA-01, PR.AA-03, PR.AA-05, PR.DS-01 | 6 |
These tests are switched on per workspace by the Safeguard team.
Related
- Observability 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