Story
PagerDuty
EntergyHow Entergy Runs Detection Engineering on Incident Management
Entergy, a utilities organization in the United States, uses Incident Management from PagerDuty to support detection engineering for detection engineers.
Teams at Entergy moved security telemetry onto PagerDuty after local tools started to collide.
“Entergy is based in the United States and runs utilities operations at a scale where security telemetry cannot live in side channels.”
“Detection engineers were reconciling competing copies of the same work, which slowed detection engineering and hid who owned the next step.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Productivity | Handoffs in detection engineering sit in a shared queue instead of a mailbox trail |
| Risk and compliance | Fewer stalled items because security telemetry has a clear owner |
| Capability | New joiners can see how detection engineering actually runs |
Story
Entergy is based in the United States and runs utilities operations at a scale where security telemetry cannot live in side channels. Detection engineers were reconciling competing copies of the same work, which slowed detection engineering and hid who owned the next step.
The company runs detection engineering on PagerDuty, with Incident Management as the product detection engineers actually open. PagerDuty is an operations cloud for incident response, on-call, and event intelligence used by digital operations teams. For Entergy, that means detection engineers can open one workflow, see security telemetry, and let neighboring teams join without inventing a parallel stack.
Public materials confirm the companies and products. They do not always publish a single verified KPI for this pairing, so the outcome here is operational: clearer ownership, fewer stalled handoffs, and a shared record for security telemetry.
