Eleven linked layers
Presented at ThreatModCon 2025 in Barcelona, and live since: eleven readable threat-model layers, linked, running from the customer relationship down to the compute that serves it. This is the strongest artefact this site has, so it leads.
"One model answers what could go wrong here. Eleven linked models answer what does this line of code put at risk."
The eleven layers
Each layer is its own threat model; each links to the one above and below it, so a finding at any layer can be traced up to what it puts at risk commercially, or down to the exact code that produces it.
The vault, live
The vault is the artefact, and it is embedded here rather than copied: rebuilding eleven threat models as static site pages would turn a published vault demonstrating the platform's own argument into a screenshot of one. Open it directly:
Customer → Business → Application → Component → Package → Class → Method → Source Code → Environment → Runtime → Compute. Live, and built to run offline.
Two demonstrations riding on top of it
One SQL injection, four audiences
A single SQL injection in a payment gateway, retold for Board, CISO, CTO and Developer — the practical form of Linking Threat Models with Semantic Business Graphs. Same finding, different altitude, same underlying graph.
From "everything is critical" to risk-based prioritisation
Five walkthroughs moving from an undifferentiated pile of findings to a mapped, prioritised set — the threat-prioritisation application of Wardley mapping. The mapping technique itself lives at wardley-maps.sgit.ai; this site keeps only the application.
How it runs offline
The vault was adapted for offline operation: d3, three.js and tween.js are inlined at pinned versions rather than loaded from a CDN, data is read through sg.vfs.readText() on vault-relative paths, and the network fallback reports failure rather than silently hiding it. A data-integrity note worth stating because it models the discipline the whole network runs on: two upstream JSON files had formatting errors, and both were repaired "using only bracket adjustments and repositioning — no field edits or invented content."
See also
/validated/ is this site's other signature page — a single threat model checked, finding by finding, against the code. /graph/ explains the schema this vault's data follows, and draws the line between what this vault proves today and what the wider papers still argue for.