PagerDuty Incidents
Connect PagerDuty Incidents to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your PagerDuty Incidents connection as ticketing evidence. Automated collection is not available for this provider yet.
| Category | Ticketing |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In PagerDuty Incidents:
- 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.
- Click Create Key and store the key; this is the only time it is displayed in full.
- (Alternative: a user token from User Icon › My Profile › User Settings, under API Access click Create API User Token, which acts with that user's permissions.)
PagerDuty Incidents shows the secret only once, so copy it before you leave the page.
The page does not cover the EU service region or a base URL; no account or workspace ID is needed for PagerDuty REST API keys.
Source: support.pagerduty.com, checked 2026-10-07.
-
On Compliance › Connectors, open PagerDuty Incidents, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
No automated compliance test reads PagerDuty Incidents yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
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