Threat model — notes-api (fill in)¶
Before you fill this in
Start in: Module 1 lab. Save as: docs/capstone/work/threat-model.md. Edit the copy, never this template.
Example: Helix threat model. If your copy mentions Dana, HELIX_DEBUG, or ticket 42, you’ve modelled the wrong system.
Diagram¶
Draw the compose stack as you found it: every process, every port it binds, every data flow. Mark each trust boundary a request crosses.
Assets¶
| Asset | Sensitivity | Why it matters here |
|---|---|---|
Trust boundaries¶
| From | To | Control today | Residual |
|---|---|---|---|
Top threats¶
Name the actor, the boundary, and the asset. “Hackers” is not a threat.
1. 2. 3. 4. 5.
Residual risk statement¶
Write one paragraph: what can still go wrong after the controls above, and who has accepted that.