01
Create a read-only credential
Create the credential in Buildkite 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 access-review checks for Buildkite: the token connects, the number of organization admins stays within the bound you set, and SSO is enforced for every member.
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 access token authenticates and resolves to a valid user identity.
token-connectivity
Access-review check: fails if the number of organization members with the `admin` role exceeds the approved maximum, flagging over-broad administrative access.
org-admin-count-limited
Fails if any organization member does not log in via SSO (`sso_mode` other than `required`). Also fails if no members are returned, to avoid a vacuous pass.
sso-enforced
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 Buildkite 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 Buildkite 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.