Threat models
One file per feature, named <feature>.md, written before the feature is built. Copy the template below.
# Threat model: <feature>
## Specs and references- Normative spec(s):- OWASP cheat sheet:- ASVS requirements covered:
## AssetsWhat we're protecting (e.g. session tokens, password hashes, account ownership).
## Trust boundariesWhere untrusted data enters: HTTP request, FFI boundary, email link, IdP response, etc.
## Attacker capabilitiesWhat an attacker controls (e.g. request headers, timing measurements, a victim's email inbox scanner).
## Threats (STRIDE)| # | Threat | Category | Mitigation | Test ||---|--------|----------|------------|------|| T1 | | | | |
## InvariantsThings that must never happen, written as statements the tests check.