Incident Response Frameworks Compared: NIST, SANS, and ISO/IEC 27035

What is an incident response framework?
An incident response framework is a structured model that defines how an organization prepares for, detects, contains, and recovers from a cybersecurity incident — and how it learns from that incident afterward. Rather than reacting to a breach ad hoc, a framework gives teams a shared language, a defined sequence of actions, and clear ownership so that nothing falls through the cracks when every second counts.
Frameworks matter for three reasons:
- Consistency — everyone follows the same playbook, regardless of who is on shift when the alert fires.
- Speed — pre-agreed decision paths and escalation authority remove hesitation during a live incident.
- Compliance — regulators and standards such as DORA, NIS2, PCI DSS, and ISO 27001 increasingly expect a documented, tested incident response capability.
The three dominant frameworks below approach the same goal from different angles.
The 3 leading incident response frameworks at a glance
‍
‍
The NIST incident response framework (SP 800-61 Revision 3)
The NIST incident response framework is defined in Special Publication 800-61, Revision 3, released in April 2025. This is a significant change worth understanding, because it replaced a model that had been the industry default for over a decade.
What changed in 2025. The older Revision 2 (the Computer Security Incident Handling Guide) described a four-phase lifecycle: Preparation; Detection & Analysis; Containment, Eradication & Recovery; and Post-Incident Activity. NIST formally withdrew Revision 2 on 3 April 2025 and superseded it entirely with Revision 3. If your incident response plan still references the four-phase model, it is now built on withdrawn guidance.
How Revision 3 is structured. Rather than a linear list of phases, Revision 3 maps incident response activities across the six core functions of the NIST Cybersecurity Framework (CSF) 2.0:
- Govern — establish and communicate the organization's cybersecurity risk-management strategy, expectations, and policy.
- Identify — understand assets, risks, and the environment so incidents can be recognised in context.
- Protect — put safeguards in place to prevent or limit the impact of incidents.
- Detect — find and analyse anomalous or malicious activity.
- Respond — take action once an incident is confirmed: contain, eradicate, and coordinate.
- Recover — restore normal operations and reduce the impact of the incident.
The most important shift is philosophical. Revision 3 treats incident response as a continuous, embedded practice rather than a sequence you run only when something goes wrong. Improvement is no longer confined to a single "post-incident" meeting at the end — it happens throughout the lifecycle. That reframing — from a linear playbook to an ongoing capability — is exactly why point-in-time preparation is no longer enough.
The SANS incident response process (PICERL)
The SANS incident response process is a six-step model developed by the SANS Institute, widely referred to by the mnemonic PICERL. Where the current NIST guidance is outcome- and governance-oriented, the SANS model is prized for its operational, step-by-step clarity — it tells responders what to do, in what order, and how to hand off between stages during a live incident.
The six steps are:
- Preparation — build and resource the incident response team, define policy, identify critical assets, and create and test response plans before anything happens.
- Identification — monitor systems, detect deviations from normal, confirm whether an event is a genuine incident, and establish its type and severity.
- Containment — limit the damage, typically with short-term containment (e.g. isolating an affected segment) followed by longer-term measures while clean systems are rebuilt.
- Eradication — remove the threat from the environment, including root-cause analysis so the same weakness cannot be re-exploited.
- Recovery — restore affected systems to normal operation and validate they are clean and monitored before returning them to production.
- Lessons Learned — review the incident end-to-end and feed improvements back into preparation.
Because it splits detection, containment, eradication, and recovery into discrete, sequential stages, PICERL reads more like a responder's field manual than a governance model — which is precisely why many technical teams reach for it first.
The ISO/IEC 27035 incident response standard
ISO/IEC 27035 is the international standard for information security incident management. Its foundational document, ISO/IEC 27035-1:2023 (Principles and process), is the second edition and technically revises the original 2016 version. Unlike NIST and SANS, ISO/IEC 27035 is designed to slot directly into an ISO 27001 information security management system, which makes it the natural choice for organizations pursuing certification or operating under international audit requirements.
The standard defines a 5-phase process:
- Plan and prepare — establish incident management policy with top-management commitment, form the incident management team, and put supporting processes and awareness in place.
- Detect and report — identify and report potential information security events and incidents.
- Assess and decide — triage reported events, determine whether they are incidents, and decide on the appropriate response.
- Respond — contain, investigate, resolve, and where necessary escalate the incident.
- Learn lessons — identify improvements, implement them, and evaluate the incident response team's performance.
The ISO/IEC 27035 series extends beyond this single document — later parts cover planning and preparation in depth and the operational running of incident response — but the five-phase model above is the backbone every part builds on.
NIST vs SANS vs ISO/IEC 27035: which should you use?
The frameworks are complementary far more than they are competitive, and mature security programmes routinely blend them:
- Choose NIST SP 800-61 Rev 3 when you need incident response to sit inside a broader risk-management strategy, when you report to a board that thinks in terms of governance and continuous improvement, or when US and federal alignment matters. Its CSF 2.0 structure makes it easy to benchmark maturity across the six functions.
- Choose SANS PICERL when you want an operational, execution-focused playbook your responders can follow stage by stage under pressure. It is the most immediately actionable of the three at the technical coalface.
- Choose ISO/IEC 27035 when you need an auditable, certifiable process that aligns with ISO 27001 and satisfies international compliance and customer-assurance requirements.
In practice, the phases map onto one another cleanly. SANS's Preparation and ISO's "Plan and prepare" mirror NIST's Govern/Identify/Protect; SANS's Identification aligns with ISO's "Detect and report" and NIST's Detect; and every framework closes with a structured learning loop. Picking a framework is the easy part. The gap that actually determines outcomes lies elsewhere.
Where frameworks stop and readiness begins
Every framework on this page describes what good incident response looks like. None of them prove that your people can do it when a real attacker is inside your environment at 2 a.m. A plan that lives in a shared drive and has never been stress-tested is a compliance artifact, not a capability — and the 2025 NIST revision makes exactly this point when it reframes incident response as a continuous practice rather than a document you write once.
That distinction — between having a framework and proving you can execute it — is where Immersive focuses. Immersive One lets organizations rehearse their incident response against realistic, high-fidelity scenarios and measure how their people actually perform:
- Cyber Range Exercising puts technical teams into live-fire scenarios mapped to MITRE ATT&CK, so they can test detection, containment, and response — the operational heart of the SANS and NIST models — in a safe, controlled environment.
- Cyber Crisis Simulation exercises decision-making, coordination, and leadership under pressure, and benchmarks performance against recognised frameworks including NIST, ISO, and DORA — turning an abstract standard into evidence of readiness.
- The wider Immersive One platform runs this as a continuous loop — prove, improve, benchmark, report — so readiness is something you can demonstrate to the board with data, not assume.
The frameworks tell you where you should be. Immersive helps you prove you're actually there, find the gaps, and be ready before the next incident lands.
‍
Key takeaways
- The three leading incident response frameworks are NIST SP 800-61 Rev 3, SANS PICERL, and ISO/IEC 27035 — each strong in a different context.
- NIST changed materially in April 2025: Revision 2's four-phase model is withdrawn and replaced by a CSF 2.0-aligned, six-function model. Plans still citing the old phases need updating.
- SANS PICERL (six steps) is the most operational; ISO/IEC 27035 (five phases, 2023 edition) is the most audit- and certification-friendly.
- The frameworks are complementary, not mutually exclusive — most mature programmes combine them.
- A framework only becomes a capability once your workforce has rehearsed it. Continuous exercising and simulation turn a written plan into proven, measurable readiness.
Ready to prove your incident response actually works? See how Immersive One helps organizations build and measure cyber resilience against NIST, ISO, and DORA.
Frequently asked questions
What are the phases of the NIST incident response lifecycle? As of Revision 3 (April 2025), NIST SP 800-61 maps incident response to the six functions of CSF 2.0: Govern, Identify, Protect, Detect, Respond, and Recover. The earlier four-phase model (Preparation; Detection & Analysis; Containment, Eradication & Recovery; Post-Incident Activity) came from Revision 2, which NIST has withdrawn.
What does PICERL stand for? PICERL is the mnemonic for the six steps of the SANS incident response process: Preparation, Identification, Containment, Eradication, Recovery, and Lessons Learned.
What is the difference between NIST and SANS incident response? The SANS PICERL model is a linear, six-step operational playbook focused on how responders execute during an incident. NIST SP 800-61 Rev 3 is broader and governance-oriented, mapping incident response to CSF 2.0's six functions and treating it as a continuous risk-management activity. SANS is often favoured for hands-on execution; NIST for policy, governance, and maturity benchmarking.
Is ISO/IEC 27035 the same as ISO 27001? No. ISO 27001 is the standard for an information security management system as a whole. ISO/IEC 27035 is a supporting standard that provides detailed guidance specifically on information security incident management, designed to align with and strengthen an ISO 27001 programme.
Can you use more than one incident response framework? Yes, and many organizations do. A common approach is to use NIST or SANS to structure day-to-day operations and ISO/IEC 27035 to make the programme certifiable and auditable. Because their phases map onto one another closely, blending them is straightforward.
‍
‍
