STRIDE Threat Model Risk Explorer

Data Flow

Select a flow to score

DREAD Factors (0–10)

Damage potential 5

Reproducibility 5

Exploitability 5

Affected users and discoverability are fixed by this system's architecture — see readout below.

Live Risk

DREAD risk (this flow)

5.0 / 10

STRIDE category

Spoofing

Affected-users factor

4.0 / 10

Discoverability factor

9.0 / 10

System-wide aggregate risk (6 flows)

5.0 / 10

Highest-risk flow right now

—

How it works

Each arrow in the 3D scene is one data flow in a small five-component system: a user, a public web server, an internal API, an admin console and a database. Every flow is pre-classified under Microsoft's STRIDE threat model (the category it is most exposed to), and its risk is scored with the classic DREAD formula:

Risk = (D + R + E + A + Di) / 5   (each factor 0–10)

D  = Damage potential      — how bad if exploited
R  = Reproducibility       — how reliably it can be triggered
E  = Exploitability        — how much skill/tooling it needs
A  = Affected users        — fixed here by the sensitivity of
                              the flow's destination component
Di = Discoverability       — fixed here by whether the flow
                              crosses the public/internal
                              trust boundary

You control D, R and E with the sliders; A and Di are derived from the architecture itself (a flow ending at the database affects more, and a public-facing flow is easier to discover than an internal one) — exactly how a real threat-modeling session separates "how you'd defend it" from "what it structurally exposes."

Pulses travelling along each edge are the data flow itself — their speed and color (green → amber → red) track that flow's live DREAD score.
The system-wide aggregate averages all six flows' current scores, so hardening one flow's D/R/E only helps the whole system if the others aren't quietly carrying more risk.
This mirrors real practice: STRIDE finds what kind of threat a flow faces, DREAD ranks how urgently to fix it, and the two together are how security teams triage a system diagram instead of treating every arrow as equally dangerous.

Low risk (0–3) Medium risk (4–6) High risk (7–10)

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.