Skip to main content

IRO-03: Continuous Incident Response Improvements

IRO 3 — Low Identify

Mechanisms exist to use qualitative and quantitative data from incident response testing to: (1) Determine the effectiveness of incident response processes; (2) Continuously improve incident response processes; and (3) Provide incident response measures and metrics that are accurate, consistent and in a reproducible format.

Renumbered: Formerly IRO-04.3 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, IRO-03 was Indicators of Compromise (IOC). That control is now IRO-05.

Control Question: Does the organization use qualitative and quantitative data from incident response testing to: (1) Determine the effectiveness of incident response processes; (2) Continuously improve incident response processes; and (3) Provide incident response measures and metrics that are accurate, consistent and in a reproducible format?

General (5)
Framework Mapping Values
COBIT 2019 DSS03.04 DSS03.05
NIST 800-53 R5.2 IR-03(03)
NIST 800-82 R3 IR-03(03)
NIST 800-171 R3 (source) 03.06.04.b
NIST 800-171A R3 (source) A.03.06.04.b[03]
US (2)
Framework Mapping Values
USA Federal CISA CPG 2022 2.S
USA Federal IRS 1075 2021 IR-3(CE-3) IR-3(CE-3).a IR-3(CE-3).b IR-3(CE-3).c
EMEA (1)
Framework Mapping Values
EMEA UK CAP 1850 2020 D2
APAC (4)
Framework Mapping Values
APAC Australia SOCI 2028 30CF
APAC Japan ISMAP 16.1.1.14
APAC Singapore CCOP CII 2026 7.3.3(g)
APAC Singapore MAS TRM 2021 7.8.3 12.3.3
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.06.04.B

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

SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).

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 use qualitative and quantitative data from incident response testing to: (1) Determine the effectiveness of incident response processes; (2) Continuously improve incident response processes; and (3) Provide incident response measures and metrics that are accurate, consistent and in a reproducible format.

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-03_A01 qualitative / quantitative data from testing are used to determine the effectiveness of incident response processes.
  2. IRO-03_A02 qualitative / quantitative data from testing are used to continuously improve incident response processes.
  3. IRO-03_A03 qualitative / quantitative data from testing are used to provide incident response measures and metrics that are accurate.
  4. IRO-03_A04 qualitative / quantitative data from testing are used to provide incident response measures and metrics that are consistent.
  5. IRO-03_A05 qualitative / quantitative data from testing are used to provide incident response measures and metrics in a reproducible format.

Evidence Requirements

E-IRO-07 IRP Updates

Documented evidence of a periodic review process for the organization's Incident Response Plan (IRP) to identify necessary updates.

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

  • ITIL 4 (https://axelos.com) - Incident and problem management

Large

  • ITIL 4 (https://axelos.com) - Incident and problem management

Enterprise

  • ITIL 4 (https://axelos.com) - Incident and problem management

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.