Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is the NIST SP 800-61 Incident Response Lifecycle?

NIST SP 800-61 is the most widely adopted incident response framework, built around four phases in Revision 2 and restructured in April 2025 around the six functions of CSF 2.0.

Illustration for the cybersecurity term NIST SP 800-61
Home / Blog / Cybersecurity Terms / What Is the NIST SP 800-61 Incident Response Lifecycle?
17 November 2026

What Is the NIST SP 800-61 Incident Response Lifecycle?

What Is the NIST SP 800-61 Incident Response Lifecycle?

NIST Special Publication 800-61 is the incident handling guide published by the United States National Institute of Standards and Technology. It has no legal force in the UK, yet it is the framework most British incident response plans are built on, largely because it describes the work in a sequence that survives contact with a real incident.

Revision 2, issued in August 2012, defined the four-phase cycle almost everyone quotes. Revision 3, published in April 2025, rewrote the document around the NIST Cybersecurity Framework 2.0 functions, which changes its emphasis significantly. Both are worth understanding, because most existing plans and job descriptions still use the older vocabulary.

The Four Phases of Revision 2

  1. Preparation. Everything done before an incident: the plan, the team, the contact lists, the logging, the tooling, the retainer, and the exercises. Revision 2 is blunt that this phase determines the outcome of the other three.
  2. Detection and Analysis. Recognising that something has happened, triaging the signal, determining scope, and prioritising. This is where most organisations lose time, because an alert without context cannot be assessed.
  3. Containment, Eradication, and Recovery. Grouped deliberately as one phase, because the three overlap and iterate rather than running in sequence. Containment buys time; eradication removes the attacker’s access; recovery returns services to normal operation under heightened monitoring.
  4. Post-Incident Activity. The lessons-learned review, the root cause analysis, evidence retention decisions, and the feedback of findings into preparation.

The cycle is drawn as a loop for a reason. Output from post-incident activity is input to preparation, and in practice teams move backwards as often as forwards, returning to analysis when containment reveals a second foothold.

What Revision 3 Changed

SP 800-61r3 is subtitled as a CSF 2.0 community profile and is a considerably shorter document. Rather than describing a self-contained lifecycle, it maps incident response activity onto the six CSF functions: Govern, Identify, Protect, Detect, Respond, and Recover.

The notable addition is Govern. Revision 3 treats incident response as part of enterprise risk management with named accountability, policy, roles, and supplier arrangements, rather than as a technical procedure owned by the security team. It also abandons the fixed phase diagram, acknowledging that preparation and improvement are continuous rather than bracketing the incident. If your plan is written against Revision 2, the practical gap to close is usually governance evidence: who decides, who is informed, and what the board has approved.

Mapping to Other Models

The SANS six-step model, PICERL, splits the NIST third phase into containment, eradication, and recovery as separate steps and is otherwise identical. The NCSC’s incident management guidance covers the same ground in British terms, and the Cyber Assessment Framework places incident management under Objective D, where it is assessed for operators of essential services under the NIS Regulations 2018.

For UK organisations the framework also has to carry regulatory timing. The ICO must be notified of a qualifying personal data breach within 72 hours of becoming aware, which sits inside the detection and analysis phase rather than after it. Financial entities in scope of DORA face their own reporting windows, and the cyber resilience legislation announced in the 2024 King’s Speech proposes to widen UK incident reporting duties further.

Using It Without Turning It Into Paperwork

At Privia Security, we build and test plans against this structure as part of Emergency Action Plan Services, so that the first time a team uses the process is not during a live incident.

FAQ – Frequently Asked Questions

What Are the Four Phases of the NIST Incident Response Lifecycle?

Preparation; Detection and Analysis; Containment, Eradication, and Recovery; and Post-Incident Activity. The third phase deliberately groups three overlapping activities because they iterate rather than run in order. The cycle feeds back on itself, with findings from the final phase improving preparation before the next incident, which is why it is drawn as a loop rather than a line.

Should We Follow Revision 2 or Revision 3?

Revision 3, published in April 2025, is the current document and aligns incident response with CSF 2.0, adding explicit governance expectations. Revision 2 remains useful because its four-phase language is embedded in most existing plans, training, and job descriptions. A reasonable approach is to keep your operational playbooks as they are and add the governance and supplier elements that Revision 3 emphasises.

Is NIST SP 800-61 Relevant for a UK Organisation?

Yes. It carries no legal weight in the UK, but it is the de facto reference used by consultancies, insurers, and software vendors, so plans written against it are widely understood. UK-specific obligations still apply on top: the ICO’s 72-hour breach notification, the NCSC Cyber Assessment Framework for essential services, and sector rules such as DORA for financial entities.

How Is SP 800-61 Different From the SANS PICERL Model?

Only in presentation. PICERL lists preparation, identification, containment, eradication, recovery, and lessons learned as six discrete steps, while NIST combines containment, eradication, and recovery into one phase and calls identification detection and analysis. The underlying activities are the same, so an organisation can document against either without materially changing how it responds.

Related Terms

You May Be Interested In These

What Is a Macro Virus?

Cybersecurity Terms

17 November 2026

What Is a Macro Virus?

Read More
What Is SMB Protocol Security?

Cybersecurity Terms

17 November 2026

What Is SMB Protocol Security?

Read More
What Is a PLC?

Cybersecurity Terms

17 November 2026

What Is a PLC?

Read More