Skip to content
Incident Response Plan Templates

StepsChecked 16 November 2026

What is the correct order of incident response steps?

Open the free templateRead the method

What is the correct order of incident response steps?

Start with preparation, then detection and analysis, containment, eradication and recovery, and post-incident review. That order matches the CISA playbook and the SANS handbook. Preparation is not part of the incident itself; it happens before.

NIST SP 800-61 Rev. 3 says the preparation activities of Govern, Identify and Protect are broader risk management activities that support incident response, which is the Detect, Respond and Recover work.

Which steps run in parallel?

Several do. CISA says eradication and recovery actions can be executed simultaneously. It says that if new signs of compromise appear during containment, responders return to the technical analysis step to re-scope the incident. After eradication, detection and analysis continue to watch for re-entry.

Documentation and communication run through every step.

  • Evidence preservation starts at detection and continues until closure.
  • Communication starts at declaration and continues to the last update.
  • Lessons are shared as they appear, not only at the end, per NIST Rev. 3.
  • Legal notice clocks start at the point each rule defines and run in parallel with technical work.

What must be true before moving to the next step?

Use stage gates. Before eradication: all means of persistent access have been accounted for, the adversary activity is sufficiently contained and all evidence has been collected (CISA). Before recovery: the cause is removed and backups are verified. Before closing: the recovery exit criteria in the plan are met and documentation is complete (CSF outcome RC.RP-06).

The containment step page covers the first gate in detail.

What must be true before moving to the next step?
GateTest before moving on
Detect to containIncident declared, severity set, evidence preserved
Contain to eradicateNo new signs of compromise; persistence accounted for; evidence collected
Eradicate to recoverCause removed; backups verified
Recover to closeSystems verified; exit criteria met; documents complete

Sources

  1. CISA, Cybersecurity Incident & Vulnerability Response Playbooks (November 2021)
  2. SANS Institute, Incident Handler's Handbook (21 February 2012)
  3. NIST SP 800-61 Rev. 3, full text (April 2025)
  4. NIST CSF 2.0 Reference Tool download, with ISO/IEC 27001:2022 informative references

Last reviewed 16 November 2026. Each source above was read that day.