01
Create a read-only credential
Create the credential in Sentry with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
Read-only checks on Sentry verify who can see your stack traces: two-factor authentication enforced and single sign-on configured for the organization.
4 read-only checks, run on a schedule. Each failure becomes a finding linked to a control — every check is listed, none are “coming soon”.
Confirms the auth token authenticates and can read the organization via GET /api/0/organizations/{slug}/ (HTTP 200).
token-connectivity
Fails if the Sentry organization does not require two-factor authentication for all members. Reads `require2FA` on GET /api/0/organizations/{slug}/ and treats a missing or false value as a failure (fail-closed).
two-factor-required
Fails if the Sentry organization has no auth provider (SSO/SAML) wired up. Reads `hasAuthProvider` on GET /api/0/organizations/{slug}/ and treats a missing or false value as a failure (fail-closed).
sso-configured
Access-review scoping check: fails if the organization member roster is empty. Walks the full member list via GET /api/0/organizations/{slug}/members/ (cursor pagination through the Link header) so an access review has members to scope to.
member-access-review
Bring your current platform's test list — we'll map it against these checks, gap by gap
Setup is minutes, not a migration project — and every step stays on your side
Create the credential in Sentry with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
The first run starts right after connecting, then repeats on a schedule. Results are timestamped, so your evidence has a history, not a snapshot.
Passing results attach as evidence to the controls they support; failures become findings you triage. When the audit comes, the proof is already connected.
Open any page for its full check register.
You create and scope every credential yourself, and you can revoke it at any time. Checks only read; results and evidence are stored in Switzerland and stay exportable.
Yes. The checks authenticate with a credential you create and scope yourself, and only ever read configuration. devguard holds no write access to Sentry and remediates nothing silently.
A failed check becomes a finding linked to the control it supports, with the evidence attached. You decide the treatment — nothing pages your engineers and nothing is auto-remediated.
Checks run from Swiss infrastructure, and results and evidence are stored in Switzerland. Everything is exportable — your evidence stays yours.
20 minutes on how you run certification today. Bring your current test or control list and we'll map it against these checks — honestly, gap by gap.