NIST SP 800-61 Revision 3, incident response as a CSF 2.0 profile, explained
NIST’s April 2025 revision of SP 800-61 retires the four-phase incident handling cycle, maps incident response to the six CSF 2.0 Functions, rates each outcome High, Medium or Low, and moves the how-to material online.
For more than a decade, NIST Special Publication 800-61 Revision 2, the Computer Security Incident Handling Guide, was the reference many incident response plans were built around. In April 2025 NIST replaced it with Revision 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile [1]. The new version keeps the number and changes almost everything else. This explainer covers four parts: why NIST dropped the old life cycle, how the new model maps to the Cybersecurity Framework (CSF) 2.0, who it says takes part in a response, and how the community profile is built, with the status as checked on November 14, 2026.
Status and scope
NIST released a draft on April 3, 2024 and the final publication on April 3, 2025. It supersedes SP 800-61 Revision 2, dated August 6, 2012 [1]. As checked on November 14, 2026, the CSRC page lists Revision 3 as the final publication [1]. NIST developed it under its responsibilities in the Federal Information Security Modernization Act of 2014, and states that nongovernmental organizations may use it on a voluntary basis [2]. Its stated audience is cybersecurity program leadership, cybersecurity staff and others responsible for preparing for, detecting, responding to or recovering from incidents, and it is meant for most organizations regardless of sector or size [2].
The scope is narrower in one way and wider in another. NIST says the details of how to perform incident response change too often, and vary too much across technologies and organizations, to keep in one static document. The procedural guidance is gone, and the publication instead addresses risk management across all six CSF 2.0 Functions in support of incident response [2]. The change log records a full rewrite, a shift from guidelines on handling incidents to recommendations for building incident response into risk management, a reorganization as a CSF 2.0 Community Profile, and the move of most hyperlinks to a new SP 800-61 project website to make them easier to maintain [2].
The publication defines an event as any observable occurrence involving computing assets, including physical and virtual platforms, networks, services and cloud environments. For a cybersecurity incident it uses the FISMA 2014 definition: an occurrence that actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality or availability of information or an information system, or that violates or imminently threatens to violate law, security policies, security procedures or acceptable use policies [2].
From a four-phase cycle to six Functions
Revision 2 drew incident response as a circle: preparation, detection and analysis, containment, eradication and recovery, and post-incident activity. Revision 3 explains why that no longer fits. When the earlier guide was written, incidents were relatively rare and narrow and were usually resolved within a day or two, so a separate team running a separate cycle made sense. NIST now says incidents occur frequently, cause far more damage and often take weeks or months to recover from, and that lessons learned should often be shared as soon as they are identified, not delayed until after recovery concludes [2].
The new model uses the six CSF 2.0 Functions. Govern, Identify and Protect help prevent some incidents, prepare for the ones that happen, reduce their impact and improve practice from lessons learned. Detect, Respond and Recover cover finding, managing, prioritizing, containing, eradicating and recovering from incidents, including reporting and notification [2]. The project page describes the figure in layers: the preparation Functions at the bottom are broader risk management activities that also support incident response; Detect, Respond and Recover are the response itself; and the Improvement Category in Identify sits in the middle, taking lessons from every Function and feeding them back [3].
NIST gives the mapping from the old phases [2]:
- Preparation maps to Govern, all of Identify, and Protect.
- Detection and analysis maps to Detect and to Identify’s Improvement Category.
- Containment, eradication and recovery maps to Respond, Recover and Identify’s Improvement Category.
- Post-incident activity maps to Identify’s Improvement Category.
NIST does not insist on its own model. It says organizations should use the incident response life cycle framework or model that suits them best, and that larger, more technology-dependent organizations are likely to gain more from a model that stresses continuous improvement [2]. In our reading, an organization that keeps a four-phase plan is still within the guidance. The publication says that, whatever model is used, every organization should take incident response into consideration throughout its cybersecurity risk management activities [2].
Who takes part, including providers
The guide says incident response used to be performed almost exclusively by incident handlers from the organization’s own team, and that most organizations increasingly recognize that success depends on many internal and external parties [2]. Its examples are leadership, which oversees response, allocates funding and may decide on high-impact actions such as shutting down or rebuilding critical services; incident handlers, who may be on staff, on contract or available when needed; technology professionals; legal; public affairs and media relations; human resources; physical security and facilities; and asset owners, who know response and recovery priorities for their systems [2].
Third parties get specific treatment. NIST describes a shared responsibility model in which an organization transfers some responsibilities to a provider, such as a managed security services provider performing detection, response and recovery, or a cloud or internet service provider involved in some incidents. Those responsibilities should be defined in a contract, and the response team should know the division of duties, information flows, coordination and authority to act, including limits such as whether the provider may share sanitized incident information with other customers or deactivate services to contain an incident [2]. NIST adds that providers often hold privileged access and sensitive data, so the risk of a malicious insider or a compromised provider should be addressed, for example through non-disclosure agreements and contract clauses [2].
For regulated organizations, our reading is that this section maps closely onto contract and third-party risk work that banks, health systems and agencies already do. An incident clause that names who may contain, who may notify and who holds the evidence is easier to agree before an incident than during one. That is our observation, not text from the publication.
How the community profile works
Section 3 is the core of the document. It is a CSF 2.0 Community Profile in two tables: one for preparation (Govern, Identify and Protect) and lessons learned (Identify’s Improvement Category), and one for incident response (Detect, Respond and Recover). Every Function, Category and Subcategory has a row with a priority for incident response: High for a core activity for most organizations, Medium for activities that directly support it, and Low for those that indirectly support it. NIST calls these a starting point for organizations to tailor [2]. Items in each row are labeled R for a recommendation, C for a consideration and N for a note, so that “GV.OC-03.R1” is the first recommendation for that Subcategory [2].
A few rows show the flavor:
- DE.AE-08, incidents are declared when adverse events meet defined criteria (High): apply incident criteria to the known and assumed characteristics of analyzed activity, and consider known false positives [2].
- RS.MA-02, incident reports are triaged and validated (High): verify that an incident occurred, estimate severity and urgency, and have mechanisms for third parties to report possible incidents involving the organization [2].
- RS.CO-02, stakeholders are notified (High): follow procedures on what must be reported to whom and when, and notify in line with the incident notification laws and regulations that apply to the organization’s sectors and locations, noting that new laws and regulations are being established frequently [2].
- GV.SC-08, suppliers and other third parties are included in incident planning, response and recovery (Medium), with a pointer to ID.IM-02 on tests and exercises, which is rated High [2].
The detailed resources now live online. NIST points readers to the Incident Response project page and to mappings in the Cybersecurity and Privacy Reference Tool, such as links from CSF 2.0 outcomes to SP 800-53 controls [2] [3]. Our suggestion, not NIST’s: teams that cited specific sections of Revision 2 in plans, contracts or audit evidence may want to check where that material went. The change log says NIST removed outdated material and material addressed in more depth in other NIST publications and other federal agency content [2].
Status as checked on November 14, 2026. NIST states that nongovernmental organizations may use the publication on a voluntary basis [2]. Where a regulator, contract or insurer cites SP 800-61, we suggest confirming which revision it means. This explainer is general information, not legal advice.
Moraph’s teams help organizations with work like this. See our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.