Skip to main content

IRO-16.2: Cyber Incident Reporting for Sensitive / Regulated Data

IRO 9 — Critical Detect

Mechanisms exist to report sensitive and/or regulated data incidents in a timely manner.

Renumbered: Formerly IRO-10.2 in SCF 2025.4.

Control Question: Does the organization report sensitive and/or regulated data incidents in a timely manner?

General (15)
Framework Mapping Values
AICPA Privacy Management Framework (PMF) D6.6 D6.6-POF2
AICPA TSC 2017:2022 (used for SOC 2) (source) CC2.2-POF6 CC2.3-POF1 CC2.3-POF12 CC7.3-POF2 CC7.3-POF7 CC7.4 CC7.4-POF6 CC7.4-POF13
CIS CSC 8.1 17.2
CIS CSC 8.1 IG1 17.2
CIS CSC 8.1 IG2 17.2
CIS CSC 8.1 IG3 17.2
CSA CCM 4.1.0 SEF-09
IMO Maritime Cyber Risk Management 3.5.5.1
NAIC Insurance Data Security Model Law (MDL-668) 6.A 6.A(1) 6.A(2) 6.A(2)(a) 6.A(2)(b) 6.A(2)(b)(i) 6.A(2)(b)(ii) 6.B 6.B(1) 6.B(2) 6.B(3) 6.B(4) 6.B(5) 6.B(6) 6.B(7) 6.B(8) 6.B(9) 6.B(10) 6.B(11) 6.B(12) 6.B(13) 6.D(2) 6.E(2)(a) 6.E(2)(b) 6.F
NIST AI 600-1 MG-4.3-003
NIST 800-171 R3 (source) 03.06.02.b 03.06.02.c
NIST 800-171A R3 (source) A.03.06.02.ODP[02] A.03.06.02.b
NIST CSF 2.0 (source) RS.CO RS.CO-02 RS.CO-03
NIST Privacy Framework 1.0 CM.AW-P7
TISAX ISA 6.0.3 9.6.2
US (8)
Framework Mapping Values
USA Federal C2M2 2.1 RESPONSE-2g RESPONSE-3c
USA Federal DFARS 252.204-7012 252.204-7012(c)(1)(ii) 252.204-7012(c)(2) 252.204-7012(c)(3) 252.204-7012(d)
USA Federal 33 CFR Part 101 Subpart F 101.620(b)(7) 101.625(d)(10) 101.650(g)(1)
USA Federal HIPAA Administrative Simplification 2013 § 164.410(a)(1)
USA Federal NERC CIP 2024 CIP-008-6 4.2
USA Federal FCA CRM 2023 609.930(c)(3)(v)
USA California SB1386 2002 1798.29(a) 1798.29(b)
USA New York DFS 23 NYCRR500 2023 Amd 2 500.17(a)(1)
EMEA (12)
Framework Mapping Values
EMEA CHE FINMA Circular 2023/1 IV.D-81
EMEA Germany FDPA 2017 3.4.65(1) 3.4.65(2) 3.4.65(3) 3.4.65(3)1 3.4.65(3)2 3.4.65(3)3 3.4.65(3)4 3.4.65(4) 3.4.65(5) 3.4.65(6)
EMEA EU AI Act Article 17.1(j)
EMEA EU Cyber Resiliency Act 2024 Article 14(1) Article 14(3) Article 14(4)(a) Article 14(4)(b) Article 14(4)(c) Article 14(4)(i) Article 14(4)(i)(ii) Article 14(4)(i)(iii)
EMEA EU EBA GL/2019/04 3.7.5.91
EMEA EU GDPR 2016 Article 33.1 Article 33.2 Article 33.3(a) Article 33.3(b) Article 33.3(c) Article 33.3(d) Article 33.4
EMEA EU NIS2 Annex 2024 3.1.2(b)
EMEA Ireland DPA 2018 s.87
EMEA Kenya DPA 2019 IV.43(1)(a)
EMEA Qatar PDPPL 2020 3.14
EMEA Saudi Arabia ECC-1 2018 2-13-3-3 2-13-3-4
EMEA UAE NIAF 2023 3.3.3
APAC (9)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-0733
APAC Australia Prudential Standard CPS230 2023 33
APAC India RBI PA 2025 Annex 1.1.3
APAC India RBI PPI 2025 15.7
APAC India SEBI CSCRF 2024 DE.DP.S3 RS.CO.S2
APAC Japan APPI 2020 IV.1.22-2(1)
APAC New Zealand NZISM 3.9 7.2.18.C.01 7.2.20.C.01 7.2.21.C.01 7.2.23.C.01 7.3.8.C.03
APAC Philippines DPA 2012 V.20(f)
APAC Singapore PDPA 2012 6A.26C(3)(a) 6A.26C(3)(b) 6A.26C(4)
Americas (4)
Framework Mapping Values
Americas Argentina Reg 132 2018 G.1.3
Americas Bahamas DPA 2003 V.47(1) V.47(2) V.47(3) V.47(4)(a) V.47(4)(b) V.47(4)(c) V.47(4)(d) V.47(4)(e) V.47(4)(f) V.47(4)(g) V.47(4)(h) V.47(5) V.47(6) V.47(6)(a) V.47(6)(b) V.47(6)(c)
Americas Canada ITSP-10-171 2025 03.06.02.B 03.06.02.C
Americas Colombia Law 1581 2012 VI.17(n)

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.

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 report sensitive/regulated data incidents in a timely manner.

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-16.2_A01 sensitive / regulated data incidents are reported within an organization-defined time period.
  2. IRO-16.2_A02 authorities to whom incident information is to be reported are defined.

Evidence Requirements

E-IRO-11 Incident Reporting Capability

Documented evidence of a capability to provide situational awareness of incidents to internal stakeholders and generated necessary reporting to affected clients, applicable third-parties and regulatory authorities.

Incident Response

Technology Recommendations

Micro/Small

  • Incident Response Plan (IRP)

Small

  • Incident Response Plan (IRP)

Medium

  • Integrated Incident Response Program (IIRP)
  • Integrated Security Incident Response Team (ISIRT)

Large

  • Integrated Incident Response Program (IIRP)
  • Integrated Security Incident Response Team (ISIRT)

Enterprise

  • Integrated Incident Response Program (IIRP)
  • Integrated Security Incident Response Team (ISIRT)

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.