Skip to main content

THR-05: Threat Intelligence Reporting

THR 8 — High Identify

Mechanisms exist to utilize external threat intelligence feeds to generate and disseminate organization-specific security alerts, advisories and/or directives.

Renumbered: Formerly THR-03.1 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, THR-05 was Insider Threat Awareness. That control is now THR-16.

Control Question: Does the organization utilize external threat intelligence feeds to generate and disseminate organization-specific security alerts, advisories and/or directives?

General (5)
Framework Mapping Values
BSI Standard 200-1 4.2
ISO 27002 2022 5.7
ISO 27018 2025 5.7
NIST 800-171 R3 (source) 03.14.03.b
NIST 800-171A R3 (source) A.03.14.03.a A.03.14.03.b[01] A.03.14.03.b[02]
US (3)
Framework Mapping Values
USA Federal C2M2 2.1 THREAT-1i THREAT-2b THREAT-2h THREAT-2k
USA Federal DoD Zero Trust Execution Roadmap v1.1 7.5 7.5.1 7.5.2
USA Federal 33 CFR Part 101 Subpart F 101.625(d)(8) 101.625(d)(14) 101.650(e)(3)(iii)
EMEA (6)
APAC (5)
Framework Mapping Values
APAC India SEBI CSCRF 2024 RS.AN.S1
APAC Japan ISMAP 4.9 4.9.1.1 4.9.2.1 4.9.2.2
APAC Malaysia RMiT 2025 11.19 A5-C3(b)
APAC Singapore CCOP CII 2026 3.1.5(a) 3.1.5(b) 3.1.5(c) 3.2.3
APAC Singapore MAS TRM 2021 12.1.3
Americas (2)

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

Threat Management (THR) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with THR domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Threat management-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 subscribe to threat feeds to maintain situational awareness of emerging threats. ▪ IT and/or cybersecurity personnel provide limited threat intelligence feeds to employees for situational awareness of evolving threats.

Level 2 — Planned & Tracked

Threat Management (THR) 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 THR domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with THR 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 THR domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Threat management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Threat management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Threat feeds are utilized to maintain situational awareness of emerging threats.

Level 3 — Well Defined

Threat Management (THR) 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 THR domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with THR domain capabilities are well-documented and kept current by process owners. ▪ A threat management team, or similar function, is appropriately staffed and supported to implement and maintain THR domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of threat management operations (e.g., threat intelligence solution and bug bounty solution). ▪ 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 THR 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 utilize external threat intelligence feeds to generate and disseminate organization-specific security alerts, advisories and/or directives.

Level 4 — Quantitatively Controlled

Threat Management (THR) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ 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. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

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. THR-05_A01 internal security alerts, advisories, and directives are generated, as necessary.
  2. THR-05_A02 internal security alerts, advisories, and directives are disseminated, as necessary.

Evidence Requirements

E-THR-04 Threat Intelligence Program (TIP)

Documented evidence of a formal capability that intakes and analysis threat information to determine specific threat to the organization and necessary actions to mitigate the threat(s).

Threat Management

Technology Recommendations

Micro/Small

  • US-CERT mailing lists & feeds
  • Internal newsletters

Small

  • US-CERT mailing lists & feeds
  • Internal newsletters

Medium

  • US-CERT mailing lists & feeds
  • Internal newsletters
  • InfraGard (https://infragard.org)

Large

  • US-CERT mailing lists & feeds
  • Internal newsletters
  • InfraGard (https://infragard.org)

Enterprise

  • US-CERT mailing lists & feeds
  • Internal newsletters
  • InfraGard (https://infragard.org)

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.