Skip to main content

IRO-03: Indicators of Compromise (IOC)

IRO 8 — High Respond

Mechanisms exist to define specific Indicators of Compromise (IOC) to identify the signs of potential cybersecurity events.

Control Question: Does the organization define specific Indicators of Compromise (IOC) to identify the signs of potential cybersecurity events?

General (11)
Framework Mapping Values
COBIT 2019 DSS02.01
CSA IoT SCF 2 IAM-09 MON-02 MON-09
ISO/SAE 21434 2021 RQ-08-02
NIST 800-171 R2 (source) 3.14.7
NIST CSF 2.0 (source) DE.CM
Shared Assessments SIG 2025 J.5
TISAX ISA 6 1.6.1
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) IRO-03
SCF CORE ESP Level 1 Foundational IRO-03
SCF CORE ESP Level 2 Critical Infrastructure IRO-03
SCF CORE ESP Level 3 Advanced Threats IRO-03
US (9)
Framework Mapping Values
US C2M2 2.1 SITUATION-2.D.MIL2 SITUATION-2.E.MIL2 SITUATION-2.F.MIL2 SITUATION-2.G.MIL3 SITUATION-2.H.MIL3 SITUATION-2.I.MIL3 RESPONSE-1.D.MIL3 RESPONSE-1.E.MIL3 RESPONSE-1.F.MIL3
US CISA CPG 2022 3.A
US CMMC 2.0 Level 2 (source) SI.L2-3.14.7
US DHS CISA TIC 3.0 3.UNI.DTDIS
US DHS ZTCF SEC-02 SEC-05 TRF-01
US FFIEC D1.RM.RMP.A.4 D5.IR.Te.E.1 D5.ER.Es.E.1
US HIPAA HICP Medium Practice 8.M.A 8.M.B
US HIPAA HICP Large Practice 8.M.A 8.M.B
US NERC CIP 2024 (source) CIP-008-6 1.2.1 CIP-008-6 1.2.2
EMEA (4)
APAC (1)
Framework Mapping Values
APAC New Zealand NZISM 3.6 7.2.17.C.01 7.2.17.C.02
Americas (1)
Framework Mapping Values
Americas Canada OSFI B-13 2.7.2 3.1

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to define specific Indicators of Compromise (IOC) to identify the signs of potential cybersecurity events.

Level 1 — Performed Informally

Incident Response (IRO) efforts are ad hoc and inconsistent. CMM Level 1 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • IT personnel use an informal process to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery.
  • Incident response operations are decentralized.
Level 2 — Planned & Tracked

Incident Response (IRO) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for incident response operations. o Implement and maintain 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.

  • Incident response operations are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
  • IT/cybersecurity personnel:
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 define specific Indicators of Compromise (IOC) to identify the signs of potential cybersecurity events.

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 define specific Indicators of Compromise (IOC) to identify the signs of potential cybersecurity events.

Assessment Objectives

  1. IRO-03_A01 anomalous or suspicious behavior is defined.
  2. IRO-03_A02 environments or resources which may contain or may be related to anomalous or suspected adversarial behavior are defined.
  3. IRO-03_A03 anomalous or suspected adversarial behavior in or related to organization-defined environments or resources are analyzed.
  4. IRO-03_A04 organizational systems and system components are monitored on an ongoing basis for anomalous or suspicious behavior.

Evidence Requirements

E-IRO-02 Indicators of Compromise (IOC)

Documented evidence of defined Indicators of Compromise (IOC).

Incident Response

Technology Recommendations

Micro/Small

  • Indicators of Compromise (IoC)

Small

  • Indicators of Compromise (IoC)

Medium

  • Indicators of Compromise (IoC)

Large

  • Indicators of Compromise (IoC)

Enterprise

  • Indicators of Compromise (IoC)

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.