IRO-11: Integrated Security Incident Response Team (ISIRT)
Mechanisms exist to establish an integrated team of cybersecurity, IT and business function representatives that are capable of addressing cybersecurity and data protection incident response operations.
Renumbered: Formerly IRO-07 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, IRO-11 was Incident Reporting Assistance. That control is now IRO-18.
Control Question: Does the organization establish an integrated team of cybersecurity, IT and business function representatives that are capable of addressing cybersecurity and data protection incident response operations?
General (29)
US (8)
| Framework | Mapping Values |
|---|---|
| USA Federal C2M2 2.1 | RESPONSE-3a |
| USA Federal CMMC 2.0 Level 3 | IR.L3-3.6.2E |
| USA Federal FFIEC ITEH 2016 | III.D |
| USA Federal FedRAMP R5 (high) | IR-04(11) |
| USA Federal GLBA CFR 314 2023 | 314.4(h)(3) |
| USA Federal NERC CIP 2024 | CIP-008-6 1.3 |
| USA Federal SEC Cybersecurity Rule 2023 | Form 8-K Item 1.05(a) |
| USA Federal TSA SDP 2021-02F | III.F.2 |
EMEA (7)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | SIM-01.02B SIM-03.03B |
| EMEA Spain CCN-STIC 825 | op.exp.9 |
| EMEA EU DORA 2023 | Article 14.1 Article 14.2 Article 14.3 |
| EMEA EU DORA RTS 2024 | Article 22.1(b) Article 23.1 |
| EMEA EU NIS2 Annex 2024 | 3.1.2(c) 3.1.3 3.5.3(a) 4.3.3 |
| EMEA LUX CCSF 20/750 2020 | 3.5.1-60.b |
| EMEA Saudi Arabia OTCC-1 2022 | 2-12-1-4 |
APAC (6)
| Framework | Mapping Values |
|---|---|
| APAC Australia CCM 2026 | RES-05 |
| APAC Australia ISM June 2026 | ISM-0733 ISM-1618 |
| APAC Malaysia RMiT 2025 | 11.13(a) 11.14 A10-B14(d) |
| APAC New Zealand NZISM 3.9 | 7.2.18.C.01 |
| APAC Singapore CCOP CII 2026 | 3.2.2(b)ii 7.1.1 7.1.1(a) 7.1.2 |
| APAC Singapore MAS TRM 2021 | 7.7.5 7.7.6 |
Americas (5)
| Framework | Mapping Values |
|---|---|
| Americas Argentina Reg 132 2018 | G.1.1-2 |
| Americas Bermuda BMACCC 2020 | 6.4 |
| Americas Canada ITSP-10-171 2025 | 03.06.02.B 03.06.02.D |
| Americas Canada OSFI B-13 2022 | 2.7.2 3.3.3 3.4.4 |
| Americas Canada OSFI Self-Assessment Guidance | 3.4.4 |
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
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
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 establish an integrated team of cybersecurity, IT and business function representatives that are capable of addressing cybersecurity and data protection incident response operations.
Level 4 — Quantitatively Controlled
Incident Response (IRO) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.
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-11_A01 an integrated incident response team is established and maintained.
- IRO-11_A02 the time period within which an integrated incident response team can be deployed is defined.
- IRO-11_A03 the cyber incident response team can be deployed by the organization within an organization-defined time period.
- IRO-11_A04 suspected incidents are reported to the organizational incident response capability within an organization-defined time period.
- IRO-11_A05 an incident response support resource that offers advice and assistance to system users on handling and reporting incidents is provided.
- IRO-11_A06 a time period for deploying a cyber incident response team is defined.
- IRO-11_A07 the cyber incident response team can be deployed by the organization within an organization-defined time period.
- IRO-11_A08 the cyber incident response team is maintained.
- IRO-11_A09 suspected incidents are reported to the organizational incident response capability within <A.03.06.02.ODP[01]: time period>.
Evidence Requirements
- E-IRO-09 Formally Assigned Incident Response Roles & Responsibilities
-
Documented evidence of the establishment of a formally-assigned, integrated team of cybersecurity, IT and business function representatives that are capable of addressing cybersecurity & data privacy incident response operations.
Incident Response
Technology Recommendations
Micro/Small
- Basic incident response plan
- Designate incident response contact
Small
- Documented incident response plan
- Incident log
- Designated IR team
Medium
- Integrated Security Incident Response Team (ISIRT)
Large
- Integrated Security Incident Response Team (ISIRT)
Enterprise
- Integrated Security Incident Response Team (ISIRT)