AWS Well-Architected Security Pillar SEC01-BP07: Identify threats and prioritize mitigations using a threat model

What else in your programme already covers this

This control maps to 54 controls across 20 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 · 5 controls

NIST-CSF-GV.RM-06 A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated
NIST-CSF-ID.AM-03 Representations of the organization's authorized network communication and internal and external network data flows are maintained
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-53 Rev 5 · 5 controls

NIST800-CM-4 CM-4 Impact Analyses
NIST800-RA-3 RA-3 Risk Assessment
NIST800-RA-7 RA-7 Risk Response
NIST800-SA-17 SA-17 Developer Security and Privacy Architecture and Design
NIST800-SA-8 SA-8 Security and Privacy Engineering Principles

CMMC 2.0 · 4 controls

CA.L2-3.12.4 System Security Plan
CM.L2-3.4.4 Security Impact Analysis
RA.L2-3.11.1 Risk Assessments
SC.L2-3.13.2 Security Engineering

NIST SP 800-161 Rev 1 · 4 controls

161R1-PL-8 Security and Privacy Architectures
161R1-RA-3 Risk Assessment
161R1-RA-9 Criticality Analysis
161R1-SA-8 Security and Privacy Engineering Principles

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

CCM-AIS-04 Secure Application Design and Development
CCM-DSP-07 Data Protection by Design and Default
CCM-GRC-02 Risk Management Program

FedRAMP High · 3 controls

CM-4 Impact Analyses
RA-3 Risk Assessment
SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))

FedRAMP Moderate · 3 controls

CM-4 Impact Analyses
RA-3 Risk Assessment
SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))

ISO 27001:2022 · 3 controls

5.8 Information security in project management
8.26 Application security requirements
8.27 Secure system architecture and engineering principles

ISO 27002:2022 · 3 controls

5.8 Information security in project management
8.26 Application security requirements
8.27 Secure system architecture and engineering principles

ISO 27701:2019 · 3 controls

5.4.1 Actions to address risks and opportunities
5.6.2 Information security risk assessment
7.2.5 Privacy impact assessment

NIST SP 800-171 Rev 3 · 3 controls

03.04.04 Impact Analyses
03.11.01 Risk Assessment
03.16.01 Security Engineering Principles

SOC 2 · 3 controls

SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)

C5 (Germany) · 2 controls

C5-OIS-06 Risk Management Policy
C5-OIS-07 Application of the Risk Management Policy

HIPAA Security Rule · 2 controls

164.308(a)(1)(ii)(A) Risk Analysis (Required)
164.308(a)(1)(ii)(B) Risk Management (Required)

NIST SP 800-218 · 2 controls

SP800-218-PW.1.1 Design Software to Meet Security Requirements
SP800-218-PW.1.2 Track Security Requirements, Risks, and Decisions

NIST SP 800-66 Rev 2 · 2 controls

164.308(a)(1)(ii)(A) Risk Analysis (Required)
164.308(a)(1)(ii)(B) Risk Management (Required)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-41 Conduct a Formal Risk Analysis

Azure Security Benchmark · 1 control

ASBv3-DS-1 Conduct threat modeling

PCI DSS 4.0 · 1 control

12.3.1 12.3.1 Targeted risk analysis for flexible-frequency requirements

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.

You are reading one control. How much of AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC01-BP07 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.

If you hold NIST SP 800-53 Rev 582.5% covered · 11 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.6% covered · 16 gaps If you hold ISO 27002:202273% covered · 17 gaps If you hold FedRAMP Moderate69.8% covered · 19 gaps If you hold Azure Security Benchmark65.1% covered · 22 gaps If you hold PCI DSS 4.063.5% covered · 23 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free