Skip to main content

IRO-02.1: Automated Incident Handling Processes

IRO 1 — Low Respond

Automated mechanisms exist to support the incident handling process.

Control Question: Does the organization use automated mechanisms to support the incident handling process?

General (13)
US (11)
EMEA (2)
Framework Mapping Values
EMEA EU DORA 9.4(b)
EMEA Israel CDMO 1.0 24.4

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to support the incident handling process.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to support the incident handling process.

Level 2 — Planned & Tracked

C|P-CMM2 is N/A, since a well-defined process is required to support the incident handling process.

Level 3 — Well Defined

Incident Response (IR) processes are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • An Integrated Security Incident Response Team (ISIRT), or similar function, exists to form an on-demand, scalable and integrated team of formally-assigned cybersecurity, IT, data privacy and business function representatives that can perform coordinated incident response.
  • The ISIRT, or similar function, develops and maintains a documented, program-level Integrated Incident Response Program (IIRP) that provides operational and tactical-level guidance for cybersecurity and data privacy response operations.
  • A Security Operations Center (SOC), or similar function, facilitates incident management operations that includes preparation, detection and analysis, containment, eradication and recovery.
  • Business Process Owners (BPOs), in conjunction with the SOC and ISIRT functions, develop and maintain a documented Incident Response Plan (IRP) specific to the business process / business unit but inclusive of the organization's larger approach to incident response operations.
  • An IT Asset Management (ITAM) function, or similar function, categorizes endpoint devices according to the data the asset stores, transmits and/ or processes and provides that information to the SOC for Incident Response Operations (IRO).
Level 4 — Quantitatively Controlled

See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to support the incident handling process.

Level 5 — Continuously Improving

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to support the incident handling process.

Assessment Objectives

  1. IRO-02.1_A01 anomalous or suspicious behavior is defined.
  2. IRO-02.1_A02 organizational systems and system components are monitored on an ongoing basis for anomalous or suspicious behavior.
  3. IRO-02.1_A03 automated mechanisms used to support the incident handling process are defined.
  4. IRO-02.1_A04 the incident handling process is supported using automated mechanisms.
  5. IRO-02.1_A05 incident response personnel (identified by name and/or by role) to be notified of detected suspicious events is/are defined.
  6. IRO-02.1_A06 least-disruptive actions to terminate suspicious events are defined.
  7. IRO-02.1_A07 incident response personnel are notified of detected suspicious events.
  8. IRO-02.1_A08 least-disruptive actions are taken upon the detection of suspicious events.

Technology Recommendations

Medium

  • CimTrak Integrity Suite (https://cimcor.com/cimtrak)

Large

  • CimTrak Integrity Suite (https://cimcor.com/cimtrak)

Enterprise

  • CimTrak Integrity Suite (https://cimcor.com/cimtrak)

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.