01
Create a read-only credential
Create the credential in Opsgenie 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 Opsgenie verify your on-call reality: the key connects, schedules exist, and escalation paths end at a human, evidence for the incident-response control.
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 API key authenticates via GET /v2/users (HTTP 200).
key-connectivity
Access-review scoping check: fails if the account has no users. Reads the first page of GET /v2/users (Opsgenie paginates by numeric offset / a full next-URL, neither of which the check engine can walk as a cursor, so this is a presence check on the first page).
users-access-review
Fails if the Opsgenie account has no on-call schedules, so there is no defined on-call rotation. Reads GET /v2/schedules.
schedules-configured
Fails if the Opsgenie account has no heartbeats, or if none of them is enabled. An active heartbeat is a dead-man's-switch: it alerts when an expected periodic signal stops arriving. Reads GET /v2/heartbeats.
heartbeat-active
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 Opsgenie 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 Opsgenie 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.