Threat Modeling
Find the Flaws in the Design
Built by working security engineers. You get a finished system architecture, you find the threats in it — no home lab, no setup, just the skill security design reviews actually test.
Guided by The Strategist
What it is
Threat Modeling, defined
Threat modeling is reviewing a system's design — not its code — and finding how it can be attacked before it's built. You read an architecture diagram, trace what talks to what and who trusts whom, spot the threats, put each one in the right category, and prescribe the fix. It's the exact exercise security design reviews and security interviews put in front of you.
The career
A skill you get hired for
The cheapest security bug to fix is the one caught in the design review, before any code exists. Companies run these reviews on every major feature — and interviewers use 'threat model this system' as a standard screen for security roles.
Builds toward
Product Security Engineer
Typical salary
$150K/yr avg
Market demand
500K+ open US roles
Who you'd work alongside
- Product & application security engineers
- Teams running security design reviews
- Engineers who own the security section of a design doc
- Anyone preparing for security engineering interviews
The DefendTheOrg approach
How you'll learn it
Every lab is a finished system architecture — the kind an engineering team would bring to a real design review. No home lab, no environment to stand up. You do the review, and you're graded the way a real reviewer's work is judged:
Find the threats
Read the design, trace the trust boundaries, and identify where it breaks — spoofed identities, leaked data, paths that skip the checks. Finding the real issues without flagging noise is the core skill.
Categorize them correctly
Tag each threat with the right category, using the same standard framework (STRIDE) real security teams use. Naming the threat correctly is how reviewers communicate — and how interviews are scored.
Prescribe the fix
A threat without a mitigation is just a complaint. You recommend the design change that closes it — the judgment call that separates a reviewer from a checklist.
Stuck? Get walked through it.
Every Easy and Medium lab has a walkthrough from The Strategist — one hint at a time, with a chance to try each step yourself before the answer. You get three a week, and using one never touches your score. It teaches the reasoning, not the solution.
Try it yourself
A taste of the real lab
This is a simplified, no-signup slice of a Threat Modeling lab — make your call and see how it's graded. The real labs go deeper.
Review the design
Click a component or a flow, then tag the threats you can justify from what's on screen.
Select a component or a flow
Two things here are worth flagging. One is bait.
Push yourself
Where Hard and Expert labs take you
Every skill scales from your first lab to genuinely hard reasoning. Difficulty isn't a bigger wall — it's deeper thinking.
Hard
Hard labs are larger systems where the threats aren't local — a single service can look fine while the way two components trust each other is the flaw. You have to reason across the whole diagram.
Expert
Expert labs mirror real design reviews: deliberately plausible architectures where most of the design is sound, the dangerous flaws hide behind reasonable-looking decisions, and calling something a threat when it isn't costs you — just like it does in a real review.
Start threat modeling training
Hands-on labs built from real engagement data. Learn by doing — guided by The Strategist.