What Is STRIDE?

STRIDE is a threat-modeling framework developed at Microsoft in the late 1990s to give engineers a structured, repeatable way to ask "what could go wrong here?" instead of relying on whoever happens to be in the room to think of everything. It remains the most widely used framework for software threat modeling today.

Quick definition: STRIDE is a mnemonic for six categories of threat — Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege — each of which violates a specific security property a well-designed system should uphold.

The six categories

ThreatViolatesExample
S Spoofing Authentication An attacker forges a JWT to impersonate another user
T Tampering Integrity An attacker modifies a request payload in transit
R Repudiation Non-repudiation A user denies performing an action because there is no audit log
I Information Disclosure Confidentiality Stack traces leak internal file paths to a public API response
D Denial of Service Availability Unauthenticated endpoints accept unbounded file uploads
E Elevation of Privilege Authorisation A standard user accesses an admin-only route due to missing RBAC checks

How STRIDE is actually applied

STRIDE is rarely applied to a system as a whole — that produces a vague list nobody acts on. Instead, it's applied per element of a Data Flow Diagram: for every process, data store, external entity, and data flow you've mapped, you ask which of the six categories could apply to that specific element. A login API process gets checked against all six; a static data store typically doesn't need a Denial of Service pass in the same way a public endpoint does.

This element-by-element discipline is what makes STRIDE repeatable rather than dependent on one person's intuition. Two different engineers running STRIDE against the same DFD should land on largely the same threat list, because the categories and the elements to check them against are both fixed.

STRIDE vs. PASTA vs. LINDDUN

STRIDE isn't the only threat-modeling framework, though it's the one most teams start with. PASTA (Process for Attack Simulation and Threat Analysis) is a heavier, risk-centric process that ties threats directly to business impact — more common in organisations that need to justify security spend to non-technical stakeholders. LINDDUN mirrors STRIDE's structure but replaces the six categories with privacy-specific ones (Linkability, Identifiability, Non-repudiation, Detectability, Disclosure, Unawareness, Non-compliance), and is worth adding alongside STRIDE if your system handles personal data under GDPR or similar regulation.

For most teams, STRIDE is the right starting point: it's fast to learn, maps directly onto a DFD, and covers the threat categories that account for the overwhelming majority of real-world software vulnerabilities.

For how STRIDE fits alongside PASTA, LINDDUN, attack trees, OCTAVE and the scoring models, see threat modeling methodologies compared.

For a full worked example — threat-modeling an actual login flow end to end with STRIDE — see What Is Threat Modeling and Why Does It Matter?

Several industries require a specific threat-classification step that STRIDE can satisfy directly — see threat modeling by industry for which standard expects what.

Frequently asked questions

What does STRIDE stand for?

STRIDE stands for Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service and Elevation of Privilege. Each category is the violation of one security property: authenticity, integrity, non-repudiation, confidentiality, availability and authorization.

How do you apply STRIDE?

Apply it per element of a data flow diagram rather than to the whole system. For every process, data store, external entity and data flow, ask which of the six categories could apply, and pay most attention to elements that sit on a trust boundary. Each finding becomes a threat you can score and treat.

Is STRIDE still used today?

Yes. STRIDE remains the framework most teams start with, because it is quick to learn and fits routine design reviews. Teams often pair it with LINDDUN for privacy threats and with attack trees to explore the most serious threats in more depth.

Apply STRIDE in a real threat model

Map your system as a data flow diagram in ThreatTree, walk each element through the six STRIDE categories, then capture the threats that matter as attack tree steps tagged with their STRIDE category. Score them, and they flow straight into an auto-generated risk register. Want a head start on the sweep? The attack tree generator suggests STRIDE-tagged threats for every component you've drawn.

Looking for a free threat modeling tool? ThreatTree's Free plan includes data flow diagrams, attack trees and the risk register. See all features.

Get started free

Not ready to sign up? Get new threat-modeling guides by email instead.