STRIDE Threat-Model Worksheet
A guided Spoofing/Tampering/Repudiation/Info-Disclosure/DoS/Elevation worksheet, exportable as Markdown.
STRIDE is a checklist for asking "what could go wrong here" in a structured way: Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, and Elevation of privilege. Six prompts, applied to one component at a time, catch a surprising share of design flaws before any code exists.
How to use it
- Name the system or feature being modelled.
- Work through each STRIDE category for that component.
- Download the completed worksheet as Markdown.
What to take away
Model one component at a time
"Our whole platform" produces nothing useful. "The password reset endpoint" produces real findings in twenty minutes.
Each letter maps to a control
Spoofing to authentication, Tampering to integrity, Repudiation to logging, Information disclosure to confidentiality, DoS to availability, Elevation to authorisation. That mapping turns a threat into a task.
Design-time bugs are the expensive ones
A missing authorisation check in a design costs a conversation. The same gap found in production costs an incident.
Frequently asked questions
When should threat modelling happen?
While the design is still changeable — before or during implementation. Modelling after release still finds things, but the findings are much more expensive to act on.
Do I need a data flow diagram first?
A rough sketch of components, trust boundaries and data flows makes STRIDE far more productive. It does not need to be formal; a whiteboard photo works.
How does STRIDE compare to PASTA or attack trees?
STRIDE is the fastest to teach and the easiest to run in a normal team meeting. The others go deeper and cost more time; STRIDE is where nearly everyone should start.
Where this fits in the course
This security tool pairs with Path 22 — DevSecOps & AppSec — see all 26 learning paths.
It runs entirely in your browser: nothing is uploaded, no account is needed, and it is free.
Related
- MITRE ATT&CK Mapper — A searchable reference of real ATT&CK tactics and techniques, tied back to where this course covers each one.
- Risk Register Builder — Add risks with likelihood and impact, get an auto-scored severity, and export the register as Markdown.
- Secure Code Review Toy — Paste a code snippet and get flagged patterns — eval, string-built SQL, hardcoded secrets. Not a real SAST tool, but trains the eye.
- Vulnerability Report Writer — A guided form that forces good structure — title, severity, steps to reproduce, impact, remediation — then exports clean Markdown or a printable PDF.