Integration · Monitoring & incidents

PagerDuty integration for continuous SOC 2 & ISO 27001 compliance

CATAAM connects to PagerDuty with read-only access and runs 1 automated check against your real configuration. The results map to 2 controls across 7 frameworks, including SOC 2, ISO 27001, NIST CSF, SOC 1, APRA CPS 234, COBIT 5.

automated checks: 1
controls mapped: 2
frameworks: 7

What happens when you connect PagerDuty

Connect with read-only access
Add a read-only role, OAuth scope or API token for PagerDuty. The credential is encrypted at rest.
Discover assets
CATAAM pulls the accounts, users, repositories or devices it finds into one asset inventory.
Run 1 automated check
Every check runs against your real configuration, then keeps running on a schedule.
Map results to 2 controls
Each result lands on the controls it proves — and counts for every framework that shares them.
Store evidence and raise issues
Passing checks become audit evidence. Failures show up for the control owner and can open a Jira issue.

The 1 check CATAAM runs on PagerDuty

Each check runs against your real PagerDuty configuration and keeps running on a schedule. Check names are shown as they appear in the CATAAM platform.

PagerDuty on-call schedules active with current coverage

Controls these checks support (2)

A passing check becomes evidence for each control below, and counts for every framework that shares the control.

Control	Requirement	Frameworks
IRO-1	Incident response plan tested	SOC 2, ISO 27001, NIST CSF, SOC 1, APRA CPS 234 +1
IRO-2	Incident response policies established	SOC 2, ISO 27001, NIST CSF, SOC 1, APRA CPS 234 +2

PagerDuty integration: frequently asked questions

What does CATAAM check in PagerDuty?

CATAAM runs 1 automated check on PagerDuty: PagerDuty on-call schedules active with current coverage.

Which compliance frameworks does the PagerDuty integration support?

The PagerDuty checks map to 2 control and count toward SOC 2, ISO 27001, NIST CSF, SOC 1, APRA CPS 234, COBIT 5.

Does CATAAM need write access to PagerDuty?

No. Connectors use read-only roles, scopes or API tokens, and credentials are encrypted at rest. The only optional write anywhere in CATAAM is opening Jira issues for failed checks.

How do I connect PagerDuty to CATAAM?

Add a read-only role, OAuth scope or API token for PagerDuty in CATAAM. CATAAM then discovers your assets, runs the checks and keeps running them on a schedule, storing each result as audit evidence.