Skip to main content

IRO-16.3: Serious Incident Reporting

IRO 5 — Medium Identify

Mechanisms exist to report any serious incident involving the organization's Technology Assets, Applications, Services and/or Data (TAASD) to relevant authorities in the locality where the incident occurred, in accordance with mandatory reporting: (1) Requirements; and (2) Timelines.

Renumbered: Formerly IRO-10.5 in SCF 2025.4.

Control Question: Does the organization report any serious incident involving its Technology Assets, Applications, Services and/or Data (TAASD) to relevant authorities in the locality where the incident occurred, in accordance with mandatory reporting: (1) Requirements; and (2) Timelines?

US (2)
Framework Mapping Values
USA Federal 33 CFR Part 101 Subpart F 101.625(d)(10)
USA Federal NERC CIP 2024 CIP-008-6 R4 CIP-008-6 4.1 CIP-008-6 4.1.1 CIP-008-6 4.1.2 CIP-008-6 4.1.3 CIP-008-6 4.2
EMEA (4)
Framework Mapping Values
EMEA CHE FINMA Circular 2023/1 IV.B.d-60 IV.C-68 IV.D-81
EMEA Spain Royal Decree 311 2022 Article 33(7)
EMEA EU PSD2 2015 96(1)
EMEA Saudi Arabia SAMA CSF 1.0 2017 3.3.15.7 3.3.15.7.a 3.3.15.7.b 3.3.15.7.c 3.3.15.7.d 3.3.15.7.e 3.3.15.7.f 3.3.15.7.g 3.3.15.7.h 3.3.15.7.i 3.3.15.7.j 3.3.15.7.k
APAC (5)
Americas (1)
Framework Mapping Values
Americas Bermuda BMACCC 2020 6.5 6.5(a) 6.5(b) 6.5(c) 6.5(d) 6.5(e)

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.

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 any serious incident involving the organization's TAASD to relevant authorities in the locality where the incident occurred, in accordance with mandatory reporting: (1) Requirements; and (2) Timelines.

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.3_A01 serious incidents involving the organization's Technology Assets, Applications, Services and/or Data (TAASD) are reported to relevant authorities in the locality where the incident occurred, in accordance with mandatory reporting requirements and timelines.

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

  • Basic incident response plan
  • Designate incident response contact

Small

  • Documented incident response plan
  • Incident log
  • Designated IR team

Medium

  • Formal incident response program
  • IR playbooks
  • Tabletop exercises

Large

  • Enterprise incident response program
  • 24/7 SOC monitoring
  • SOAR platform

Enterprise

  • Enterprise SOC with SIEM/SOAR (e.g., Splunk SOAR, Palo Alto XSOAR)
  • IR retainer
  • Threat hunting

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.