Skip to main content

THR-02: Indicators of Exposure (IOE)

THR 8 — High Identify

Mechanisms exist to develop Indicators of Exposure (IOE) to understand the potential attack vectors that attackers could use to attack the organization.

Control Question: Does the organization develop Indicators of Exposure (IOE) to understand the potential attack vectors that attackers could use to attack the organization?

General (9)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC3.2-POF6 CC3.2-POF7 CC3.3 CC9.2-POF13
COSO 2017 Principle 8
ISO/SAE 21434 2021 RQ-08-01 RQ-08-02
ISO 27002 2022 5.7
NIST CSF 2.0 (source) DE DE.CM ID.RA-03 ID.RA-05 ID.RA-08
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) THR-02
SCF CORE ESP Level 1 Foundational THR-02
SCF CORE ESP Level 2 Critical Infrastructure THR-02
SCF CORE ESP Level 3 Advanced Threats THR-02
US (3)
Framework Mapping Values
US CISA CPG 2022 3.A
US DHS CISA TIC 3.0 3.UNI.DTDIS
US DHS ZTCF SEC-05 TRF-01
EMEA (2)
Framework Mapping Values
EMEA Israel CDMO 1.0 23.3
EMEA Saudi Arabia OTCC-1 2022 2-12-2-8
APAC (1)
Framework Mapping Values
APAC Singapore MAS TRM 2021 14.3.1 14.3.2 14.3.3
Americas (1)
Framework Mapping Values
Americas Canada OSFI B-13 3.1

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to develop Indicators of Exposure (IOE) to understand the potential attack vectors that attackers could use to attack the organization.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to develop Indicators of Exposure (IOE) to understand the potential attack vectors that attackers could use to attack the organization.

Level 2 — Planned & Tracked

Threat Management (THR) 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 threat management. o Subscribe to threat feeds to maintain situational awareness of emerging threats.

  • Threat management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
  • The HR department, in conjunction with cybersecurity personnel, helps ensure secure practices are implemented in personnel management operations to help manage threats.
  • IT/cybersecurity personnel:
Level 3 — Well Defined

Threat Management (THR) efforts 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: o Subscribes to threat feeds to maintain situational awareness of emerging threats. o Develops Indicators of Exposure (IOE) to better understand potential attack vectors that attackers could use to attack the organization. o Implements a Threat Awareness Program (TAP) that includes a cross-organization information-sharing capability. o Implements a “threat hunting” capability to actively identify internal threats.

  • A Security Operations Center (SOC), or similar function:
  • An Integrated Security Incident Response Team (ISIRT), or similar function, exists to form an on-demand, integrated team of cybersecurity, IT, data privacy and business function representatives that can execute coordinated incident response operations, including a cross-discipline incident handling capability.
  • Cybersecurity personnel enable security awareness training on recognizing and reporting potential indicators of insider threat.
Level 4 — Quantitatively Controlled

Threat Management (THR) efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
  • Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
  • Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
  • Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
  • Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
  • Both business and technical stakeholders are involved in reviewing and approving proposed changes.
Level 5 — Continuously Improving

Threat Management (THR) efforts are “world-class” capabilities that leverage predictive analysis (e.g., machine learning, AI, etc.). In addition to CMM Level 4 criteria, CMM Level 5 control maturity would reasonably expect all, or at least most, the following criteria to exist:

  • Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions.
  • Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes.

Assessment Objectives

  1. THR-02_A01 Indicators of Exposure (IOE) exist for personnel to understand the potential attack vectors that attackers could use to attack the organization.

Evidence Requirements

E-THR-01 Indicators of Exposure (IOE)

Documented evidence of defined Indicators of Exposure (IOE).

Threat Management

Technology Recommendations

Micro/Small

  • Indicators of Exposure (IoE)

Small

  • Indicators of Exposure (IoE)

Medium

  • Indicators of Exposure (IoE)

Large

  • Indicators of Exposure (IoE)

Enterprise

  • Indicators of Exposure (IoE)

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.