Skip to content

Response, New York. Noah Park: Check Point Patches Actively Exploited Management Server Path Traversal. Detection, Dallas. Ava Okello: Report Finds Nearly Half of Deployed Detections Need Attention Before SOCs Can Trust Them.

SOCtember

Always First. Fast SOC News.

NIST incident response life cycle model diagram from the SP 800-61r3 project page.
Photo: NIST, incident response life cycle model based on CSF 2.0 Functions, SP 800-61r3.

Response

Did You Know: Containment Stops Expansion; Eradication Removes What Remains

NIST SP 800-61 Revision 3 maps incident response to CSF 2.0 and keeps a distinction responders still need on the keyboard: containment prevents an incident from expanding, while eradication removes persistence and entry points after the bleed is stopped.

Noah Park, ResponseNew York3 min read

GAITHERSBURG - The National Institute of Standards and Technology finalized Special Publication 800-61 Revision 3 in April 2025 as a CSF 2.0 Community Profile for cyber incident risk management. The guide, authored by Alexander Nelson, Sanjay Rekhi, and Murugiah Souppaya of NIST with Karen Scarfone of Scarfone Cybersecurity, supersedes the August 2012 Revision 2 Computer Security Incident Handling Guide. It no longer treats incident response as a closed four-phase circle run by a separate team between rare events. Instead it places Detect, Respond, and Recover as the incident response layer, with Govern, Identify, and Protect as broader preparation and risk management that support response but are not response itself, and with continuous improvement (Identify Improvement, ID.IM) feeding every Function.

Figure 1 from NIST SP 800-61r3 showing the previous four-phase incident response life cycle.
Photo: NIST, Fig. 1 from SP 800-61r3, the previous incident response life cycle model, shown for contrast.

Inside Respond, NIST still draws a sharp operational line that many SOC desks blur under pressure. Under RS.MI-01, containment means preventing expansion of an incident so additional damage does not pile up and resources are not overwhelmed. Most incidents, NIST says, require some form of containment. Under RS.MI-02, eradication means mitigating effects after containment: eliminating persistence mechanisms and entry points such as deleting malware, disabling breached user accounts, and identifying and mitigating all exploited vulnerabilities, after identifying every affected host and service so all flaws can be remediated. Recovery then restores assets and operations and confirms systems are functioning normally.

NIST mark with the SP 800-61 Revision 3 title.
Photo: NIST, brand mark with the SP 800-61 Revision 3 title panel (April 2025 final).
SOCtember diagram contrasting containment under RS.MI-01 with eradication under RS.MI-02.
Illustration: SOCtember, containment (RS.MI-01) versus eradication (RS.MI-02), paraphrased from NIST SP 800-61r3.

Revision 3 also warns against treating evidence collection as a free pause. Redirecting an attacker into a sandbox to gather more data delays containment and eradication. NIST says the incident response team should first discuss the feasibility of that strategy with the legal department, because an intentional delay can let an attacker escalate access or compromise other systems. For desks writing playbooks, the practical takeaway is sequence and authority: stop the spread, then remove what remains, then restore, while feeding lessons into improvement without waiting for a formal post-incident ceremony weeks later.

SOCtember diagram of CSF 2.0 incident response layered over improvement and preparation.
Illustration: SOCtember, Detect, Respond, and Recover over Improvement (ID.IM) over Govern, Identify, and Protect, paraphrased from NIST Fig. 2.

Sources:


Noah Park covers incident response and SOC operations for SOCtember from New York.

Related stories

Response desk