threat-modeling

Threat modeling identifies and quantifies security risks by enumerating threats per system element. It uses system decomposition and trust boundary definitions to map threats to mitigations and document residual risk for remediation planning.

STRIDE and PASTA are distinct methodologies for structuring threat modeling. STRIDE categorizes threats by type per element, while PASTA focuses on a risk-centric approach to quantify likelihood and impact across the system decomposition.

To enumerate threats per element, select STRIDE or PASTA, break down the system architecture, and define trust boundaries. You then score likelihood and impact for each threat and map them to specific mitigations to calculate residual risk.

Yes, threat modeling supports secure-by-design initiatives and compliance mappings. By systematically quantifying risks and documenting residual risk per element, it provides the necessary audit trail for architecture reviews and compliance requirements.

Yes, a system decomposition reference is required to begin threat modeling. It acts as the baseline to define trust boundaries, enumerate per-element threats, and accurately score likelihood and impact for mitigations.

The best way to document residual risk is through per-element threat enumeration and mitigation mapping. By scoring likelihood and impact before and after mitigations, you produce a quantified residual risk profile for remediation planning.