PagerDuty
Connect PagerDuty to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect PagerDuty to collect ticketing evidence with automated compliance tests, switched on per workspace.
| Category | Ticketing |
| Connect with | API token, MCP server |
| What a connection produces | Automated compliance tests |
| PagerDuty's guide | support.pagerduty.com |
Connect with an API token
-
In PagerDuty:
- In PagerDuty, navigate to Integrations › Developer Tools › API Access Keys.
- Click Create New API Key.
- Enter a Description (for example Safeguard) and check Read-only API Key to restrict the key to GET calls, which covers reading services, escalation policies, schedules, users and incidents.
- Click Create Key and store the key; this is the only time it is displayed in full.
PagerDuty shows the secret only once, so copy it before you leave the page.
The fine-grained scopes (services.read, escalation_policies.read and so on) belong to PagerDuty scoped OAuth apps, not to REST API keys; a read-only key is the documented least-privilege key. The page does not cover how to tell the EU service region apart.
Source: support.pagerduty.com, checked 2026-10-07.
The permissions Safeguard needs:
services.read,escalation_policies.read,schedules.read,users.read,incidents.read. -
On Compliance › Connectors, open PagerDuty, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. Region (optional) — -
Click Connect with token.
Connect with the MCP server
Choose MCP server: the address https://mcp.pagerduty.com/mcp is filled in. Sign in to PagerDuty when asked. It lets Griffin AI search PagerDuty; the compliance evidence comes from the API token connection.
Frameworks
Safeguard's automated tests read PagerDuty and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | A1.1, CC6.2, CC7.4 | 6 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.5.24, A.5.26, A.6.5 | 6 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.308(a)(6) | 6 |
| PCI DSS | Automated tests | 7.2.4, 8.2.5, 12.10.1 | 6 |
| NIST CSF 2.0 | Automated tests | GV.RR-02, PR.AA-01, PR.AA-05, RS.MA-01 | 6 |
These tests are switched on per workspace by the Safeguard team.
Related
- Ticketing connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks