Course contentsShow
← Security
Lesson 2422 of 3,05246. Incident ResponseFree lesson

Root Cause Analysis Methodologies

Apply structured approaches like Five Whys and Fishbone diagrams to identify the true origin of security incidents.

Root Cause Analysis Methodologies

What you'll learn: How to use structured frameworks like Five Whys and Fishbone diagrams to trace security incidents back to their true underlying cause.

Why Root Cause Analysis Matters

After constructing timelines and identifying pivot points in an investigation, you need to answer the hardest question: why did this incident happen? Without understanding the root cause, you'll patch symptoms while leaving the door open for recurrence. Root cause analysis (RCA) transforms incident data into actionable prevention.

The Five Whys Technique

This iterative interrogation method asks "Why?" five times (or until you reach bedrock):

Example: Ransomware encrypted production servers.

  1. Why? → Attacker had domain admin credentials
  2. Why? → Credentials were harvested from a compromised workstation
  3. Why? → Workstation ran unpatched software with known exploit
  4. Why? → Patch management system excluded user workstations
  5. Why? → Policy only required server patching due to resource constraints

Root cause: Incomplete patch management scope driven by resource prioritization decisions.

Fishbone (Ishikawa) Diagram

This visual method categorizes contributing factors across branches:

  • People: Inadequate security awareness training
  • Process: No MFA enforcement policy
  • Technology: EDR not deployed to all endpoints
  • Environment: Flat network topology enabling lateral movement

Each branch traces back to the "head" (the incident), revealing multiple contributing factors. Unlike Five Whys, Fishbone acknowledges that security incidents rarely have a single root cause—they're often confluence events.

Applying Both Methods

Use Five Whys for linear causal chains and Fishbone when multiple systems, people, and processes contributed. Both transform your timeline artifacts and IOCs into systemic improvements rather than one-off fixes.

Key Takeaway: Root cause analysis methodologies like Five Whys and Fishbone diagrams systematically trace security incidents beyond immediate triggers to underlying organizational, technical, or process failures that enabled the attack.