Engineer working on a laptop connected to a device test rig, surrounded by wiring harnesses and test hardware

Firmware vulnerabilities & fixes

ISO/IEC 27035 (information security incident management), explained

Last updated:

ISO/IEC 27035 is the multi-part International Standard, developed by ISO/IEC JTC 1/SC 27, that provides the process-level detail behind "incident management" as a control topic — the step-by-step guidance that ISO/IEC 27001 and ISO/IEC 27002 reference but don't themselves spell out. Its two foundational parts were substantially revised in 2023; a newer fourth part, on multi-party coordination, followed in 2024. Unlike the firmware- and device-specific standards covered elsewhere on this site, ISO/IEC 27035 is organization-level process guidance — it describes how to run incident management, not which technical controls a product must implement.

Key takeaways

  • Part 1 separates an event from an incident.
  • Part 2 is the planning manual.
  • Part 1 and Part 2 cover one organization.
  • ISO/IEC 27035 is about incidents; product vulnerabilities have their own standards.

What do the four parts of ISO/IEC 27035 cover?

Part Title Current edition Published
1 Principles and process ISO/IEC 27035-1:2023 (2nd ed., 33 pp.) 2023-02-13
2 Guidelines to plan and prepare for incident response ISO/IEC 27035-2:2023 (2nd ed., 53 pp.) 2023-02-13
3 Guidelines for ICT incident response operations ISO/IEC 27035-3:2020 (1st ed., 31 pp.) 2020-09
4 Coordination ISO/IEC 27035-4:2024 (1st ed., 22 pp.) 2024

Per ISO's own abstract, Part 1 is "the foundation of the ISO/IEC 27035 series." Parts 1 and 2 were both revised on the same date, 2023-02-13, superseding their 2016 editions — ISO's catalogue marks ISO/IEC 27035-1:2016 as withdrawn that day. The Part 1 preview lists the main changes: new terms "incident management team" and "incident coordinator," new subclauses 4.5 to 4.7 on capability, communication and documentation, an updated Annex C and a new Annex D. Part 3 has no prior edition and is new as of 2020; ISO's catalogue currently flags it as under review (stage 90.60, "Close of review," on the iTeh catalogue record), meaning it has not been updated to match the 2023 revision of Parts 1-2. Part 4 is the newest addition, covering guidance for organizations that must coordinate incident handling with other parties.

What is the five-phase process model?

ISO/IEC 27035-1:2023's Clause 5 ("Process") lays out an incident management lifecycle across five activity phases, following an initial overview sub-clause:

  1. 5.2 Plan and prepare
  2. 5.3 Detect and report
  3. 5.4 Assess and decide
  4. 5.5 Respond
  5. 5.6 Learn lessons

Part 2 explicitly anchors its own scope to two of these phases: it "provides guidelines to plan and prepare for incident response and to learn lessons from incident response," based on "the 'plan and prepare' and 'learn lessons' phases of the information security incident management phases model presented in ISO/IEC 27035-1:2023" — citing clauses 5.2 and 5.6 by number. Part 3's scope, covering "information security incident detection, reporting, triage, analysis, response, containment, eradication, recovery and conclusion," states that it is "based on the 'Detection and reporting' phase, the 'Assessment and decision' phase and the 'Responses' phase" of the phases model in ISO/IEC 27035-1:2016, the previous edition of Part 1. Those three phases correspond to the 2023 edition's detect/assess/respond phases (5.3-5.5). Part 3 is also explicit about what it excludes: it "is not concerned with non-ICT incident response operations such as loss of paper-based documents," scoping it firmly to technical/ICT incident handling.

Which roles and records does Part 1 define?

Part 1 separates an event from an incident. An information security event is an "occurrence indicating a possible breach of information security or failure of controls"; an incident is one or more related events "that can harm an organization's assets or compromise its operations." Clause 4.1 adds that "not all information security events are classified as information security incidents," which is why the assess and decide phase exists. The roles and records in Clauses 3 and 4.7 map onto a device maker's organization like this:

ISO/IEC 27035-1 term Definition (paraphrased from Clause 3) Typical holder at a device maker
Incident management team (IMT) Leads all incident management activities and coordinates with internal and external parties Security lead, product security, IT, legal, communications
Incident response team (IRT) Responds to and resolves incidents; there can be several IT/CSIRT for corporate systems; PSIRT and firmware engineers for product issues
Incident coordinator Leads all incident response activities and coordinates the IRT Named on-call lead per incident
Point of contact (PoC) The role to which events are raised Security mailbox, PSIRT intake
Event report, incident management log, incident report, incident register (4.7.2-4.7.5) The four documentation types Ticket, timeline, closing report, register of all incidents

What does Part 2 ask you to prepare?

Part 2 is the planning manual. Its contents list what an organization should have before the first incident:

  • an incident management policy with top-management commitment (Clause 4) and updated security policies (Clause 5);
  • an incident management plan, including an incident classification scale (6.5), incident forms (6.6) and documented procedures (6.7);
  • an IMT and one or more IRTs with defined roles and competencies (Clause 7);
  • internal and external relationships (Clause 8), the list Part 4 reuses;
  • technical support, awareness and training (Clauses 9 and 10);
  • exercises and capability monitoring with metrics (Clause 11);
  • a learn-lessons process, including IMT evaluation (Clause 12).

Its informative annexes give example forms for events, incidents and vulnerability reports (Annex B) and example approaches to categorizing and prioritizing events and incidents (Annex C).

What does Part 4 add for incidents that span several organizations?

Part 1 and Part 2 cover one organization. Part 4 covers "multiple organizations handling information security incidents in a coordinated manner," and defines coordinated incident management as the "process for IRTs from multiple organizations to work together." It runs the same five phases with "coordinated" in front of each name. Clause 4.2 describes a coordination team (a national or sector CSIRT, for example) with a defined "service constituency" that acts "as a central point," and Clause 4.3 sets four principles:

  1. Timeliness:agree time requirements for each item before coordinating.
  2. Roles and responsibilities:each party knows its role, with criteria for who leads a given incident.
  3. Common understanding:shared vocabulary, taxonomy and data exchange formats.
  4. Confidentiality:protect business and personal information shared with outside parties, with rules agreed with legal.

For a device maker, the typical multi-party case is a vulnerability in a supplier's chip SDK that is being exploited at several OEMs' customers at once.

Where does incident management hand off to the PSIRT?

ISO/IEC 27035 is about incidents; product vulnerabilities have their own standards. Part 1's Introduction says the series "covers some aspects of information security vulnerabilities," and points to ISO/IEC 29147 (vulnerability disclosure) and ISO/IEC 30111 (vulnerability handling) for vendors. Part 4 repeats that pointer and adds ISO/IEC TR 5895 for multi-party vulnerability coordination. See our ISO/IEC 29147 and 30111 guide.

Situation Lead process Lead team
Your build server or update infrastructure is compromised ISO/IEC 27035 incident IMT / corporate IRT
A researcher reports a flaw in shipped firmware ISO/IEC 30111 handling, 29147 disclosure PSIRT
A flaw in shipped firmware is being exploited at customers Both: the PSIRT owns the fix and advisory; the IMT owns coordination, evidence and reporting PSIRT and IMT together
An incident investigation finds a product flaw Hand-off from IRT to PSIRT, logged in the incident management log IRT → PSIRT

The EU adds deadlines to the third row. Under Article 14 of the Cyber Resilience Act, applying since 11 September 2026, a manufacturer notifies an actively exploited vulnerability, and separately a severe incident affecting product security, to the CSIRT designated as coordinator and to ENISA: an early warning within 24 hours, a notification within 72 hours, and a final report within 14 days after a fix is available (vulnerabilities) or within one month of the notification (incidents). Put those clocks in the assess and decide phase so they start when you become aware. Our guides on CRA 24-hour reporting, setting up a PSIRT and the FIRST PSIRT Services Framework cover the product side.

How does it plug into ISO/IEC 27001 and 27002?

ISO/IEC 27035-1:2023 states its relationship to the ISMS standards directly, rather than leaving it to inference. Its Introduction says "the ISO/IEC 27035 series provides additional guidance to the controls on incident management in ISO/IEC 27002," and Clause 4.2 adds that the standard aims "to provide guidance to organizations that aim to meet the information security management system (ISMS) requirements specified in ISO/IEC 27001 which are supported by guidance from ISO/IEC 27002," since "ISO/IEC 27001 includes requirements related to information security incident management." Clause 4.2 also says "Table C.1 provides cross-references on information security incident management clauses from ISO/IEC 27001 and clauses in this document"; the table of contents titles Annex C "Cross-reference table of ISO/IEC 27001 to the ISO/IEC 27035 series." The table itself sits beyond the publicly available preview pages.

The specific control titles on the ISO/IEC 27002:2022 side are 5.24, "Information security incident management planning and preparation," and 5.26, "Response to information security incidents" — taken directly from ISO/IEC 27002:2022's own table of contents. In practice, Annex A of ISO/IEC 27001:2022 and the corresponding ISO/IEC 27002:2022 control text establish that an ISMS must plan for and respond to incidents; ISO/IEC 27035 is where the process detail — who does what, in which order, with which artifacts — actually lives.

How does it compare with NIST SP 800-61, and what do NIS2 and the CRA say?

Anyone comparing ISO/IEC 27035 to NIST's incident-handling guidance should note that the NIST side of the comparison recently changed shape. SP 800-61 Revision 2, "Computer Security Incident Handling Guide" (originally August 2012), was withdrawn by NIST on 3 April 2025 and superseded by SP 800-61 Revision 3, retitled "Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile" (April 2025) — a shift from a standalone incident-handling playbook toward a profile mapped against the NIST Cybersecurity Framework 2.0. No ENISA, NIST or national-agency document offers a formal, phase-by-phase crosswalk between ISO/IEC 27035 and either NIST revision; treat any such mapping seen on a vendor blog as an informal convenience comparison, not an authoritative equivalence. Our NIST SP 800-61 guide covers the NIST side.

On EU regulatory status: ENISA's own Cyber Resilience Act Requirements Standards Mapping (JRC137340, 2024) does not mention ISO/IEC 27035 anywhere in its 69-page text. ENISA's June 2025 Technical Implementation Guidance on NIS2's cybersecurity risk-management measures does cite it, but only in supplementary footnotes to its Incident Handling section — footnote 18 notes "the ISO/IEC 27035 series provides further guidance on incident management," citing Part 1, and footnote 33 lists Parts 1 and 2 alongside NIST SP 800-61 Rev. 2 as material to "consider" in addition to ENISA's own normative mapping table. Neither reference elevates ISO/IEC 27035 to a binding or presumption-of-conformity standard under NIS2 or the CRA — it's ENISA-endorsed supplementary guidance, not a named legal requirement in either law's operative text.

What does one incident look like, phase by phase?

Worked example (synthetic; the company, dates and findings are invented for illustration). A camera maker's PSIRT intake receives a customer report of units rebooting and opening an unexpected outbound connection.

  1. Detect and report (5.3):the PoC logs an event report at 09:10 on day 1 and opens an incident management log.
  2. Assess and decide (5.4):the IRT confirms an exploited command-injection flaw in the web UI on firmware 4.1.x; the incident coordinator classifies it high on the Part 2 scale. Because it is an actively exploited product vulnerability, the CRA clock is treated as started at 11:30 and the 24-hour early warning is sent on day 2 at 08:00.
  3. Hand-off:the PSIRT takes the flaw under its ISO/IEC 30111 process; the IMT keeps customer communication, evidence and regulator reporting.
  4. Respond (5.5):the PSIRT issues a mitigation (disable remote web UI), the 72-hour notification goes out, and fixed firmware 4.1.7 ships on day 9 with an advisory.
  5. Coordinate (Part 4):the flaw sits in a supplier's web server SDK, so the maker contacts the supplier and the coordinating CSIRT under agreed time limits and confidentiality rules.
  6. Learn lessons (5.6):the final report is filed within 14 days of the fix; the incident report records root cause, the register is updated, and the build adds a check for the vulnerable SDK version.

What is a workable starting point?

  1. Use Part 1's five phases as your incident runbook skeleton, with one owner and one record per phase.
  2. Pair Part 2 with your ISMS planning cycleBecause Part 2 is explicitly scoped to the "plan and prepare" and "learn lessons" phases, it's the part to read before (and after) an incident, not during one — Part 3 is the during-incident operational guide.
  3. Cite the ISO/IEC 27002:2022 control numbers preciselyIf your Statement of Applicability references incident management, use 5.24 (planning and preparation) and 5.26 (response) rather than a generic "incident management control" — auditors will expect the specific control numbers.
  4. Write the PSIRT hand-off downDefine which events go to the PSIRT, who owns regulator reporting, and how the incident log references the vulnerability case.
  5. Don't claim ISO/IEC 27035 satisfies NIS2 or CRA incident-reporting obligations on its ownENISA's footnote treatment makes it supplementary good practice, not a named conformity mechanism — the actual reporting-timeline obligations live in the regulations themselves.
  6. Check Part 3's review status before relying on 2020-dated languagefor ICT incident response operations — it predates the 2023 revision of Parts 1-2 and may be revised to match.

Common pitfalls: running product vulnerabilities through the IT ticket queue with no PSIRT owner; classifying every event as an incident, which buries real ones; starting the CRA clock at the fix instead of at awareness; and skipping the learn-lessons phase once the patch ships.

SoftWSP does not run your incident process. For product-vulnerability cases in the assess and respond phases, it can extract a CycloneDX 1.6 SBOM from a firmware image, match its components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and draft a cited report that an engineer reviews; watchlist alerts can follow a CVE ID or a vendor and product. Exploitability and reachability decisions stay with your engineers. See Device & Firmware Security.

This guide summarizes publicly available ISO catalogue, front-matter and ENISA/NIST guidance material; ISO/IEC 27035's full operative text (including Annex C) is copyrighted and must be purchased from ISO, IEC or a national member body. This guide is not a substitute for the full standard or for compliance/legal advice.

Put this guide to work

Frequently asked questions

What is ISO/IEC 27035, and what does each part cover?

ISO/IEC 27035 is a multi-part International Standard, developed by ISO/IEC JTC 1/SC 27, on information security incident management. Per ISO's own catalogue, the current parts are: Part 1, "Principles and process" (ISO/IEC 27035-1:2023, 2nd edition, published 2023-02-13, 33 pages), which ISO describes as "the foundation of the ISO/IEC 27035 series," presenting "basic concepts, principles and process with key activities of information security incident management"; Part 2, "Guidelines to plan and prepare for incident response" (ISO/IEC 27035-2:2023, 2nd edition, also published 2023-02-13, 53 pages); Part 3, "Guidelines for ICT incident response operations" (ISO/IEC 27035-3:2020, 1st edition, published September 2020, 31 pages), which covers "information security incident detection, reporting, triage, analysis, response, containment, eradication, recovery and conclusion" and explicitly excludes "non-ICT incident response operations such as loss of paper-based documents"; and Part 4, "Coordination" (ISO/IEC 27035-4:2024, 1st edition, 22 pages), covering guidelines for organizations that must coordinate incident handling across multiple parties. Parts 1 and 2 superseded the 2016 editions of the same parts on their 2023-02-13 publication date, per ISO's catalogue withdrawal records; Part 3 has no prior edition, and Part 3 is separately flagged in ISO's catalogue as currently under review, so it has not been refreshed to match the 2023 revision of Parts 1-2. ISO/IEC 27035 is copyrighted; full text must be purchased from ISO, a national member body, or an authorized reseller — this guide summarizes publicly available catalogue and front-matter material rather than reproducing the operative text.

What is the five-phase incident management process, and where does it come from?

ISO/IEC 27035-1:2023's Clause 5 ("Process") sets out an information security incident management process built around five activity phases, after an initial overview sub-clause: 5.2 Plan and prepare, 5.3 Detect and report, 5.4 Assess and decide, 5.5 Respond, and 5.6 Learn lessons. ISO/IEC 27035-2:2023 explicitly anchors itself to two of those phases, stating in its own scope that it "provides guidelines to plan and prepare for incident response and to learn lessons from incident response," based on "the 'plan and prepare' and 'learn lessons' phases of the information security incident management phases model presented in ISO/IEC 27035-1:2023" (cited by 27035-2 to 27035-1 clauses 5.2 and 5.6 specifically). ISO/IEC 27035-3:2020's scope — covering detection, reporting, triage, analysis, response, containment, eradication, recovery and conclusion — is itself "based on the 'Detection and reporting' phase, the 'Assessment and decision' phase and the 'Responses' phase" of the phases model in ISO/IEC 27035-1:2016, the previous edition of Part 1; those correspond to the 2023 edition's detect/assess/respond phases (5.3-5.5). Some secondary summaries render the phase names as noun phrases ("detection and reporting," "assessment and decision," "lessons learnt") rather than ISO's own verb-phrase clause titles quoted above — both describe the same five-phase model, but only the verb-phrase form reflects ISO's literal Clause 5 titles.

How does ISO/IEC 27035 relate to ISO/IEC 27001 Annex A and ISO/IEC 27002?

ISO/IEC 27035-1:2023 states its own relationship to the ISMS standards directly. Its Introduction says "the ISO/IEC 27035 series provides additional guidance to the controls on incident management in ISO/IEC 27002," and its Clause 4.2 adds that "another objective associated with this document is to provide guidance to organizations that aim to meet the information security management system (ISMS) requirements specified in ISO/IEC 27001 which are supported by guidance from ISO/IEC 27002," noting that "ISO/IEC 27001 includes requirements related to information security incident management" and that the standard's own Annex C contains a table (Table C.1) that "provides cross-references on information security incident management clauses from ISO/IEC 27001 and clauses in this document." The specific ISO/IEC 27002:2022 controls this maps to are 5.24, "Information security incident management planning and preparation," and 5.26, "Response to information security incidents" — both titles taken from ISO/IEC 27002:2022's own table of contents. In short: ISO/IEC 27001 Annex A and ISO/IEC 27002 state *that* an ISMS must manage incidents and name the control titles; ISO/IEC 27035 is where the step-by-step process guidance for doing so actually lives. See our guide to [ISO/IEC 27001:2022](/guides/iso-iec-27001-isms-requirements/) for the ISMS clause structure and Annex A control themes this plugs into.

How does ISO/IEC 27035 compare to NIST SP 800-61, and does NIS2 or the CRA name it?

NIST's own incident-response guidance has recently moved past direct comparability: SP 800-61 Revision 2 ("Computer Security Incident Handling Guide," originally August 2012) was withdrawn by NIST on 3 April 2025 and superseded by SP 800-61 Revision 3, retitled "Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile" (April 2025) — a shift from a standalone incident-handling playbook to a profile mapped against the NIST Cybersecurity Framework 2.0. No ENISA, NIST or national-agency document provides a formal phase-by-phase crosswalk between ISO/IEC 27035 and either NIST revision; comparisons of that kind exist mainly on vendor and compliance blogs, which this guide does not treat as authoritative. On EU law: ENISA's own Cyber Resilience Act Requirements Standards Mapping (JRC137340, 2024) does not mention ISO/IEC 27035 anywhere in its text. ENISA's June 2025 Technical Implementation Guidance on the NIS2 Directive's cybersecurity risk-management measures does name it, but only in supplementary footnotes to its Incident Handling section — footnote 18 states "the ISO/IEC 27035 series provides further guidance on incident management," citing ISO/IEC 27035-1:2023, and footnote 33 lists both ISO/IEC 27035-1:2023 and -2:2023 alongside NIST SP 800-61 Rev. 2 as material to "consider" in addition to ENISA's own normative mapping table. Neither footnote makes ISO/IEC 27035 a binding or presumption-of-conformity mechanism under NIS2 or the CRA — treat it as ENISA-endorsed supplementary guidance, not a named legal requirement.

Sources

  1. ISO: ISO/IEC 27035-1:2023 — Information security incident management — Part 1: Principles and process (catalogue record: edition, date, pages, scope)
  2. ISO: ISO/IEC 27035-2:2023 — Part 2: Guidelines to plan and prepare for incident response (catalogue record)
  3. ISO: ISO/IEC 27035-3:2020 — Part 3: Guidelines for ICT incident response operations (catalogue record)
  4. ISO: ISO/IEC 27035-4:2024 — Part 4: Coordination (catalogue record)
  5. ISO: ISO/IEC 27035-1:2016 (withdrawn 2023-02-13) — catalogue record showing supersession by the 2023 edition
  6. iTeh Standards: ISO/IEC 27035-1:2023 front-matter preview — Introduction and Clause 4.2 text on the relationship to ISO/IEC 27001/27002 and Annex C cross-reference table
  7. iTeh Standards: ISO/IEC 27002:2022 front-matter preview — control 5.24 and 5.26 titles
  8. iTeh Standards: ISO/IEC 27035-2:2023 preview — scope and contents (Clauses 4-12, Annexes A-C)
  9. iTeh Standards: ISO/IEC 27035-3:2020 catalogue record — stage 90.60 and scope
  10. iTeh Standards: ISO/IEC 27035-3:2020 preview — scope based on the ISO/IEC 27035-1:2016 phases
  11. iTeh Standards: ISO/IEC 27035-4:2024 preview — scope, coordination team and principles of coordination
  12. Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex — Article 14 reporting obligations
  13. NIST CSRC: SP 800-61 Rev. 2, Computer Security Incident Handling Guide — withdrawn 2025-04-03, superseded by Rev. 3
  14. NIST CSRC: SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile (April 2025)
  15. ENISA/JRC: Cyber Resilience Act Requirements — Standards Mapping (JRC137340, 2024) — does not mention ISO/IEC 27035
  16. ENISA: Technical implementation guidance on cybersecurity risk management measures (NIS2), v1.0, June 2025 — footnotes 18 and 33 citing ISO/IEC 27035-1/-2 and NIST SP 800-61 Rev. 2
Was this guide helpful?

In this cluster