# Incident response steps: the order and who does what

Steps, read 16 November 2026

**The short answer.** Incident response runs in five steps: prepare, detect and analyze, contain, eradicate and recover, then learn. CISA's playbook uses this order, which follows NIST SP 800-61 Rev. 2. This page, read on 16 November 2026, shows what each step must produce and who owns it, and links to the six-step and NIST views.

## What are the steps in incident response?

The steps are prepare, detect and analyze, contain, eradicate and recover, and learn. CISA's Cybersecurity Incident & Vulnerability Response Playbooks (November 2021) organize the incident response process into preparation, detection and analysis, containment, eradication and recovery, and post-incident activities, with coordination across all of them.

The same playbook says many activities are iterative and may occur continuously until the incident is closed out. The steps are therefore a guide to emphasis, not a strict line.

| Step | Must produce | Owner in the template |
| --- | --- | --- |
| 1 Prepare | Approved plan, named roles, contacts, tested backups | Executive sponsor, incident lead |
| 2 Detect and analyze | A declared incident with a scope and a severity | Incident lead, technical lead |
| 3 Contain | Spread stopped; evidence preserved | Technical lead |
| 4 Eradicate and recover | Threat removed; systems restored and verified | Technical lead, system owners |
| 5 Learn | Report, root cause and dated actions | Incident lead |

What are the steps in incident response?

## What happens in each step?

Step 1, prepare. Document policy and plan, set up logging and detection, train responders and users, and agree communication channels. CISA lists establishing staffing plans and means of collecting forensic evidence.

Step 2, detect and analyze. Declare the incident, determine scope, and collect and preserve data. CISA tells federal agencies to report every incident to CISA; for others the local legal duty applies.

Step 3, contain. Isolate affected systems, block malicious access and change credentials where compromise is suspected, while keeping evidence.

Step 4, eradicate and recover. Remove the threat, rebuild or reimage, then restore and test systems and watch for re-entry.

Step 5, learn. Hold a review, finalize reports, adjust detections and update the plan.

## Which models use a different count of steps?

NIST SP 800-61 Rev. 3 (April 2025) now ties incident response to the six CSF 2.0 Functions. The SANS Incident Handler's Handbook uses six phases. The [NIST versus SANS page](/steps/incident-response-steps-nist-vs-sans/) puts them side by side, and the [six-step page](/steps/incident-response-plan-6-steps/) describes the SANS model.

See also the [correct order of the steps](/steps/correct-order-of-incident-response-steps/) and the [containment step](/steps/containment-step/).

## All step pages

- [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/)
- [What is the correct order of incident response steps?](/steps/correct-order-of-incident-response-steps/)
- [The containment step of incident response](/steps/containment-step/)

## Related pages

- [Free incident response plan template](/)
- [Glossary](/glossary/)
- [FAQ](/faq/)
- [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/)
- [The standards map](/standards-map/)

## 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)
- 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)
- SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/steps/
