NIST SP 800-172
SI

NIST SP 800-172 3.14.6e: Use Threat Indicator Information for Detection

Use threat indicator information relevant to the information and systems being protected and effective mitigations obtained from external organizations to inform intrusion detection and threat hunting.

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

What else in your programme already covers this

This control maps to 28 controls across 16 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 Cybersecurity Framework 2.0 · 3 controls

  • 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 SP 800-161 Rev 1 · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

Azure Security Benchmark · 2 controls

  • ASBv3-ES-3 Ensure anti-malware software and signatures are updated
  • ASBv3-LT-1 Enable threat detection capabilities

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

FedRAMP High · 2 controls

  • SI-5 Security Alerts, Advisories, and Directives
  • SI-7(7) Integration of Detection and Response

FedRAMP Moderate · 2 controls

  • SI-5 Security Alerts, Advisories, and Directives
  • SI-7(7) Integration of Detection and Response

ISO 27001:2022 · 2 controls

  • 5.6 Contact with special interest groups
  • 5.7 Threat intelligence

ISO 27002:2022 · 2 controls

  • 5.6 Contact with special interest groups
  • 5.7 Threat intelligence

C5 (Germany) · 1 control

  • C5-OIS-05 Contact with Relevant Government Agencies and Interest Groups

CIS Controls v8 · 1 control

  • CIS-16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities

CMMC 2.0 · 1 control

NIST SP 800-171 Rev 3 · 1 control

  • 03.14.03 Security Alerts, Advisories, and Directives

NIST SP 800-218 · 1 control

PCI DSS 4.0 · 1 control

  • 6.3.1 6.3.1 Vulnerability identification and risk ranking

SOC 2 · 1 control

  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies

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 SI

You are reading one control. How much of NIST SP 800-172 have you already done?

NIST SP 800-172 3.14.6e is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-172 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 24 of 35 NIST SP 800-172 controls already carry evidence.

If you hold NIST SP 800-53 Rev 568.6% covered · 11 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.165.7% covered · 12 gapsIf you hold NIST SP 800-161 Rev 162.9% covered · 13 gapsIf you hold FedRAMP Moderate60% covered · 14 gapsIf you hold NIST Cybersecurity Framework 2.048.6% covered · 18 gapsIf you hold C5 (Germany)45.7% covered · 19 gaps

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. 5 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll NIST SP 800-172 controls