NodeMotion
Live Canvas
Back to Guides & eBooks Hub
Fundamentals · Lesson 2 / 8
LESSON 02STRIDEPASTALINDDUNAttack Trees

Threat Modeling Methodologies Decoded: STRIDE, PASTA, LINDDUN & Attack Trees

Choosing the right lens for software engineering, business risk, privacy & deep exploit paths

THREAT MODELING ACADEMY · LESSON 02⏱ 11 min read

“A carpenter doesn’t argue about whether a hammer is better than a saw. Pick the threat modeling methodology that matches the question you need answered.”

— Nova, Principal Security Architect
TL;DR in 15 Seconds:STRIDE excels at software/architecture reviews, PASTA aligns security with business risk in 7 stages, LINDDUN hunts privacy/GDPR blind spots, and Attack Trees decompose complex attacker goals into AND/OR paths.
Nova's Field Tip:Start 90% of engineering sprint reviews with STRIDE—it maps straight to code controls. Reach for LINDDUN whenever personal data or tracking is involved!
STRIDEDeveloper-Friendly6 Threat CategoriesFast Sprint ReviewsLens: Software FlowsPASTA7-Stage Risk-CentricBusiness Impact FirstAttack SimulationLens: Business RiskLINDDUNPrivacy & GDPRLinkability & TrackingAttack Trees PairingLens: Privacy“Which methodology wins? None—pick the right lens for the problem in front of you!”STRIDE for dev sprints, PASTA for executive risk, LINDDUN for privacy, Attack Trees for depth.
STRIDE, PASTA, and LINDDUN debate at sprint planning—each bringing a different security superpower to the table.

Walk into an AppSec conference and ask "Which threat modeling methodology is best?" and you will start a 45-minute philosophical debate. One person swears by STRIDE, another insists on 7-stage PASTA, and a privacy engineer chimes in with LINDDUN.

Here is the secret: they are not competitors—they are different lenses. Looking at a microservice through STRIDE reveals broken authentication and tampering. Looking at that same microservice through LINDDUN reveals that your analytics pipeline accidentally de-anonymizes minors in Europe.

Knowing how each methodology thinks lets you pick the sharpest tool in 30 seconds instead of forcing a heavyweight framework onto a two-day sprint.

Section 2 · Core Theory & Visual Architecture Diagrams

Comparing the Big Four: STRIDE, PASTA, LINDDUN & Attack Trees

STRIDE (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege) is software-centric. Each letter maps directly to a security property engineers understand: Authentication (S), Integrity (T), Non-repudiation (R), Confidentiality (I), Availability (D), and Authorization (E).

PASTA (Process for Attack Simulation and Threat Analysis) is risk-centric across 7 stages—starting with business objectives and regulatory impact before decomposing tech and simulating attacks. LINDDUN is privacy-centric (Linkability, Identifiability, Non-repudiation, Detectability, Disclosure, Unawareness, Non-compliance), essential for GDPR/CCPA systems.

Attack Trees are goal-centric: place an attacker goal at the root ("Steal Customer Signing Keys") and branch downward with OR nodes (alternative paths) and AND nodes (conditions that must all hold). Combining STRIDE for breadth with Attack Trees for Crown Jewels is a superpower.

STRIDE — Best for Daily Engineering

Fast, repeatable, and maps directly to concrete technical controls on Data Flow Diagrams.

PASTA — Best for Executive Risk Alignment

Connects threat scenarios directly to financial impact and business priorities across 7 structured stages.

LINDDUN — Best for Privacy & Compliance

Catches tracking, linkability, and metadata leakage that classic security reviews miss.

Attack Trees — Best for Crown Jewel Depth

Decomposes high-value targets into concrete AND/OR exploit prerequisites.

The Methodology Selector MatrixANNOTATED VISUAL WALKTHROUGH
1. STRIDE (Software-Centric)Spoofing, Tampering, Repudiation, Info Disc, DoS, EoP2. PASTA (Risk-Centric)Aligns business objectives with 7-stage attack simulation3. LINDDUN (Privacy-Centric)Linkability, Identifiability, Non-repudiation, Detectability4. Attack Trees (Goal-Centric)AND/OR tree mapping every concrete path to a Crown Jewel
1
STRIDE Per-Element

Apply S/T/R/I/D/E systematically to every Process, Data Store, and Data Flow.

2
LINDDUN Privacy Lens

Crucial when "encrypted" data can still be correlated via timestamps or IP metadata.

3
Attack Tree Leaf Nodes

Every leaf node becomes a concrete test case or security ticket.

Choose STRIDE for engineering velocity, PASTA for business alignment, LINDDUN for privacy, and Attack Trees for deep exploit modeling.ANNOTATED ARCHITECTURE DIAGRAM
Section 3 · Real-World Case Study & Attack Walkthrough

Case Study: Why Classic Security Missed a Privacy Breach (Until LINDDUN)

A fitness app encrypted all GPS coordinates in transit (TLS 1.3) and at rest (AES-256) and enforced strong OAuth tokens. By STRIDE alone, the public leaderboard API looked clean—until researchers realized public pace-per-minute + start timestamps allowed anyone to infer home addresses.

STRIDE Check

Transport & Auth Passed

TLS, OAuth, and database encryption satisfied classic confidentiality and spoofing checks.

LINDDUN Lens

Linkability & Identifiability Fired

LINDDUN asks: "Can an external observer link anonymized records back to a real person?" Public start/end zones made home locations trivial to triangulate.

Design Fix

Privacy Zones & Spatial Fuzzing

Trimming the first and last 300 meters of public routes eliminated the linkability risk at zero performance cost.

Design Lesson Learned:Security and privacy overlap, but they are not identical. Adding a quick LINDDUN pass on user-facing features catches metadata leaks early.
Section 4 · Cognitive Breaks & Self-Check

There Are No Dumb Questions

Candid answers to the skeptical questions every security engineer asks first.

Q:Do I need to run all four methodologies on every single pull request?
A:Definitely not! Use lightweight STRIDE for normal features, add LINDDUN when handling personal/behavioral data, and draw an Attack Tree for Crown Jewel systems.
Q:Isn’t PASTA too heavy for a 2-week Agile sprint?
A:Full 7-stage PASTA is usually run quarterly on flagship platforms or major architecture overhauls, while STRIDE fits inside a 30-minute sprint design review.
Q:What is the difference between an `AND` node and an `OR` node in an Attack Tree?
A:OR means the attacker only needs ONE of the child steps to succeed. AND means the attacker must achieve ALL child steps—so breaking just one AND leaf blocks that entire branch!
FIRESIDE CHAT · CONCEPT DEBATE

STRIDE vs. PASTA in Modern Engineering Orgs

PASTA PuristRisk Strategist

“Without tying threats to business objectives first, engineers waste time fixing low-impact theoretical bugs!”

STRIDE PragmatistStaff Engineer

“True—so we tag Crown Jewels for business impact, then run fast STRIDE on every Data Flow. Best of both worlds without a 3-week workshop!”

INTERACTIVE EXERCISE

Sharpen Your Pencil · 60-Second Brain Challenge

You are reviewing a healthcare analytics portal that strips patient names from exported CSVs, but leaves exact birthdates, 5-digit ZIP codes, and visit timestamps intact. Which methodology specifically catches this re-identification risk?

Lesson 02 Sticky-Note Recap
  • ▸STRIDE is the fastest, most developer-friendly lens for catching technical flaws on Data Flow Diagrams.
  • ▸PASTA connects technical threats to business objectives and financial impact across 7 stages.
  • ▸LINDDUN uncovers privacy blind spots (Linkability, Identifiability, Detectability) that encryption alone cannot solve.
  • ▸Attack Trees map concrete AND/OR paths to Crown Jewels—break one AND prerequisite to neutralize the chain.
Optional Interactive Practice

Practice running deterministic STRIDE checks on your own topology in NodeMotion’s Live Canvas →

Practice This Pattern in NodeMotion's Live Canvas