Securie for PagerDuty — critical-finding pager + incident handoff

live

Route Securie's critical maintenance findings + incident correlations to a PagerDuty service so the right on-call engineer is paged. Securie posts one incident per correlated event with severity, evidence link, deploy context, and a recommended runbook. Ack from PagerDuty mirrors back to the Securie dashboard finding row.

Updated

What it does

Posts a PagerDuty incident the moment Securie confirms a critical finding in-sandbox, or when the runtime-incident correlator (Ring 3) escalates a correlated alert chain. The incident carries the sandbox-proof URL, the affected repo/commit/file, the suggested-fix PR link if one was already drafted, and a one-line runbook pointer. Resolve on PagerDuty mirrors back to the Securie finding row. The runtime correlation path runs orchestrator-side via `crates/chat-connectors` PagerDuty submodule, so an outage in the dashboard doesn't lose pages.

When to use it

Best fit: any paid tier that runs PagerDuty for incident response. The integration is the natural pair with the Slack notifier — Slack handles team-channel visibility, PagerDuty handles on-call escalation. Particularly useful for Business+ tiers using the engineer-loop dispatcher: critical Ring-3 correlations route directly to PagerDuty without a dashboard click in between.

Limitations

Available by request. One PagerDuty service per Securie tenant at launch; multi-service routing (e.g., one service per repo) ships post-launch. The integration uses PagerDuty Events API v2; legacy v1 integration keys are not supported.

Install

  1. Create a Securie integration on the PagerDuty service you want paged (Generic Events API v2)
  2. Copy the integration key into Securie dashboard → Settings → PagerDuty
  3. Pick which severity levels page (default: critical only) and the per-tenant routing rules
  4. Send a test event from the Securie dashboard to confirm the page lands
  5. Configure escalation policy on the PagerDuty side as usual