An incident response plan is a document an organization writes in advance to say what happens when its systems are attacked or its data is actually breached, for example by ransomware (malware that encrypts data and demands payment): who does what, who decides, and who must be told. NIST (the US standards institute) publishes the main guidance on this as SP 800-61 Rev. 3, released in April 2025, which replaced Rev. 2 of August 2012. This article summarizes the new edition and shows how to turn it into a plan that works in practice.

What NIST SP 800-61 Rev. 3 is

CSF 2.0 is version 2.0 of the NIST Cybersecurity Framework (NIST's framework for managing cyber risk). The document's full title is Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile. NIST's publication page says the final version came out in April 2025 (the public draft was in April 2024) and that Rev. 3 supersedes Rev. 2. A Community Profile is a baseline set of CSF outcomes written for a particular community or topic, here incident response. NIST adds that readers can reach reference material mapped to each topic through the NIST Cybersecurity and Privacy Reference Tool (CPRT).

NIST explains the reason for the revision in the document itself. When Rev. 2 was written, incidents were fairly rare, narrow in scope, and usually handled within a day or two, so incident response could be treated as a separate job for a dedicated team. Today incidents are frequent and do more damage, and recovery often takes weeks or months. NIST therefore treats incident response as part of cyber risk management across the whole organization.

The new life cycle: six CSF 2.0 Functions

CSF 2.0 divides security work into six Functions. Rev. 3 uses all six as the frame of its incident response life cycle. They mean the following:

  • Govern: the organization's cyber risk strategy, expectations, and policy are set, communicated, and monitored
  • Identify: the organization's current cyber risks are understood
  • Protect: safeguards are used to manage those risks
  • Detect: possible attacks and compromises are found and analyzed
  • Respond: actions are taken on a detected incident
  • Recover: assets and operations affected by an incident are restored

NIST draws the life cycle in three levels. Govern, Identify, and Protect are preparation work that is broader than incident response and also supports it. Incident response itself is Detect, Respond, and Recover. The middle level is continuous improvement (the Improvement category inside Identify). Lessons from every Function flow into it and are then used to adjust all Functions. NIST says lessons should be shared as soon as they are found, not held until recovery is over.

INFOGRAPHIC
The CSF 2.0 incident response life cycle
Incident response
six Functions in three levels
Govern
preparation: policy, expectations, authority
Identify and Protect
preparation: know the risks, apply safeguards
Detect, Respond, Recover
incident response itself
Improvement (ID.IM)
middle level: lessons from every Function

Rev. 3 includes a table that maps the four phases of the Rev. 2 life cycle to the new Functions. Preparation maps to Govern, Identify, and Protect. Detection & Analysis maps to Detect. Containment, Eradication & Recovery maps to Respond and Recover. Post-Incident Activity maps to the Improvement category. NIST stresses that an organization may use a different life cycle model if it suits them better, but should consider incident response throughout its cyber risk management.

What an incident response plan should contain

NIST says every organization's incident response policy is individual, but most include the same key elements:

  • Management commitment: a statement that leadership backs the effort
  • Purpose: what the policy is for
  • Scope: whom and what it applies to, and under what circumstances
  • Definitions: what terms such as event, incident, and investigation mean
  • Roles, responsibilities, and authorities: for example which roles may confiscate, disconnect, or shut down assets
  • Prioritization guidelines: how to prioritize incidents, estimate severity, and start recovery
  • Performance measures: what is used to measure incident response

Procedures should be based on the policy and the plan. NIST advises documenting procedures for the most common incidents, and for urgent tasks that may be needed mid-crisis, such as redeploying the primary authentication platform. Many organizations write them as playbooks (documents that list the steps people carry out in a given scenario). Rev. 3 points to CISA's playbooks (CISA is the US cybersecurity agency) as examples. The CISA document we read is dated November 2021, was written for US federal civilian executive branch agencies, uses the same phases as Rev. 2, and says future iterations may also be useful to organizations outside that group. Thai organizations should therefore treat it as an example of format, not as a requirement.

Building the plan step by step

The sequence below is our own arrangement of guidance from NIST and the #StopRansomware Guide, written by CISA, NSA, FBI, and MS-ISAC (an information-sharing center for US local governments):

  • Set the policy and delegate authority: write the policy with the elements above and have senior leadership approve it in writing
  • Define the team and stakeholders: besides IT, name HR, facilities, system and data owners, and external providers, and write the providers' duties into the contract
  • Write procedures and playbooks: start with the common incidents, then add the urgent tasks
  • Set prioritization criteria: use factors such as asset criticality, functional and data impact, stage of the attack, and recoverability
  • Prepare fallback channels: keep a hard copy and an offline copy of the plan, and have a communication channel outside the systems that may be attacked, such as phone calls
  • Exercise and improve: exercise the plan periodically, then fix what you find in both the plan and the procedures
INFOGRAPHIC
Building the plan in six steps
1
Policy and authority
leadership approves in writing
2
Team and stakeholders
not only IT; include external providers
3
Procedures and playbooks
start with the common incidents
4
Prioritization criteria
by risk factors, not first come first served
5
Fallback channels
hard copy, offline copy, and phone calls
6
Exercise and improve
fix both plan and procedures

NIST describes external providers as a shared responsibility, so the organization must know what each provider may do on its behalf and what limits apply, such as shutting down a service on its own to contain an incident. If ransomware is the incident you worry about, continue with How to Prevent Ransomware: 5 First Steps for Organizations and Ransomware Recovery Plan: RTO, RPO and Rehearsals, then use Ransomware Tabletop Exercise Template: Ready Scenario to rehearse the plan with your team.

Common mistakes

  • Treating it as the IT team's job alone: Rev. 3 notes that many teams and third parties hold roles, such as HR, facilities, system owners, and service providers
  • Not saying who may disconnect the network or shut down systems: during an incident, time is lost waiting for someone to decide
  • Handling incidents first come, first served: NIST says not to, because resources are limited; prioritize by risk factors instead
  • Letting an outside provider take on work without defining its duties in the contract: nobody knows who must do what, or who can give orders
  • Waiting for recovery to finish before summarizing lessons: NIST says lessons should be shared as soon as they are found
INFOGRAPHIC
Stumbling response versus a prepared one

Stumbling

  • No named decision-makertime lost waiting for a decision mid-incident
  • First come, first servedcritical cases can sit at the back of the queue
  • Lessons only at the endnew knowledge reaches the team late

Prepared

  • Authority is namedeveryone knows who may disconnect or shut down
  • Prioritized by riskasset criticality, impact, and recoverability
  • Lessons shared at oncefed back into the plan while the incident is still open

Start today

  • Check whether a written incident response policy approved by leadership exists
  • List the names and phone numbers of people to notify first, and say which roles may disconnect the network or shut down systems
  • Print the plan and keep an offline copy outside the main systems
  • Pick one common incident type and write a short playbook, using CISA's examples for the format
  • Schedule a tabletop exercise (a talk-through of a made-up scenario) with the people who have roles in the plan

To see how ready your organization is overall, try our self-assessment.

If you need to preserve evidence while responding to an incident, see the collection principles and chain of custody in Digital Forensics Basics: Preserve Evidence Properly.

Thai organizations that hold personal data must also decide when to report a breach to the PDPC; see PDPA Security Measures: A Guide for Security Teams.

References and further reading