Key Threat Modeling Methodologies
Several methodologies have been developed to provide a structured approach to threat modeling. Each has its own focus and strengths, and the choice of methodology often depends on the specific context, system complexity, and organizational preferences. Here are some of the most widely recognized methodologies:
STRIDE
Developed by Microsoft, STRIDE is one of the oldest and most well-known threat modeling methodologies. It's a mnemonic for categorizing threats based on the kind of exploit or motivation behind them. STRIDE is often applied to software applications to identify threats related to security properties.
STRIDE Categories:
| Category | Threat | Violated Security Property |
|---|---|---|
| Spoofing | Illegitimately claiming an identity. | Authentication |
| Tampering | Modifying data or code. | Integrity |
| Repudiation | Denying an action. | Non-Repudiation |
| Information Disclosure | Exposing information to unauthorized individuals. | Confidentiality |
| Denial of Service | Denying or degrading service to valid users. | Availability |
| Elevation of Privilege | Gaining capabilities without proper authorization. | Authorization |
STRIDE is effective for ensuring comprehensive coverage of common threat types, particularly when analyzing data flows and system components. Understanding how to systematically apply these categories across diverse systems helps maintain a consistent security posture across your organization.
DREAD
DREAD is a risk assessment model used to prioritize threats once they have been identified. It helps quantify the severity of each threat based on five categories. Though Microsoft has largely moved away from DREAD in favor of other risk rating systems, it's still a useful conceptual tool for some teams.
DREAD Categories (typically rated 1-10):
- Damage Potential: How great is the damage if the vulnerability is exploited?
- Reproducibility: How easy is it to reproduce the attack?
- Exploitability: How easy is it to launch an attack?
- Affected Users: How many users will be affected?
- Discoverability: How easy is it to find the vulnerability?
The DREAD score is often calculated by summing or averaging the scores. Higher scores indicate higher-risk threats that should be prioritized. This data-driven approach to risk assessment mirrors how autonomous analysis platforms help make informed decisions by synthesizing multiple factors into actionable insights.
PASTA (Process for Attack Simulation and Threat Analysis)
PASTA is a seven-step, risk-centric methodology. It aims to align business objectives with technical requirements, taking a threat-centric view that combines an attacker's perspective with risk and impact analysis. PASTA is known for its comprehensive and contextual approach.
PASTA Stages:
- Define Objectives (DO) for the Analysis of Risks
- Define the Technical Scope (DTS)
- Application Decomposition and Analysis (ADA)
- Threat Analysis (TA)
- Weakness and Vulnerability Analysis (WVA)
- Attack Modeling & Simulation (AMS)
- Risk Analysis & Management (RAM)
PASTA emphasizes understanding the attacker's motivations and likely attack patterns. It is particularly useful for applications with significant business impact or complex architectures.
Other Methodologies
While STRIDE, DREAD, and PASTA are prominent, other methodologies and frameworks exist, such as:
- VAST (Visual, Agile, and Simple Threat Modeling): Focuses on scalability and integration with agile development.
- Trike: A risk-based approach with a focus on modeling threats from an attacker's perspective using a requirements model.
- OCTAVE (Operationally Critical Threat, Asset, and Vulnerability Evaluation): A risk-management framework from Carnegie Mellon's SEI, more focused on organizational risk rather than just software.
The choice of methodology can also be influenced by the type of system being analyzed. Understanding these methodologies provides a solid foundation for identifying and mitigating threats. The next step is to learn about the Threat Modeling Process itself.