Lion Cipher Lab

Run a blameless root-cause analysis after a security incident

Why it matters

The same class of incident keeps happening at most organisations because the response stops at the symptom: 'a developer leaked a key', 'the analyst clicked a phish', and everyone moves on feeling something was done. Nothing was. A real root-cause analysis (RCA) is the difference between fixing this one instance and fixing the whole class of problem so it can't recur. It is also where careers are made or lost: run it with blame and people hide the very facts you need; run it blamelessly and you get the truth. This lab teaches the thinking directly on a worked incident, so you can walk into a…

What you'll learn

Steps in this lab

  1. What a root-cause analysis actually is (and what it isn't)
  2. Where this fits: the post-incident activity phase
  3. The blameless principle — and why blame destroys the data you need
  4. Three words you must keep straight: proximate cause, contributing factor, root cause
  5. Your worked incident — read the whole timeline before you analyse it
  6. Technique 1 — run the 5 Whys, out loud, on paper
  7. The 5 Whys failure mode — why it is dangerous alone
  8. Technique 2 — build a fishbone (Ishikawa) diagram to catch what the chain missed
  9. WHEN a full RCA is worth it — and which technique fits which incident
  10. Turn findings into corrective actions — specific, assigned, verifiable
  11. Write it up — the six-section RCA report
  12. What you actually learned

Open the full interactive lab →