# Incident response plan in 6 steps: the SANS model

Steps, read 16 November 2026

**The short answer.** The SANS six-step model runs preparation, identification, containment, eradication, recovery and lessons learned. It comes from the SANS Incident Handler's Handbook, published 21 February 2012. This page, read on 16 November 2026, gives each step's purpose and what it must leave behind.

## What are the six steps of incident response?

The six steps are preparation, identification, containment, eradication, recovery and lessons learned. The SANS Incident Handler's Handbook says it limits itself to the six phases of the incident handling process and notes that each phase, from preparation to lessons learned, is best followed in sequence because each builds on the other.

| Step | Purpose in the handbook | Leaves behind |
| --- | --- | --- |
| 1 Preparation | Ready the team: policy, response plan, communication, documentation, team, access control, tools, training | Plan, contact list, tools, drilled team |
| 2 Identification | Detect and decide whether a deviation is an incident, and its scope | Declared incident, evidence, notified team |
| 3 Containment | Limit damage: short-term containment, system back-up, long-term containment | Stopped spread, forensic image |
| 4 Eradication | Remove and restore affected systems, usually by reimaging, and improve defenses | Clean systems, patched weakness |
| 5 Recovery | Return systems to production carefully, test, monitor and validate | Systems back, monitored |
| 6 Lessons learned | Complete documentation and review | Report, meeting, improvements |

What are the six steps of incident response?

## What does preparation include in the SANS model?

The handbook lists eight elements: policy, response plan or strategy, communication, documentation, the response team, access control, tools and training. It suggests a "jump bag" holding everything responders need and drills at regular intervals.

Template sections 1 to 4, 12 and 14 cover the same ground.

## How quickly should lessons learned happen?

The handbook says the lessons learned meeting should be held as soon as possible and gives a rule of thumb of within two weeks after the incident, with a short report and an executive summary. The template's [review section](/templates/incident-response-checklist-template/) uses a 10 business day default that you can change.

## Where does this model sit beside NIST?

NIST SP 800-61 Rev. 3 maps the older four-phase NIST model to CSF 2.0 Functions. The SANS model splits NIST's "containment, eradication and recovery" phase into three. See [NIST versus SANS](/steps/incident-response-steps-nist-vs-sans/).

## Related pages

- [Incident response steps: the order and who does what](/steps/)
- [Free incident response plan template](/)
- [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/)
- [Incident response steps: NIST vs SANS compared](/steps/incident-response-steps-nist-vs-sans/)
- [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

- 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)

Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/steps/incident-response-plan-6-steps/
