root cause analysis
Working back from what went wrong to the underlying causes that, if changed, would stop it happening again.
In more detail
Stop at causes the organisation can change, not at a person or bad luck: "human error" is where the questions start. Ask separately how the attacker got in, how they stayed and why they went unnoticed, since each has its own causes. Five whys and fishbone diagrams are common methods.
Related terms
- five whys — A root cause method that asks "why?" about a problem, then about each answer, about five times, until it reaches a changeable cause.
- fishbone diagram — A root cause diagram that lists possible causes of a problem on branches grouped into categories, drawn like a fish skeleton.
- post-incident review — A meeting held soon after an incident to work out what happened, why, and what must change, without blaming individuals.
Taught in
- NIST SP 800-61 Incident Lifecycle & Management — Security Operations & Threat Hunting (SOC)
- Post-Incident Review & Root Cause Analysis — Security Operations & Threat Hunting (SOC)