Threat Modeling
What is Threat Modeling?
A structured approach to identifying and prioritizing potential security threats to a system, application, or organization and defining countermeasures.
Terms that appear alongside threat modeling
Each of these is named in at least one of the same controls as threat modeling. The number is how many controls name both.
- vulnerability 6 shared controls
- secure coding 6 shared controls
- security testing 3 shared controls
- nist 3 shared controls
- incident response 3 shared controls
- remediation 3 shared controls
- zero trust 2 shared controls
- patch management 2 shared controls
Frameworks that govern threat modeling
What the standards actually require on threat modeling
Requirements naming threat modeling across 6 standards, quoted from the control text.
Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development and the subsequent testing and evaluation of the system, component, or service that: (a) Uses the following contex...
NIST800-SA-11(2) · SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses →Perform threat modelling to identify potential threats and enumerate mitigating controls, covering both the running application and the artefacts and pipeline that produce it.
ASBv3-DS-1 · Conduct threat modeling →Carry out threat modelling, which is the work of finding and dealing with security design flaws in an application's design before any code is written.
CIS-16.14 · Conduct Threat Modeling →Carry out threat modelling, which identifies and addresses security design flaws before code is written. Trained people evaluate the design and the risk at each entry point and access level, laying out the application and the architecture and infrastructure be...
cis-controls-v8-1::16.14 · Conduct Threat Modeling →Conduct cloud-native threat modeling: enumerate assets, trust boundaries and threats (including the v2 ransomware use case) to drive control selection.
CNCF-SA-THREATMODEL · Threat Modeling →Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses. Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development and the subsequent testing
SA-11(2) · Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2)) →Questions people ask about threat modeling
What is Threat Modeling?
Why is Threat Modeling important for compliance?
Which compliance frameworks address Threat Modeling?
Where can I learn more about Threat Modeling?
See how Threat Modeling applies across compliance frameworks
Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.