← All integrations
PagerDuty
Live integration

PagerDuty

Monitoring · API key / service-account token · Daily

Read-only REST API key. Pulls escalation-policy coverage across services and live on-call rotation presence — the platform's first automated incident-response (IR-4/IR-6) evidence.

Authentication
API key / service-account token
Sync cadence
Daily
Stale threshold
Every 2 days
Category
Monitoring

Evidence this connector produces

Every sync writes typed evidence rows linked to the controls below. Evidence is immutable once attached to an approved assessment, fingerprinted for de-dup, and surfaced in the control coverage calculation on your dashboard.

NIST 800-53 IR-4IR-6

How to connect

Create a read-only REST API key in PagerDuty and paste it here.

  1. 1
    Create the API key

    PagerDuty → Integrations → API Access Keys → Create New API Key. Check 'Read-only API key'.

  2. 2
    Copy the key

    The key is shown once — copy it and paste it into the form.

Security model

Every connector ships behind the same auditor-grade primitives — not just RBAC config, but architectural enforcement.

Credentials KMS-encrypted at rest

Tokens, client secrets, and service-account keys are encrypted under a per-tenant AWS KMS data key. The plaintext is never persisted, never logged, and never leaves the FastAPI process boundary.

Tenant-isolated by architecture

Every Connection, ConnectorRun, and emitted Evidence row carries an organization ObjectId. The scheduler never iterates without an org-scoped filter; cross-tenant evidence bleed is impossible at the data layer.

Audit log on every action

Connect, sync, sync-failure, re-auth, and revoke each write a row to the immutable AuditLog. The full lifecycle is reconstructable for any examiner.

Soft-delete on revoke

Revoking a connection sets deletedAt and clears the encrypted credential blob, but the historical evidence + sync log stays queryable for the retention window. Auditors can still trace what was attested when.

Stale-evidence degradation

If this connector hasn't synced in Every 2 days, control coverage degrades automatically and an alert fires. Auditors don't trust stale evidence — neither do we.

Least-privilege scopes only

We request the minimum read-only scopes needed for the listed evidence. No write scopes, no admin scopes, no scopes outside the documented set.

Ready to connect PagerDuty?

Connect from Settings → Integrations — typically under 5 minutes. Or talk to us first.

Request a demoSign in to connect