How to Connect PagerDuty to SecureSpect
Link PagerDuty to SecureSpect to automate incident response evidence — on-call schedules, escalation policies, and SLA adherence data.
Ready to connect? Follow the steps in SecureSpect — the integration dialog walks you through the same process described here.
Open Integrations →Overview
SecureSpect uses a read-only PagerDuty API key to collect evidence around your incident response readiness: on-call coverage, escalation policy completeness, incident resolution times, and post-mortem documentation rates. These map to SOC 2 CC7.3 (Incident Evaluation) and CC7.4 (Incident Response).
What Gets Monitored
- On-call schedules — 24/7 coverage gaps, schedule owners
- Escalation policies — Multi-level escalation, timeout values
- Incidents — P1/P2 acknowledgement time, resolution SLA compliance
- Post-mortems — Postmortem completion rate for high-severity incidents
- Services — Services with no escalation policy assigned
Step 1 — Create a Read-Only API Key
PagerDuty API keys are account-wide. To create a read-only key:
SecureSpect Read-OnlyNote: If you use PagerDuty's newer User Token approach, create a service user with a Responder role (the minimum for read access to schedules and escalation policies).
Step 2 — Connect in SecureSpect
yourcompany.pagerduty.com).Step 3 — Review Incident Response Coverage
After the first scan, SecureSpect shows:
On-call gaps — Any hour in the next 30 days without a primary on-call assigned.
Escalation policy issues — Services with:
- Only one escalation level
- Escalation timeout over 30 minutes for P1 services
- No repeat escalation configured
Incident Response Evidence for SOC 2
SecureSpect generates a quarterly incident summary report from your PagerDuty data, including:
- Total incidents by severity
- Average time to acknowledge (MTTA)
- Average time to resolve (MTTR)
- Post-mortem completion percentage
This report can be attached directly to your SOC 2 audit evidence package.