18Defense

NIST 800-61r3: what changed in incident response

If you have ever heard an incident-response plan described as 'preparation, detection and analysis, containment and eradication and recovery, post-incident activity', that phrasing came from NIST SP 800-61 Revision 2 — the Computer Security Incident Handling Guide, published in August 2012 and quoted in job interviews ever since. On April 3, 2025 NIST withdrew it and replaced it with SP 800-61r3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile. The new edition keeps the same goal — help organizations handle incidents better — but changes the shape of the advice, and with it the way a response plan should be built.

01What changed between Revision 2 and Revision 3

Revision 2 was an operations manual. It walked through a four-phase lifecycle in order — Preparation, then Detection and Analysis, then Containment, Eradication and Recovery, then Post-Incident Activity — and filled the space between the phases with concrete practice: severity ratings, containment trade-offs, evidence handling, notification templates. For thirteen years it was the default answer to 'what does incident response look like'.

Revision 3 is not a longer version of the same document. It is organized as a Community Profile for the Cybersecurity Framework 2.0, which means it expresses incident response as outcomes mapped to the six CSF functions rather than as steps in a sequence. The lifecycle is still there, but it sits inside a wider structure: Govern, Identify and Protect as the foundation that determines how well you respond; Detect, Respond and Recover as the operational core; and an improvement category (ID.IM, inside Identify) that feeds lessons learned back into everything else continuously, instead of as a final phase you get to at the end.

02The three layers, in plain terms

The foundation layer is where most response plans are actually weak. Govern covers who is allowed to declare an incident, who decides whether to isolate a production server or keep it running, what your policy says about paying a ransom, and which supplier contracts require breach notification. Identify is knowing what you have: the assets, dependencies and data flows that an incident will move through. Protect is everything that makes an incident smaller before it starts — phishing-resistant multi-factor authentication, tested offline backups, systems that are patched and hardened. A team with no authority to act can still run a perfect detection process and lose the day anyway.

The operational layer is the part people recognize: Detect means monitoring, alert triage and an agreed definition of when an event becomes an incident; Respond means analysis, containment, eradication and communications running in parallel; Recover means a documented restoration order, validation that the threat is gone, and a deliberate decision to return to normal. The connective layer — improvement — is what turns a single incident into institutional memory, and Revision 3 deliberately refuses to let it be an afterthought.

03What still has to come from you

Because Revision 3 works at the level of outcomes, it does not hand you the procedures. Those stay your responsibility, and they are the reason two organizations using the same document respond at wildly different speeds. Concretely: a severity scheme that a first-line analyst can apply without a meeting; containment options with named trade-offs (isolate the endpoint, snapshot before you wipe, keep the server under watch when destroying evidence costs more than the intrusion); an evidence and chain-of-custody habit; a communication plan that covers staff, customers, insurers and the press; and a notification clock — a personal-data breach in the EU has to reach the supervisory authority within 72 hours under GDPR, which starts counting while you are still arguing about scope.

None of that is exotic, and none of it survives on paper alone. The reliable way to find out which parts of your plan are fiction is a tabletop exercise: one hour, one scenario, the people who would really decide, and a written list of what the exercise exposed. Run it once a quarter and the plan becomes something the organization has actually done rather than something filed in a folder.

04How to use 800-61r3 without rebuilding everything

If your current plan already has an r2 shape, do not rewrite it. Map the sections you have onto the six CSF functions and look for the holes — in most organizations they cluster in Govern (nobody named as accountable, no escalation authority) and Identify (no current inventory, no dependency map). Keep the runbooks and severity tables that work; the shift is to stop treating response as a four-phase event bounded by the days around an incident, and start treating it as a capability that leadership funds, tests and reviews.

For the practical detail Revision 3 intentionally leaves out, NIST points readers to its Incident Response project page and to the CSF 2.0 reference material rather than repeating it in the publication. That is also the honest answer when a customer or an insurer asks which framework you follow: CSF 2.0 for the model of risk, 800-61r3 for how response is built into it, and your own tested runbooks for what happens on the night.

Sources & further reading

NIST CSRC — SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile (April 2025)

NIST — full publication PDF (SP 800-61r3)

NIST — news announcement: SP 800-61r3 supersedes SP 800-61r2

NIST — Incident Response project page and resources

Continue with MindSec

See MindSec incident-response and defense training paths

All publicationsNext publicationNIST CSF 2.0: the six functions in plain language
Skip to main content