AI STRIDE threat model generator
Paste a system design and get its assets, trust boundaries, data flows and a STRIDE-per-element threat list.
Your key stays in your browser.It goes straight to the provider, never to our servers, and we neither log nor keep it. Use a dedicated key with a spending cap, and delete it in the provider's dashboard when you are done.
Input
Result
The result will appear here.STRIDE — Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege — is the checklist Microsoft introduced for walking through a design and asking, component by component, what could go wrong. Doing it properly takes an afternoon at a whiteboard. Paste a design description — the services, the data stores, who logs in and how, where the secrets live — and this produces the working draft: the assets worth protecting, the trust boundaries, the data flows that cross them, and a threat list giving each threat's category, existing mitigation, proposed mitigation, likelihood, impact and severity. It is meant to start a security review, not to replace one; the output is only as good as the design you describe.
How it works
- The prompt is Fabric's create_stride_threat_model pattern: its five sections, its ten threat fields and its instruction to separate realistic risk from fantastical risk are kept, and a threat judged not worth mitigating comes with a note saying why.
- Choose one ten-column table, which pastes into a wiki, or one card per threat, which stays readable in a narrow window and in tools that mangle wide Markdown tables.
- Prose follows your language, while STRIDE category names and the low / medium / high / critical severities stay in English so that results can be filtered and compared across reviews.
- A design document shows where the weak points are, so it matters that it goes only from this tab to your AI provider, under a key you should create for the review and revoke when the review is over.
Where your data goes
With your own key, what you type and the key go from your browser straight to the provider you choose; neither passes through Hysen Labs. In hosted mode, your text goes through our server to our provider (DeepSeek) and is billed in credits; we keep the token counts and cost of each run for billing, never the text itself or the answer. How the provider handles the text is governed by its own privacy policy.
This tool handles keys and credentials, so nothing about a run is saved, not even to your own history.
About your API key
We do not collect, store or leak your key: it lives only in this page's memory (unless you tick “remember in this tab”) and is gone when you close it. Still, treat any key you have pasted into a web page with care — create a dedicated key with a spending cap for use here, and delete or rotate it in your provider's dashboard when you are done.
What it costs
This tool is free, with no sign-in and no points.
Common questions
- How detailed does the design description need to be?
- Name every component, every data store, every external party, how each one authenticates and where secrets are kept. The sample — a webhook relay with a queue, workers, a dashboard and signing secrets in environment variables — is roughly the minimum. Anything you leave out cannot be threatened, and turns up under questions and assumptions instead.
- Can I trust the risk severities?
- Treat them as a proposal. The model judges likelihood from the design and from common attack patterns, but it does not know your threat actors, your compliance obligations or what already sits in front of the system. Re-rank them in the review; the value is in the list being complete, not in the ranking being right.
- What is STRIDE per element, compared with plain STRIDE?
- Plain STRIDE asks the six questions of the system as a whole. Per element asks them of each component and data flow separately, and only the categories that fit — a data store can be tampered with but does not spoof anyone. The result is longer and far more specific, which is why the pattern uses it.
- Is it safe to paste an internal architecture here?
- This site receives nothing; the text goes from your browser to the provider under your account and is covered by that provider's API data terms. For anything under NDA, read those terms first, or run it against a local model through Ollama, which the provider list includes.
The open-source behind it
This tool's prompt is adapted from danielmiessler/Fabric (MIT) and runs on the model you choose. To use the same capability from the command line or inside your own program, start with that project.
danielmiessler/FabricAlso known as
- stride threat model
- threat modeling tool
- stride threat model template
- ai threat modeling
- security design review
- threat model example