IRO-02: Incident Response Operations
Mechanisms exist to implement and govern processes and documentation to facilitate an organization-wide response capability for cybersecurity and data protection-related incidents.
Renumbered: Formerly IRO-01 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, IRO-02 was Incident Handling. That control is now IRO-06.
Control Question: Does the organization implement and govern processes and documentation to facilitate an organization-wide response capability for cybersecurity and data protection-related incidents?
General (53)
US (31)
EMEA (24)
APAC (9)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-0137 ISM-0576 ISM-1609 ISM-1618 |
| APAC Australia Prudential Standard CPS230 2023 | 16(d) |
| APAC Australia Prudential Standard CPS234 2019 | 23.0 |
| APAC India SEBI CSCRF 2024 | RS.MA.S1 |
| APAC Japan ISMAP | 16.0 16.1 16.1.1.2 16.1.1.4 16.1.1.5 16.1.1.6.P 16.1.1.7.P 16.1.1.8.P 16.1.1.9.P 16.1.1.10.P 16.1.1.11.P 16.1.1.12.P |
| APAC Malaysia RMiT 2025 | 9.2(k) 11.12 12.3(e) A7-D1(e) A10-B14(a) |
| APAC New Zealand NZISM 3.9 | 7.1.7.C.01 7.1.7.C.02 7.1.7.C.03 7.2.18.C.01 |
| APAC Singapore CCOP CII 2026 | 6.2.1(d) |
| APAC Singapore MAS TRM 2021 | 7.7.1 7.7.2 |
Americas (5)
| Framework | Mapping Values |
|---|---|
| Americas Argentina Reg 132 2018 | E.1.2-11 G |
| Americas Bermuda BMACCC 2020 | 5.3-BP3 6.1-BP4 6.3 6.4 |
| Americas Canada ITSP-10-171 2025 | 03.06.01 |
| Americas Canada OSFI B-13 2022 | 2.7 2.7.2 3.3 3.4.1 |
| Americas Canada OSFI Self-Assessment Guidance | 2.7.1 3.4.3 |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
Incident Response (IRO) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with IRO domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Incident response-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ IT and/or cybersecurity personnel use an informal process to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery.
Level 2 — Planned & Tracked
Incident Response (IRO) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with IRO domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with DCH domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with IRO domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Incident response-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Incident response management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ IT and/or cybersecurity personnel operate an incident response capability using a documented and tested Incident Response Plan (IRP) to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery. ▪ IT and/or cybersecurity personnel facilitate prompt response to suspected or confirmed security incidents, including timely notification to affected stakeholders.
Level 3 — Well Defined
Incident Response (IRO) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with IRO domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Cybersecurity personnel operate an incident response capability using a documented and tested Incident Response Plan (IRP) to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery. ▪ An incident response team, or similar function, is appropriately staffed and supported to implement and maintain IRO domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of incident response operations (e.g., incident management software). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with IRO domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to implement and govern processes and documentation to facilitate an organization-wide response capability for cybersecurity and data protection-related incidents.
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- IRO-02_A01 the rigor of incident handling activities is comparable and predictable across the organization.
- IRO-02_A02 the intensity of incident handling activities is comparable and predictable across the organization.
- IRO-02_A03 the scope of incident handling activities is comparable and predictable across the organization.
- IRO-02_A04 the results of incident handling activities are comparable and predictable across the organization.
- IRO-02_A05 incident handling activities are coordinated with contingency planning activities.
- IRO-02_A06 an operational incident-handling capability is established.
- IRO-02_A07 the operational incident-handling capability includes preparation.
- IRO-02_A08 the operational incident-handling capability includes detection and analysis.
- IRO-02_A09 the operational incident-handling capability includes containment.
- IRO-02_A10 the operational incident-handling capability includes eradication.
- IRO-02_A11 the operational incident-handling capability includes recovery.
- IRO-02_A12 lessons learned from ongoing incident handling activities are incorporated into incident response procedures, training, and testing.
- IRO-02_A13 the changes resulting from the incorporated lessons learned are implemented accordingly.
- IRO-02_A14 an incident-handling capability that is consistent with the incident response plan is implemented.
- IRO-02_A15 incident response management operations are conducted according to documented policies, standards, procedures and/or other organizational directives.
- IRO-02_A16 resources (e.g., people, processes, technologies, data and/or facilities) required to support incident response management operations are identified and provided.
- IRO-02_A17 responsibility and authority for the performance of incident response management-related activities are assigned to designated personnel.
- IRO-02_A18 personnel performing incident response management-related activities have the skills and knowledge needed to perform their assigned duties.
Evidence Requirements
- E-IRO-01 Incident Response Plan (IRP)
-
Documented evidence of a Incident Response Plan (IRP). This is program-level documentation in the form of a runbook, playbook or a similar format provides guidance on organizational practices that support existing policies and standards.
Incident Response
Technology Recommendations
Micro/Small
- Incident Response Plan (IRP)
Small
- Incident Response Plan (IRP)
Medium
- Integrated Incident Response Program (IIRP)
Large
- Integrated Incident Response Program (IIRP)
Enterprise
- Integrated Incident Response Program (IIRP)