01
Create a read-only credential
Create the credential in PagerDuty 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 PagerDuty account and verifies incident response is wired: escalation policies exist, services are monitored, and the pager actually points at people.
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 REST API key authenticates via GET /abilities (HTTP 200).
key-connectivity
Fails if the PagerDuty account has no escalation policies, so incidents would have no on-call routing. Reads the first page of GET /escalation_policies (PagerDuty paginates by numeric offset, which the check engine cannot walk as a cursor; this is a presence check on the first page).
escalation-policies-configured
Access-review scoping check: fails if the account has no users. Reads the first page of GET /users (PagerDuty paginates by numeric offset, not a returned cursor, so this is a presence check on the first page).
users-access-review
Fails if the PagerDuty account's abilities do not include `sso`. Note: this reports the account-tier SSO capability, not per-user SSO enforcement.
sso-available
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 PagerDuty 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 PagerDuty 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.