Skip to main content

IRO-02: Incident Response Operations

IRO 9 — Critical Govern

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)
Framework Mapping Values
AICPA Privacy Management Framework (PMF) M1.3-POF3
AICPA TSC 2017:2022 (used for SOC 2) (source) A1.2-POF5 CC2.2-POF3 CC2.2-POF10 CC7.3 CC7.3-POF1 CC7.4 CC7.4-POF1 CC7.4-POF2 CC7.4-POF3 CC7.4-POF4 CC7.4-POF5 CC7.4-POF6 CC7.4-POF7 CC7.4-POF8 CC7.4-POF9 CC7.4-POF10 CC7.4-POF11 CC7.4-POF12 CC7.4-POF13
BSI Standard 200-1 4.1.3
CIS CSC 8.1 17 17.5
CIS CSC 8.1 IG2 17.5
CIS CSC 8.1 IG3 17.5
COBIT 2019 DSS02.01
CSA CCM 4.1.0 SEF-01
CSA IoT SCF 2 IMT-01
GovRAMP IR-01
GovRAMP Low IR-01
GovRAMP Low+ IR-01
GovRAMP Moderate IR-01
GovRAMP High IR-01
IEC 62443-2-1 2024 EVENT 1.8
IMO Maritime Cyber Risk Management 3.5.4
ISO/SAE 21434 2021 RQ-13-01 RQ-13-01(a) RQ-13-01(b) RQ-13-01(c) RQ-13-01(d) RQ-13-01(e) RQ-13-01(f) RQ-13-01(g)
ISO 27002 2022 5.24
ISO 27017 2015 16.1.1
ISO 27018 2025 5.24
MPA Content Security Program 5.3.1 OR-4.0
NAIC Insurance Data Security Model Law (MDL-668) 4.C(4)(c)
NIST AI 100-1 (AI RMF) 1.0 GOVERN 6.2 MANAGE 2.3 MANAGE 2.4
NIST 800-53 R4 IR-1
NIST 800-53 R5.2 IR-01
NIST 800-53B R5 (low) (source) IR-01
NIST 800-53B R5 (moderate) (source) IR-01
NIST 800-53B R5 (high) (source) IR-01
NIST 800-53B R5 (privacy) (source) IR-01
NIST SP 800-66 R2 164.308(a)(1) 164.308(a)(6) 164.308(a)(7)
NIST 800-82 R3 IR-01
NIST 800-82 R3 LOW OT Overlay IR-01
NIST 800-82 R3 MODERATE OT Overlay IR-01
NIST 800-82 R3 HIGH OT Overlay IR-01
NIST 800-161 R1 IR-1
NIST 800-161 R1 C-SCRM Baseline IR-1
NIST 800-161 R1 Flow Down IR-1
NIST 800-161 R1 Level 1 IR-1
NIST 800-161 R1 Level 2 IR-1
NIST 800-161 R1 Level 3 IR-1
NIST 800-171 R2 (source) NFO - IR-1
NIST 800-171 R3 (source) 03.06.01
NIST 800-171A (source) 3.6.1[a] 3.6.1[b] 3.6.1[c] 3.6.1[d] 3.6.1[e] 3.6.1[f]
NIST 800-171A R3 (source) A.03.06.01[01]
NIST 800-172 R3 03.11.09E
NIST 800-172A R3 A.03.11.09E.ODP[02]
NIST CSF 2.0 (source) GV.SC-08 DE.AE RS RS.MI
PCI DSS 4.0.1 (source) 10.7 10.7.1 10.7.2 10.7.3 12.10 A3.5
PCI DSS 4.0.1 SAQ D Merchant (source) 10.7.2 10.7.3
PCI DSS 4.0.1 SAQ D Service Provider (source) 10.7.1 10.7.2 10.7.3
SCF DPMP 2026 8.0
Shared Assessments SIG 2025 J.4
SWIFT CSF 2025 6.1 6.2 6.3 7.1
US (31)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 IR-1
USA Federal CISA CPG 2022 2.S 5.A
USA Federal DHS CISA SSDAF 1.f
USA Federal DHS CISA TIC 3.0 3.UNI.IRPIH
USA Federal C2M2 2.1 RESPONSE-1a
USA Federal CERT RMM 1.2 IMC:SG1 IMC:SG1.SP1 IMC:SG1.SP2 IMC:GG1.GP1 IMC:GG2 IMC:GG2.GP2
USA Federal EO 14028 4e(i)(F)
USA Federal CJIS Security Policy 6.0 5.20.5 IR-1
USA Federal FFIEC ITEH 2016 III.D
USA Federal FedRAMP R5 (low) IR-01
USA Federal FedRAMP R5 (moderate) IR-01
USA Federal FedRAMP R5 (high) IR-01
USA Federal FedRAMP R5 (LI-SaaS) IR-01
USA Federal IRS 1075 2021 1.8.4 IR-1
USA Federal GLBA CFR 314 2023 314.4(h) 314.4(h)(1) 314.4(h)(2) 314.4(h)(3) 314.4(h)(4) 314.4(h)(5) 314.4(h)(6) 314.4(h)(7)
USA Federal HIPAA Security Rule NIST SP 800-66 R2 § 164.308(a)(1)(i) § 164.308(a)(6)(i) § 164.308(a)(7)(i)
USA Federal HIPAA Administrative Simplification 2013 § 164.308(a)(1)(i) § 164.308(a)(6)(i) § 164.308(a)(7)(i)
USA Federal NERC CIP 2024 CIP-003-8 1.1.5 CIP-003-8 1.2.4 CIP-008-6 1.1 CIP-008-6 3.2
USA Federal NISPOM 2020 §117.18(b)(2)
USA Federal SEC Cybersecurity Rule 2023 Form 8-K Item 1.05(a)
USA Federal FCA CRM 2023 609.930(c)(3)
USA Federal FINRA 2007 248.30(a)(3)
USA Federal TSA SDP 2021-02F III.D.2.d
USA Federal TSA / DHS 1580/82-2022-01 III.D.2.d
USA California CCPA 2025 7123(c)(17) 7123(c)(17)(B)
USA California SB1386 2002 1798.29(a)
USA Illinois PIPA 2006 12(g) 12(g)(i) 12(g)(ii) 12(g)(iii) 12(g)(iv) 12(g)(v)
USA New York DFS 23 NYCRR500 2023 Amd 2 500.2(b)(4) 500.3(n) 500.16(a)
USA Texas DIR SCSC 2.2 2025 IR-01
USA Texas TX-RAMP Level 1 IR-01
USA Texas TX-RAMP Level 2 IR-01
EMEA (24)
Framework Mapping Values
EMEA CHE FINMA Circular 2023/1 IV.B.d-58
EMEA Germany BAIT 2017 4.7
EMEA Germany C5 2026 AM-05.01B.10 OPS-19.01B SIM-01.01B
EMEA Spain CCN-STIC 825 op.exp.7
EMEA Spain Royal Decree 311 2022 Article 8(4) Article 12(6)(m) Article 25(1)
EMEA EU DORA 2023 Article 9.4(b) Article 14.1 Article 14.2 Article 14.3 Article 17.1 Article 17.2 Article 17.3 Article 17.3(a) Article 17.3(b) Article 17.3(c) Article 17.3(d) Article 17.3(e) Article 17.3(f)
EMEA EU DORA RTS 2024 Article 22.1 Article 22.1(a)
EMEA EU EBA GL/2019/04 3.5.1.59 3.5.1.60
EMEA EU NIS2 2022 Article 21.2(b) Article 23.1
EMEA EU NIS2 Annex 2024 3.1.1 3.2.1 3.5.1 4.3.1
EMEA EU PSD2 2015 95(1)
EMEA UK CAF 4.0 D1
EMEA UK CAP 1850 2020 D1
EMEA UK DEFSTAN 05-138 2024 3105 4104
EMEA UK DEFSTAN 05-138 - L1 2024 4104
EMEA UK DEFSTAN 05-138 - L2 2024 3105 4104
EMEA UK DEFSTAN 05-138 - L3 2024 3105 4104
EMEA LUX CCSF 20/750 2020 3.5.1-59
EMEA Qatar PDPPL 2020 3.11.5
EMEA Saudi Arabia ECC-1 2018 2-13-1 2-13-2 2-13-3-1
EMEA Saudi Arabia OTCC-1 2022 2-12-1 2-12-2
EMEA Saudi Arabia SACS-002 2022 VII.A.TPC-23
EMEA Saudi Arabia SAMA CSF 1.0 2017 3.3.15.1
EMEA UAE NIAF 2023 3.3 3.3.2
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)

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

  1. IRO-02_A01 the rigor of incident handling activities is comparable and predictable across the organization.
  2. IRO-02_A02 the intensity of incident handling activities is comparable and predictable across the organization.
  3. IRO-02_A03 the scope of incident handling activities is comparable and predictable across the organization.
  4. IRO-02_A04 the results of incident handling activities are comparable and predictable across the organization.
  5. IRO-02_A05 incident handling activities are coordinated with contingency planning activities.
  6. IRO-02_A06 an operational incident-handling capability is established.
  7. IRO-02_A07 the operational incident-handling capability includes preparation.
  8. IRO-02_A08 the operational incident-handling capability includes detection and analysis.
  9. IRO-02_A09 the operational incident-handling capability includes containment.
  10. IRO-02_A10 the operational incident-handling capability includes eradication.
  11. IRO-02_A11 the operational incident-handling capability includes recovery.
  12. IRO-02_A12 lessons learned from ongoing incident handling activities are incorporated into incident response procedures, training, and testing.
  13. IRO-02_A13 the changes resulting from the incorporated lessons learned are implemented accordingly.
  14. IRO-02_A14 an incident-handling capability that is consistent with the incident response plan is implemented.
  15. IRO-02_A15 incident response management operations are conducted according to documented policies, standards, procedures and/or other organizational directives.
  16. IRO-02_A16 resources (e.g., people, processes, technologies, data and/or facilities) required to support incident response management operations are identified and provided.
  17. IRO-02_A17 responsibility and authority for the performance of incident response management-related activities are assigned to designated personnel.
  18. 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)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.