Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
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.

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 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.
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.
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.
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.
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.
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.
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.
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.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.