NIST SP 800-172
RA

NIST SP 800-172 3.11.1e: Threat-Aware Risk Assessment

Employ threat intelligence, at a minimum from open or commercial sources and any DoD-provided sources, as part of a risk assessment to guide and inform the development of organizational systems, security architectures, selection of security solutions, monitoring, threat hunting, and response and recovery activities.

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

What else in your programme already covers this

This control maps to 43 controls across 19 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-07 Cyber threat intelligence and other contextual information are integrated into the analysis
  • NIST-CSF-GV.RM-07 Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions
  • 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 SP 800-161 Rev 1 · 5 controls

NIST SP 800-53 Rev 5 · 4 controls

FedRAMP High · 3 controls

  • RA-3 Risk Assessment
  • SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))
  • SI-5 Security Alerts, Advisories, and Directives

FedRAMP Moderate · 3 controls

  • RA-3 Risk Assessment
  • SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))
  • SI-5 Security Alerts, Advisories, and Directives
  • ASBv3-DS-1 Conduct threat modeling
  • ASBv3-GS-7 Define and implement logging, threat detection and incident response strategy

C5 (Germany) · 2 controls

  • C5-OIS-05 Contact with Relevant Government Agencies and Interest Groups
  • C5-OIS-07 Application of the Risk Management Policy

CIS Controls v8 · 2 controls

  • CIS-16.14 Conduct Threat Modeling
  • CIS-7.1 Establish and Maintain a Vulnerability Management Process

CMMC 2.0 · 2 controls

NIST SP 800-218 · 2 controls

PCI DSS 4.0 · 2 controls

  • 12.3.1 12.3.1 Targeted risk analysis for flexible-frequency requirements
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking

SOC 2 · 2 controls

  • SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)
  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)

HIPAA Security Rule · 1 control

ISO 22301:2019 · 1 control

ISO 27001:2022 · 1 control

  • 5.7 Threat intelligence

ISO 27002:2022 · 1 control

  • 5.7 Threat intelligence

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 RA

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

NIST SP 800-172 3.11.1e 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.

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.

Query this from an agent

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