Overview
The PagerDuty integration surfaces active incidents and on-call schedule data in Pwnbook so security teams can monitor operational incidents alongside vulnerability findings and security events — without switching tools.Prerequisites
- A PagerDuty account
- Admin or Account Owner access in PagerDuty to create API keys
- Admin or Owner access in Pwnbook
Credentials required
| Field | Description |
|---|---|
| API Key | A PagerDuty REST API key — either a General Access key or a Read-only key |
Setup
Create a PagerDuty API key
- In PagerDuty, go to Integrations → API Access Keys.
- Click Create New API Key.
- Give it a description like “Pwnbook”.
- Select Read-only API Key (Pwnbook only needs read access).
- Copy the generated key.
What’s available
| Feature | Description |
|---|---|
| Active incidents | Count of open and acknowledged incidents, broken out by urgency |
| Incident list | Filterable list of incidents with service, status, and triggered time |
| On-call schedules | Who is currently on call for each schedule |
| Services | Health summary across your PagerDuty services |
Workbench card
The PagerDuty workbench card on your Security Workbench shows:- Count of triggered (unacknowledged) and acknowledged incidents
- Current on-call responder name for your primary schedule
- A View all link to the full incident list
Incident urgency mapping
PagerDuty incidents have ahigh or low urgency. Pwnbook displays them as:
| PagerDuty urgency | Displayed as |
|---|---|
high | Critical |
low | Low |
Disconnecting
- Go to Organization Settings → Marketplace → PagerDuty.
- Click Disconnect.
- Confirm.