# What is the correct order of incident response steps?

Steps, read 16 November 2026

**The short answer.** The order is prepare, detect and analyze, contain, eradicate, recover, then learn, but the steps overlap. CISA says many activities are iterative, eradication and recovery can run at the same time, and new findings send responders back to analysis. This page, read on 16 November 2026, shows what runs in parallel.

## 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](/steps/containment-step/) page covers the first gate in detail.

| Gate | Test before moving on |
| --- | --- |
| Detect to contain | Incident declared, severity set, evidence preserved |
| Contain to eradicate | No new signs of compromise; persistence accounted for; evidence collected |
| Eradicate to recover | Cause removed; backups verified |
| Recover to close | Systems verified; exit criteria met; documents complete |

What must be true before moving to the next step?

## Related pages

- [Incident response steps: the order and who does what](/steps/)
- [Free incident response plan template](/)
- [Incident response plan in 6 steps: the SANS model](/steps/incident-response-plan-6-steps/)
- [Incident response steps: NIST vs SANS compared](/steps/incident-response-steps-nist-vs-sans/)
- [The containment step of incident response](/steps/containment-step/)
- [Incident response plan: what it contains and how to build one](/plans/)
- [Incident response playbook: what it is and how to build a library](/playbooks/)

## Sources

- CISA, Cybersecurity Incident & Vulnerability Response Playbooks (November 2021): https://www.cisa.gov/sites/default/files/2024-08/Federal_Government_Cybersecurity_Incident_and_Vulnerability_Response_Playbooks_508C.pdf (read 16 November 2026)
- SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026)
- NIST SP 800-61 Rev. 3, full text (April 2025): https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026)
- NIST CSF 2.0 Reference Tool download, with ISO/IEC 27001:2022 informative references: https://csrc.nist.gov/extensions/nudp/services/json/csf/download?olirids=all (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/steps/correct-order-of-incident-response-steps/
