ISO 27001:2022
Organizational controls – ISO 27001:2022

ISO 27001:2022 5.7: Threat intelligence

Information about security threats is to be gathered and examined so that it yields threat intelligence. Purpose (stated in ISO/IEC 27002:2022): makes the organization aware of the threats it faces so fitting mitigations can be chosen. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 5.7.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 73 controls across 31 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • NIST-CSF-DE.AE-03 Information is correlated from multiple sources
  • NIST-CSF-DE.AE-07 Cyber threat intelligence and other contextual information are integrated into the analysis
  • NIST-CSF-ID.RA-02 Cyber threat intelligence is received from information sharing forums and sources
  • NIST-CSF-ID.RA-03 Internal and external threats to the organization are identified and recorded
  • NIST-CSF-ID.RA-04 Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded
  • NIST-CSF-ID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization
  • NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved

NIST SP 800-53 Rev 5 · 5 controls

SOC 2 · 5 controls

  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies

CIS Controls v8 · 4 controls

  • CIS-13.3 Deploy a Network Intrusion Detection Solution
  • CIS-13.6 Collect Network Traffic Flow Logs
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-8.2 Collect Audit Logs

FedRAMP High · 4 controls

  • RA-3 Risk Assessment
  • RA-7 Risk Response
  • SA-2 Allocation of Resources
  • SI-5 Security Alerts, Advisories, and Directives

HIPAA Security Rule · 4 controls

NIST SP 800-66 Rev 2 · 4 controls

PCI DSS 4.0 · 4 controls

  • 10.7.1 10.7.1 Service providers detect critical control failures (superseded)
  • 11.3.1 11.3.1 Quarterly internal vulnerability scans
  • 11.5.1 11.5.1 IDS/IPS monitoring of CDE traffic
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking

DORA · 3 controls

  • DORA-Art.13 Learning and evolving
  • DORA-Art.18 Classification of ICT-related incidents and cyber threats
  • DORA-Art.45 Information-sharing arrangements on cyber threat information and intelligence

FedRAMP Moderate · 3 controls

  • RA-3 Risk Assessment
  • SA-2 Allocation of Resources
  • SI-5 Security Alerts, Advisories, and Directives

NIST SP 800-161 Rev 1 · 3 controls

CMMC 2.0 · 2 controls

NIS2 Directive · 2 controls

  • Art.21.3 Take account of supplier-specific vulnerabilities and of Union coordinated supply chain risk assessments
  • Art.23.2 Tell affected service recipients about significant cyber threats and the remedies open to them

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-172 · 2 controls

  • 3.11.1e Threat-Aware Risk Assessment
  • 3.14.6e Use Threat Indicator Information for Detection
  • E8-PATCHAPP-ML1 Patch Applications (ML1)
  • CPS230-11 Identification, Assessment and Management of Operational Risk

APRA CPS 234 · 1 control

  • CPS234-P17 Active Maintenance of Capability Against Change
  • ASD37-31 Hunt to discover incidents (Very Good)
  • SEC01-BP04 Stay up to date with security threats and recommendations
  • AUCDR-IS-STEP3 Step 3 - Have and maintain an information security capability

C5 (Germany) · 1 control

  • C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept
  • CAT-D2-1 Threat intelligence
  • IS-VI.A.3 Threat Intelligence

ISO 27001:2013 · 1 control

  • A.6.1.4 Contact with special interest groups

ISO 27002:2022 · 1 control

  • 5.7 Threat intelligence

ISO 27701:2019 · 1 control

  • 5.7 Performance evaluation

ISO/IEC 42001:2023 · 1 control

NIST SP 800-218 · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Organizational controls – ISO 27001:2022

You are reading one control. How much of ISO 27001:2022 have you already done?

ISO 27001:2022 5.7 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 73 it maps to, and the evidence behind each claim, over MCP and REST.