Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Threat Modelling?

Threat modelling is a structured way of identifying what could go wrong with a system from a security perspective, so that risks can be addressed during design rather than after release.

Illustration for the cybersecurity term Threat Modelling
Home / Blog / Cybersecurity Terms / What Is Threat Modelling?
17 November 2026

What Is Threat Modelling?

What Is Threat Modelling?

Threat modelling is a structured process for understanding how a system could be attacked and deciding how to defend it. It is usually carried out during design, before code is written, when changing direction is cheap. Instead of waiting for a penetration test to reveal problems in a finished product, teams think like attackers early and build protections in from the start.

It applies to almost anything: a new web application, an API, a cloud migration, an AI-powered service, an internal business process, or a change to network architecture.

The Four Key Questions

The Threat Modeling Manifesto, published by a group of practitioners in 2020, sums up the process in four questions:

  1. What are we working on? Build a shared understanding of the system, usually as a diagram.
  2. What can go wrong? Identify threats to each part of the system.
  3. What are we going to do about it? Decide how to mitigate, accept, transfer, or eliminate each threat.
  4. Did we do a good enough job? Review the model and validate that mitigations work.

These questions keep threat modelling practical and stop it from becoming an academic exercise.

Modelling the System

Most teams start with a data flow diagram showing external entities (users, other systems), processes, data stores, and the flows between them. The most important element is the trust boundary: any point where data passes between areas with different levels of trust, such as from the internet into a web application, or from an application into a database. Threats cluster around these boundaries, so they deserve the closest attention.

STRIDE and Other Methods

STRIDE, developed at Microsoft in 1999, is the most widely used way of brainstorming threats. Each letter represents a category, paired with the security property it violates:

ThreatProperty violatedExample
SpoofingAuthenticationUsing stolen credentials to impersonate a user
TamperingIntegrityChanging the price of an item in a request
RepudiationNon-repudiationDenying an action because nothing was logged
Information disclosureConfidentialityAn API returning more data than intended
Denial of serviceAvailabilityExhausting server resources with expensive requests
Elevation of privilegeAuthorisationA normal user accessing admin functions

Other approaches suit different needs. PASTA (Process for Attack Simulation and Threat Analysis) is a seven-stage, risk-centric method that links threats to business impact. LINDDUN focuses on privacy threats, useful for UK GDPR data protection by design. Attack trees, popularised by Bruce Schneier, break an attacker’s goal into the different ways it could be achieved. Many teams also use the MITRE ATT&CK framework and the OWASP Top 10 as checklists of realistic attacks.

A Simple Example

Imagine a team designing a password reset feature. Using STRIDE, they might identify that an attacker could request resets for other users’ accounts (spoofing), that reset tokens could be guessed if they are short (elevation of privilege), that the “email not found” message reveals which accounts exist (information disclosure), and that someone could flood the service with reset requests (denial of service). Mitigations follow naturally: long random single-use tokens, short expiry times, identical responses for existing and non-existent accounts, rate limiting, and logging of reset events.

Making Threat Modelling Part of Development

Threat modelling works best as a regular habit rather than a one-off workshop:

Threat modelling is a core activity in secure software development frameworks such as the NIST Secure Software Development Framework and OWASP SAMM. It is also increasingly important for AI systems, where risks such as prompt injection need to be considered from the earliest design stage.

At Privia Security, our Infrastructure and Architecture Review Services include threat modelling of new systems and architectures, so security risks are addressed before they are built in.

FAQ – Frequently Asked Questions

When Should Threat Modelling Be Done?

Ideally during design, before significant code is written, because design flaws are much cheaper to fix at that stage. It should then be revisited whenever the system changes in a meaningful way, such as adding a new integration, exposing a new API, or moving to a different hosting platform. Many teams build it into regular design reviews.

Is Threat Modelling Only for Software Developers?

No. Although it is most associated with software design, threat modelling is equally useful for cloud architectures, network changes, business processes, supplier integrations, and physical security. Any situation where you need to understand how something could be attacked and how to defend it can benefit from the same structured thinking.

What Is the Difference Between Threat Modelling and a Penetration Test?

Threat modelling is a design activity that identifies potential threats and mitigations before or during development. A penetration test actively attempts to exploit a built system to find real vulnerabilities. The two complement each other: threat models highlight where testing should focus, and test results show whether the planned mitigations actually work in practice.

Related Terms

You May Be Interested In These

What Is ffuf?

Cybersecurity Terms

17 November 2026

What Is ffuf?

Read More
What Is the OSCP Certification?

Cybersecurity Terms

17 November 2026

What Is the OSCP Certification?

Read More