Written and maintained by CASRAI Editorial Board
Published
On this page
NIST SP 800-61 Rev. 3, published in April 2025 as “Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile”, is the current NIST guidance on responding to cybersecurity incidents. It replaces SP 800-61 Rev. 2 (August 2012), and instead of a step-by-step handling guide it organizes incident response recommendations around the six functions of the NIST Cybersecurity Framework (CSF) 2.0: Govern, Identify, Protect, Detect, Respond and Recover.
For a university, institute or research-computing group, the document is a planning reference: it tells a research office, a security team and a principal investigator who needs to be involved in an incident, what each stage should achieve, and how those outcomes connect to the wider cybersecurity risk management programme. It does not prescribe tools or technical procedures.
Ask CASRAI · free to tryQuestion about this guide? Ask CASRAI answers with linked sources. 2 free questions a day, no account.
What NIST SP 800-61 Rev. 3 is used for in research
The authors are Alexander Nelson, Sanjay Rekhi and Murugiah Souppaya of NIST and Karen Scarfone of Scarfone Cybersecurity. NIST’s publication page gives the identifier DOI 10.6028/NIST.SP.800-61r3 and lists an earlier draft dated 3 April 2024. The final text is 48 pages.
The publication frames incident response as part of cybersecurity risk management rather than as a separate team’s side activity. Its change log describes a full rewrite: the focus moved from guidelines on detecting, analyzing, prioritizing and handling incidents to recommendations for incorporating incident response throughout cyber risk management. The scope section states that the new scope “differs significantly from previous versions”, because the details of how to perform incident response change too often to capture in one static publication.
Events and incidents
The document separates an event from an incident. An event is any observable occurrence involving computing assets, and an adverse event is one with a negative consequence; the guide addresses only adverse cybersecurity events. An incident uses the definition from the Federal Information Security Modernization Act of 2014: an occurrence that actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality or availability of information or an information system, or that constitutes a violation or imminent threat of violation of law, security policies, security procedures or acceptable use policies. For a research institution, that boundary matters because it decides when a suspicious log entry becomes a declared incident that triggers roles, reporting and notification.
The six functions in the incident response life cycle
NIST describes all six CSF 2.0 Functions as having a role. Govern, Identify and Protect help organizations prevent some incidents, prepare for those that occur, reduce their impact and improve from lessons learned. Detect, Respond and Recover help organizations discover, manage, prioritize, contain, eradicate and recover from incidents, and handle incident reporting, notification and other communications. The preparation activities are described as not part of incident response itself; incident response is Detect, Respond and Recover, and continuous improvement runs through the Improvement category (ID.IM) in the Identify Function.
NIST also notes why the old model changed. Rev. 2 depicted a circular life cycle handled by a separate team, at a time when incidents were relatively rare and often completed within a day or two. The new document says incidents now occur frequently, recovery can take weeks or months, and lessons learned should often be shared as soon as they are identified rather than after recovery concludes.
How to access NIST SP 800-61 Rev. 3
The publication is available from NIST’s Computer Security Resource Center (CSRC) publication page for SP 800-61 Rev. 3, and the 48-page PDF is hosted on NIST’s publication server (both linked under Sources). The Rev. 2 text is a separate document with its own DOI (10.6028/NIST.SP.800-61r2).
Implementation resources live outside the PDF. The executive summary says the mappings can be reached through the NIST Cybersecurity and Privacy Reference Tool (CPRT), for example from CSF outcomes to SP 800-53 controls, and the change log notes that hyperlinks moved to a new SP 800-61 project website. NIST’s incident response project page groups these as preparation resources and life cycle resources and lists related NIST work on the Cybersecurity Framework, log management, mobile forensics, the National Vulnerability Database and ransomware protection and response.
How to build an incident response plan with NIST SP 800-61 Rev. 3, step by step
The document is a Community Profile, not a procedure, so the steps below follow how its sections and tables are organized. They are an editorial reading of the document, not a NIST-numbered process.
- Write the policy first. Section 2.3 says most incident response policies share the same elements: a statement of management commitment, purpose and objectives, scope, definitions of events, incidents and investigations, roles, responsibilities and authorities (including who may confiscate, disconnect or shut down assets), guidelines for prioritizing incidents and estimating severity, and performance measures.
- Name the roles. Section 2.2 gives example roles: leadership, incident handlers (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. Where an organization has several teams, NIST says they should act as one coordinated entity such as a federation. Where a provider such as an MSSP or cloud service provider is involved, the responsibilities should be defined in a contract.
- Document procedures and playbooks. Procedures should rest on the policy and plan and can be tested or exercised periodically. NIST points readers to CISA’s incident and vulnerability response playbooks as examples. A tabletop exercise is one way to test whether the plan matches how people would actually act.
- Set priorities in the Profile. Use the High, Medium and Low priority column as a starting point and adjust it to your own context; NIST says organizations are encouraged to customize the Profile.
- Detect and declare. DE.AE-08 says incidents are declared when adverse events meet the defined incident criteria, and its recommendation is to apply those criteria to the known and assumed characteristics of the analyzed activity while considering known false positives.
- Respond. Under RS.MA, triage and validate incident reports (RS.MA-02), categorize and prioritize by type such as data breach, ransomware, account takeover or denial of service (RS.MA-03), escalate or elevate as needed (RS.MA-04), then contain (RS.MI-01) and eradicate (RS.MI-02).
- Notify and share. RS.CO-02 recommends following established coordination procedures and notifying in compliance with the laws and regulations that apply to the organization’s sector, location and customer locations. RS.CO-03 treats voluntary sharing of incident information, for example with a sector ISAC, as often mutually beneficial.
- Recover and close. RC.RP-03 to RC.RP-05 ask for backups and restored assets to be checked for indicators of compromise and integrity problems before and after use; RC.RP-06 recommends an after-action report documenting the incident, the actions taken and lessons learned.
- Feed lessons back. Lessons from every function go into Improvement (ID.IM) and are used to inform all of the functions.
How to read the Community Profile tables
Section 3 holds the Profile in two tables. Table 2 covers Preparation (Govern, Identify, Protect) and Lessons Learned (Identify-Improvement). Table 3 covers Incident Response (Detect, Respond, Recover). Each CSF Function, Category and Subcategory has its own row, with four columns: CSF Element, the element’s description, a Priority, and Recommendations, Considerations and Notes.
Priority column
Priority is relative to incident response. High means a core incident response activity for most organizations, Medium means it directly supports incident response, and Low means it indirectly supports it. NIST says a Low rating “does not imply that they are unnecessary”, only that the element is outside the direct scope of responding to incidents. Most Table 2 rows are Low and carry no recommendations; every Table 3 element carries recommendations or considerations.
R, C and N codes
Each item in the last column starts with R (recommendation: something the organization should do), C (consideration: something it should consider doing) or N (note: additional information). Appending the code to the CSF ID makes a unique identifier, for example GV.OC-03.R1 is recommendation 1 for subcategory GV.OC-03. Statements made at a Function or Category level also apply to the Categories or Subcategories under them.
Worked reading: DE.CM
Table 3 begins with DE (Detect), described as “Possible cybersecurity attacks and compromises are found and analyzed”, rated High. Its first Category, DE.CM (Continuous Monitoring), is also High. DE.CM.R1 says continuous monitoring should cover networks and network services; computing hardware and software, runtime environments and their data; the physical environment; personnel activity and technology usage; and external service provider activities. C1 suggests using cyber threat information with monitoring, and R2 says to tune monitoring technologies to reduce false positives and false negatives to acceptable levels. Read as an ID: DE.CM.R1 is a recommendation, DE.CM.C1 a consideration.
The data table below lists the eight Categories that make up Table 3, with the subcategories each includes. Table 1 of the publication, which maps the Rev. 2 phases to CSF 2.0, is summarized here instead: Rev. 2’s Preparation maps to Govern, Identify (all Categories) and Protect; Detection and Analysis maps to Detect and Identify (Improvement); Containment, Eradication and Recovery maps to Respond, Recover and Identify (Improvement); and Post-Incident Activity maps to Identify (Improvement).
Troubleshooting NIST SP 800-61 Rev. 3
Looking for the four phases or a handling procedure
Readers who know Rev. 2 often search the new document for the four phases and detailed handling steps. The publication states that how-to detail changes too often for a static document, so the phases are replaced by CSF Functions and the Table 1 mapping. For technical implementation, use the CPRT mappings and the controls in NIST SP 800-53 Rev. 5, which NIST’s mappings connect to CSF outcomes.
Treating Low priority as optional
A Low or Medium priority in Table 2 means the element supports incident response indirectly or directly, not that it can be skipped. Some Low-rated Govern rows carry no recommendation at all, while Medium rows such as GV.OC-03 do: it says cybersecurity requirements should include all requirements related to incident notifications, data breach reporting and other aspects of incident response.
Undefined terms
NIST states that some terms in the recommendations, for example “data breach”, are not defined in the publication. Organizations adopting the Profile should define them in the context of their own environment, use cases and applicable laws and regulations, and may consult the NIST glossary.
Assuming a single team handles everything
The publication says incident response used to be performed almost exclusively by an organization’s own incident handlers, but success now depends on many internal and external parties. If your plan names only a security team, compare it against the role examples in section 2.2.
Technology examples that age
NIST notes that technologies mentioned in the recommendations are examples as of writing and may become outdated, and that the recommendations are not comprehensive and will not all apply to every organization.
Related and earlier guidance to NIST SP 800-61 Rev. 3
Rev. 3 is itself the successor to Rev. 2, and it cites other NIST and CISA material for specific tasks. The table lists those pointers as the publication gives them.
| Resource | What the publication says about it |
|---|---|
| SP 800-61 Rev. 2 (2012) | Computer Security Incident Handling Guide; superseded by Rev. 3. Its four-phase life cycle is mapped to CSF 2.0 in Table 1. |
| CISA incident and vulnerability response playbooks | Cited as examples of incident response playbooks. |
| SP 800-184 | Cited for more information on incident recovery plans and plan execution. |
| SP 800-150 | Cited for guidelines on consuming, using and storing cyber threat intelligence and establishing sharing relationships. |
| NIST CSF 2.0 and the CPRT | The framework the Profile is built on, and the tool for mappings such as CSF outcomes to SP 800-53 controls. |
For related background on this site, see threat intelligence, NIST SP 800-115 on security testing and NIST SP 800-171 Rev. 3, which covers protecting controlled unclassified information in non-federal systems.
Sources
- NIST CSRC, SP 800-61 Rev. 3 publication page, read 17 November 2026.
- NIST SP 800-61 Rev. 3, full PDF (April 2025), read 17 November 2026.
- NIST CSRC, Incident Response project page, read 17 November 2026.
- DOI 10.6028/NIST.SP.800-61r3, the publication’s persistent identifier.
Data: Categories in Table 3 (Incident Response) of NIST SP 800-61 Rev. 3
The eight CSF 2.0 Categories that make up Table 3 of the Rev. 3 Community Profile (Detect, Respond, Recover), with the CSF function, the priority shown in the table and the subcategories listed under each, compiled by reading the publication's Table 3.
Period covered: 2025.
| Category ID | Category name | CSF Function | Priority | Subcategories listed (count) | Subcategory IDs |
|---|---|---|---|---|---|
| DE.CM | Continuous Monitoring | Detect | High | 5 | DE.CM-01, -02, -03, -06, -09 |
| DE.AE | Adverse Event Analysis | Detect | High | 6 | DE.AE-02, -03, -04, -06, -07, -08 |
| RS.MA | Incident Management | Respond | High | 5 | RS.MA-01 to RS.MA-05 |
| RS.AN | Incident Analysis | Respond | High | 4 | RS.AN-03, -06, -07, -08 |
| RS.CO | Incident Response Reporting and Communication | Respond | High | 2 | RS.CO-02, -03 |
| RS.MI | Incident Mitigation | Respond | High | 2 | RS.MI-01, -02 |
| RC.RP | Incident Recovery Plan Execution | Recover | High | 6 | RC.RP-01 to RC.RP-06 |
| RC.CO | Incident Recovery Communication | Recover | High | 2 | RC.CO-03, -04 |
Sources
- NIST SP 800-61 Rev. 3 (accessed 2026-11-17)
Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.







