MethodChecked 16 November 2026
How the incident response standards map was read
What exactly was read?
Six documents were read in full or in the parts that matter, on 16 November 2026. The table lists each with the identifier or date read and what it was used for.
| Document | Identifier or date read | Used for |
|---|---|---|
| NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile | Published April 2025 (final 3 April 2025); DOI 10.6028/NIST.SP.800-61r3; supersedes Rev. 2 of 6 August 2012 | CSF Function and category structure, outcome text (Tables 2 and 3), roles, policy elements |
| NIST CSF 2.0 Reference Tool download | Informative references to ISO/IEC 27001:2022 per CSF 2.0 subcategory, read 16 November 2026 | Annex A control numbers (5.24 to 5.28, 6.8, 8.13 and others) |
| ISO/IEC 27035-1:2023 and 27035-2:2023, iso.org pages | Edition 2, published February 2023; 33 and 53 pages | Phase names and the clause numbers 5.2 and 5.6, as printed in the 27035-2 abstract |
| ISO/IEC 27001:2022, iso.org page | Published 2022 | Confirms the Annex A numbering context |
| CISA Cybersecurity Incident & Vulnerability Response Playbooks | Publication November 2021 (federal agencies) | Phase names: preparation; detection and analysis; containment; eradication and recovery; post-incident activities; coordination |
| SANS Incident Handler's Handbook | Published 21 February 2012 | Six phases: preparation, identification, containment, eradication, recovery, lessons learned |
Which ISO clause numbers could not be read?
The ISO Online Browsing Platform preview did not load on the read date, so the clause lists of ISO/IEC 27035-1:2023 and 27035-2:2023 were not read. Only what iso.org prints on the standard pages is used: the 27035-2 abstract says its guidance is based on the "plan and prepare" and "learn lessons" phases presented in ISO/IEC 27035-1:2023, 5.2 and 5.6.
The map therefore gives clause numbers 5.2 and 5.6 only, and names the other phases (detection and reporting, assessment and decisions, responses) without clause numbers. ISO/IEC 27001:2022 Annex A control titles were also not read from a page, so the data carries control numbers only, as NIST lists them. Annex A 5.24 to 5.28 and 6.8 appear in the map through those NIST references.
How was each plan section mapped?
Each plan section was matched to the CSF 2.0 outcomes whose text it answers, such as RS.MA-02 (incident reports are triaged and validated) for triage. The ISO column is the union of the Annex A numbers NIST lists for those outcomes. The CISA and SANS columns name the nearest phase in each document. The mapping is our judgment, and the data lets you check it row by row.
Cite this
Incident Response Plan Templates, "Incident Response Plan Standards Map", edition 16 November 2026. Data: CSV, JSON.
Related pages
Sources
- NIST SP 800-61 Rev. 3, publication page (April 2025)
- NIST SP 800-61 Rev. 3, full text (April 2025)
- NIST CSF 2.0 Reference Tool download, with ISO/IEC 27001:2022 informative references
- ISO/IEC 27035-1:2023 on iso.org
- ISO/IEC 27035-2:2023 on iso.org
- ISO/IEC 27001:2022 on iso.org
- CISA, Cybersecurity Incident & Vulnerability Response Playbooks (November 2021)
- SANS Institute, Incident Handler's Handbook (21 February 2012)
Last reviewed 16 November 2026. Each source above was read that day.