Lion Cipher Lab

Write an incident response plan

Why it matters

Sooner or later something goes wrong -- an account gets phished, a laptop gets encrypted and held for ransom, a strange login appears from another country. The moment that happens is the worst possible time to be figuring out who is in charge, what to unplug, who to call, and in what order. An incident response plan is the short written document that decides all of that in advance, so that when the alarm goes off people follow a rehearsed script instead of panicking. It is one of the highest-leverage documents in security because incidents are not a maybe -- they are a when -- and the…

What you'll learn

Steps in this lab

  1. What an incident is, what IR is, and why this plan exists
  2. The lifecycle -- the four phases every plan is built on
  3. Open a document and lay out the plan skeleton
  4. Preparation, part 1 -- roles and responsibilities
  5. Preparation, part 2 -- severity levels and escalation
  6. Preparation, part 3 -- the contact tree
  7. Detection & analysis -- noticing, then confirming
  8. Containment, eradication, and recovery -- the three that get confused
  9. Post-incident activity -- the review that stops a repeat
  10. Playbook 1 -- phishing (define it, then the steps)
  11. Playbook 2 -- ransomware (define it, then the steps)
  12. Assemble the one plan -- fill in the template
  13. What you built, and the mindset to keep

Open the full interactive lab →