Skip to content
Incident Response Plan Templates

Standards mapChecked 16 November 2026

Which NIST and ISO clauses does each incident response plan section answer?

Read how the map was madeDownload the data

Which standards does each plan section answer?

The table below is the map. The NIST column uses the outcomes that NIST SP 800-61 Rev. 3 (April 2025) assigns to incident response. The ISO/IEC 27001:2022 column gives Annex A control numbers that NIST lists as informative references for those outcomes.

Plan sections mapped to standards
Plan sectionNIST CSF 2.0 outcomesISO/IEC 27001:2022 Annex A control numbersISO/IEC 27035CISA playbook phaseSANS phase
1 Purpose, scope and authorityGV.PO-01, GV.PO-02, ID.IM-04, GV.RR-025.1, 5.24, 5.26, 5.27Part 1, 5.2 plan and prepare. Part 2 abstract: incident management policy and commitment of top management; incident management planPreparation: policies and procedures2 Preparation: policy
2 Roles and responsibilitiesGV.RR-01, GV.RR-02, PR.AT-025.2, 5.4, 6.3Part 1, 5.2 plan and prepare. Part 2 abstract: Incident Management Team establishmentPreparation: trained response personnel; coordination lead2 Preparation: team and roles
3 Contact and escalation sheetRS.CO-02, RS.CO-03, GV.SC-085.26Part 1, 5.2 plan and prepare. Part 2 abstract: relationships with internal and external organizationsPreparation: communications and logistics2 Preparation: communication
4 Severity levelsRS.MA-03, DE.AE-04, RS.AN-085.25Part 1, assessment and decisions phase (clause number not read)Detection and analysis: determine scope and type2 Preparation: response plan, prioritization by impact
5 Detecting, reporting and declaring an incidentDE.CM-01, DE.AE-02, DE.AE-03, DE.AE-06, DE.AE-08, RS.MA-025.24, 5.25, 5.26, 5.27, 5.28, 6.8, 8.15, 8.16Part 1, detection and reporting phase (clause number not read)Detection and analysis: declare incident3 Identification
6 Triage and analysisRS.MA-02, RS.MA-03, RS.AN-03, RS.AN-08, DE.AE-045.24, 5.25, 5.26, 5.27, 5.28, 6.8Part 1, assessment and decisions phase (clause number not read)Detection and analysis: collect and preserve data; determine scope3 Identification
7 ContainmentRS.MI-01, RS.MA-045.26Part 1, responses phase (clause number not read)Containment4 Containment
8 Eradication and recoveryRS.MI-02, RS.MA-05, RC.RP-01, RC.RP-02, RC.RP-03, RC.RP-04, RC.RP-05, RC.RP-065.25, 5.26, 5.27, 8.13Part 1, responses phase (clause number not read)Eradication and recovery5 Eradication and 6 Recovery
9 CommunicationsRS.CO-02, RS.CO-03, RC.CO-03, RC.CO-045.26, 5.28Part 1, reporting and responses phases (clause numbers not read)Coordination2 Preparation: communication; 3 Identification: notify the team
10 Legal, regulatory, contractual and insurance noticesGV.OC-03, RS.CO-025.20, 5.26, 5.31Part 1, 5.2 plan and prepare (legal and regulatory context; clause detail not read)Post-incident activities: finalize reports as required by law and policy2 Preparation: communication, law enforcement
11 Evidence handling and documentationRS.AN-06, RS.AN-075.28Part 1, assessment and responses phases (clause numbers not read)Detection and analysis: collect and preserve data2 Preparation: documentation; 3 Identification
12 Third parties and suppliersGV.SC-08, DE.CM-06, RS.MA-015.22, 5.26, 5.27, 5.28, 8.16Part 1, 5.2 plan and prepare. Part 2 abstract: relationships with external organizationsCoordination; eradication: coordinate with ICT service providers2 Preparation: communication
13 Post-incident reviewID.IM-03, ID.IM-04, RC.RP-065.24, 5.26, 5.27, 8.13Part 1, 5.6 learn lessons. Part 2 abstract: identify and make improvements; Incident Response Team evaluationPost-incident activities: perform hotwash7 Lessons Learned
14 Testing, training and keeping the plan currentID.IM-02, ID.IM-04, PR.AT-02, GV.PO-025.1, 5.2, 5.19, 5.24, 5.26, 5.27, 5.35, 6.3Part 1, 5.2 plan and prepare. Part 2 abstract: awareness briefings and trainingPreparation: trained response personnel; COOP testing2 Preparation: training
15 Appendices: formsRS.AN-06, RC.RP-065.27, 5.28, 8.13Part 1, assessment and lessons phases (clause numbers not read)Appendix B: incident response checklist8 Incident Handlers Checklist

What do the CSF outcome codes mean?

Each code is a CSF 2.0 outcome. The prefix is the Function (GV Govern, ID Identify, PR Protect, DE Detect, RS Respond, RC Recover) and the next two letters the category, for example RS.MA is Incident Management.

CSF 2.0 outcomes used
OutcomeText (NIST CSF 2.0)
GV.PO-01Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
GV.PO-02Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
ID.IM-04Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
GV.RR-01Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving
PR.AT-02Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
RS.CO-02Internal and external stakeholders are notified of incidents
RS.CO-03Information is shared with designated internal and external stakeholders
GV.SC-08Relevant suppliers and other third parties are included in incident planning, response, and recovery activities
RS.MA-03Incidents are categorized and prioritized
DE.AE-04The estimated impact and scope of adverse events are understood
RS.AN-08An incident's magnitude is estimated and validated
DE.CM-01Networks and network services are monitored to find potentially adverse events
DE.AE-02Potentially adverse events are analyzed to better understand associated activities
DE.AE-03Information is correlated from multiple sources
DE.AE-06Information on adverse events is provided to authorized staff and tools
DE.AE-08Incidents are declared when adverse events meet the defined incident criteria
RS.MA-02Incident reports are triaged and validated
RS.AN-03Analysis is performed to establish what has taken place during an incident and the root cause of the incident
RS.MI-01Incidents are contained
RS.MA-04"Incidents are escalated or elevated as needed"
RS.MI-02Incidents are eradicated
RS.MA-05The criteria for initiating incident recovery are applied
RC.RP-01The recovery portion of the incident response plan is executed once initiated from the incident response process
RC.RP-02Recovery actions are selected, scoped, prioritized, and performed
RC.RP-03The integrity of backups and other restoration assets is verified before using them for restoration
RC.RP-04Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms
RC.RP-05The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed
RC.RP-06The end of incident recovery is declared based on criteria, and incident-related documentation is completed
RC.CO-03Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
RC.CO-04Public updates on incident recovery are shared using approved methods and messaging
GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed
RS.AN-06Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved
RS.AN-07Incident data and metadata are collected, and their integrity and provenance are preserved
DE.CM-06External service provider activities and services are monitored to find potentially adverse events
RS.MA-01The incident response plan is executed in coordination with relevant third parties once an incident is declared
ID.IM-03Improvements are identified from execution of operational processes, procedures, and activities
ID.IM-02Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties

Which CSF categories are covered?

The plan draws on categories from five Functions. Incident Management (RS.MA), Incident Analysis (RS.AN), Incident Response Reporting and Communication (RS.CO), Incident Mitigation (RS.MI) and Incident Recovery Plan Execution (RC.RP) carry most of the response work.

Categories used
CategoryName
GV.OCOrganizational Context
GV.RRRoles, Responsibilities, and Authorities
GV.POPolicy
GV.SCCybersecurity Supply Chain Risk Management
ID.IMImprovement
PR.ATAwareness and Training
DE.CMContinuous Monitoring
DE.AEAdverse Event Analysis
RS.MAIncident Management
RS.ANIncident Analysis
RS.COIncident Response Reporting and Communication
RS.MIIncident Mitigation
RC.RPIncident Recovery Plan Execution
RC.COIncident Recovery Communication

Cite this

Incident Response Plan Templates, "Incident Response Plan Standards Map", edition 16 November 2026, https://incidentresponseplantemplates.com/standards-map/. Data: CSV, JSON.

Sources

  1. NIST SP 800-61 Rev. 3, full text (April 2025)
  2. NIST CSF 2.0 Reference Tool download, with ISO/IEC 27001:2022 informative references
  3. ISO/IEC 27035-1:2023 on iso.org
  4. ISO/IEC 27035-2:2023 on iso.org
  5. ISO/IEC 27001:2022 on iso.org
  6. CISA, Cybersecurity Incident & Vulnerability Response Playbooks (November 2021)
  7. SANS Institute, Incident Handler's Handbook (21 February 2012)

Last reviewed 16 November 2026. Each source above was read that day.