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

Standards map, read 16 November 2026

**The short answer.** The standards map ties each of the fifteen plan sections to NIST CSF 2.0 outcomes such as RS.MA-03, ISO/IEC 27001:2022 Annex A control numbers 5.24 to 5.28 and 6.8, the ISO/IEC 27035 phases, CISA playbook phases and SANS phases. Edition 16 November 2026; downloadable as CSV and JSON.

## 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 section | NIST CSF 2.0 outcomes | ISO/IEC 27001:2022 Annex A control numbers | ISO/IEC 27035 | CISA playbook phase | SANS phase |
| --- | --- | --- | --- | --- | --- |
| 1. Purpose, scope and authority | GV.PO-01, GV.PO-02, ID.IM-04, GV.RR-02 | 5.1, 5.24, 5.26, 5.27 | Part 1, 5.2 plan and prepare. Part 2 abstract: incident management policy and commitment of top management; incident management plan | Preparation: policies and procedures | 2 Preparation: policy |
| 2. Roles and responsibilities | GV.RR-01, GV.RR-02, PR.AT-02 | 5.2, 5.4, 6.3 | Part 1, 5.2 plan and prepare. Part 2 abstract: Incident Management Team establishment | Preparation: trained response personnel; coordination lead | 2 Preparation: team and roles |
| 3. Contact and escalation sheet | RS.CO-02, RS.CO-03, GV.SC-08 | 5.26 | Part 1, 5.2 plan and prepare. Part 2 abstract: relationships with internal and external organizations | Preparation: communications and logistics | 2 Preparation: communication |
| 4. Severity levels | RS.MA-03, DE.AE-04, RS.AN-08 | 5.25 | Part 1, assessment and decisions phase (clause number not read) | Detection and analysis: determine scope and type | 2 Preparation: response plan, prioritization by impact |
| 5. Detecting, reporting and declaring an incident | DE.CM-01, DE.AE-02, DE.AE-03, DE.AE-06, DE.AE-08, RS.MA-02 | 5.24, 5.25, 5.26, 5.27, 5.28, 6.8, 8.15, 8.16 | Part 1, detection and reporting phase (clause number not read) | Detection and analysis: declare incident | 3 Identification |
| 6. Triage and analysis | RS.MA-02, RS.MA-03, RS.AN-03, RS.AN-08, DE.AE-04 | 5.24, 5.25, 5.26, 5.27, 5.28, 6.8 | Part 1, assessment and decisions phase (clause number not read) | Detection and analysis: collect and preserve data; determine scope | 3 Identification |
| 7. Containment | RS.MI-01, RS.MA-04 | 5.26 | Part 1, responses phase (clause number not read) | Containment | 4 Containment |
| 8. Eradication and recovery | RS.MI-02, RS.MA-05, RC.RP-01, RC.RP-02, RC.RP-03, RC.RP-04, RC.RP-05, RC.RP-06 | 5.25, 5.26, 5.27, 8.13 | Part 1, responses phase (clause number not read) | Eradication and recovery | 5 Eradication and 6 Recovery |
| 9. Communications | RS.CO-02, RS.CO-03, RC.CO-03, RC.CO-04 | 5.26, 5.28 | Part 1, reporting and responses phases (clause numbers not read) | Coordination | 2 Preparation: communication; 3 Identification: notify the team |
| 10. Legal, regulatory, contractual and insurance notices | GV.OC-03, RS.CO-02 | 5.20, 5.26, 5.31 | Part 1, 5.2 plan and prepare (legal and regulatory context; clause detail not read) | Post-incident activities: finalize reports as required by law and policy | 2 Preparation: communication, law enforcement |
| 11. Evidence handling and documentation | RS.AN-06, RS.AN-07 | 5.28 | Part 1, assessment and responses phases (clause numbers not read) | Detection and analysis: collect and preserve data | 2 Preparation: documentation; 3 Identification |
| 12. Third parties and suppliers | GV.SC-08, DE.CM-06, RS.MA-01 | 5.22, 5.26, 5.27, 5.28, 8.16 | Part 1, 5.2 plan and prepare. Part 2 abstract: relationships with external organizations | Coordination; eradication: coordinate with ICT service providers | 2 Preparation: communication |
| 13. Post-incident review | ID.IM-03, ID.IM-04, RC.RP-06 | 5.24, 5.26, 5.27, 8.13 | Part 1, 5.6 learn lessons. Part 2 abstract: identify and make improvements; Incident Response Team evaluation | Post-incident activities: perform hotwash | 7 Lessons Learned |
| 14. Testing, training and keeping the plan current | ID.IM-02, ID.IM-04, PR.AT-02, GV.PO-02 | 5.1, 5.2, 5.19, 5.24, 5.26, 5.27, 5.35, 6.3 | Part 1, 5.2 plan and prepare. Part 2 abstract: awareness briefings and training | Preparation: trained response personnel; COOP testing | 2 Preparation: training |
| 15. Appendices: forms | RS.AN-06, RC.RP-06 | 5.27, 5.28, 8.13 | Part 1, assessment and lessons phases (clause numbers not read) | Appendix B: incident response checklist | 8 Incident Handlers Checklist |

Plan sections mapped to standards

## 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.

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

CSF 2.0 outcomes used

## 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.

| Category | Name |
| --- | --- |
| GV.OC | Organizational Context |
| GV.RR | Roles, Responsibilities, and Authorities |
| GV.PO | Policy |
| GV.SC | Cybersecurity Supply Chain Risk Management |
| ID.IM | Improvement |
| PR.AT | Awareness and Training |
| DE.CM | Continuous Monitoring |
| DE.AE | Adverse Event Analysis |
| RS.MA | Incident Management |
| RS.AN | Incident Analysis |
| RS.CO | Incident Response Reporting and Communication |
| RS.MI | Incident Mitigation |
| RC.RP | Incident Recovery Plan Execution |
| RC.CO | Incident Recovery Communication |

Categories used

**Cite this.** Incident Response Plan Templates, "Incident Response Plan Standards Map", edition 16 November 2026, https://incidentresponseplantemplates.com/standards-map/. Data: [CSV](/datasets/incident-response-standards-map.csv), [JSON](/datasets/incident-response-standards-map.json).

## Related

- [How the standards map was read](/standards-map/method/)
- [The general template](/)
- [Incident response plan guide](/plans/)
- [NIST layout template](/templates/incident-response-plan-template-nist/)
- [Datasets](/datasets/)

## Related pages

- [Free incident response plan template](/)
- [The template set](/templates/)
- [Datasets](/datasets/)
- [Incident response plan guide](/plans/)

## Sources

- NIST SP 800-61 Rev. 3, full text (April 2025): https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026)
- NIST CSF 2.0 Reference Tool download, with ISO/IEC 27001:2022 informative references: https://csrc.nist.gov/extensions/nudp/services/json/csf/download?olirids=all (read 16 November 2026)
- ISO/IEC 27035-1:2023 on iso.org: https://www.iso.org/standard/78973.html (read 16 November 2026)
- ISO/IEC 27035-2:2023 on iso.org: https://www.iso.org/standard/78974.html (read 16 November 2026)
- ISO/IEC 27001:2022 on iso.org: https://www.iso.org/standard/82875.html (read 16 November 2026)
- CISA, Cybersecurity Incident & Vulnerability Response Playbooks (November 2021): https://www.cisa.gov/sites/default/files/2024-08/Federal_Government_Cybersecurity_Incident_and_Vulnerability_Response_Playbooks_508C.pdf (read 16 November 2026)
- SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/standards-map/
