01
Create a read-only credential
Create the credential in Snyk 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.
devguard reads your Snyk organization and turns scanning posture into evidence: no open critical or high vulnerabilities, and the projects you ship are actually monitored.
3 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 API token authenticates against the Snyk REST API. A 401 or 403 is reported as an invalid or unauthorized token rather than a silent error.
token-connectivity
Fails if the Snyk organization has any open issue at critical or high effective severity. The request is filtered to open critical/high project issues, so any single matching issue is returned on the first page — a single read is sufficient and cannot vacuously pass. Ignored and resolved issues are excluded by the `status=open` filter.
no-open-critical-high-issues
Coverage guard: fails if the Snyk organization has no projects under monitoring, which would let the no-open-vulnerabilities check pass vacuously. This is an existence check — any project appears on the first page — so a single read is sufficient.
projects-monitored
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 Snyk 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 Snyk 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.