HomeResourcesProject resourcesTemplatesA one-page threat model

WORKSHEET

A one-page threat model

Map the records API, ownership risk, and evidence for your control.

Where it goes

Open in any text editor. Add your own availability risk and test.

Download threat-model.txt ↓Open lab 01 →

How to use this resource

  1. Save threat-model.txt in your extracted project folder and open it in a text editor.
  2. Read the six example lines about Alice’s private note and Bob’s request.
  3. Fill in your owner/date and all four “Your turn” prompts.
  4. Save the file. A finished worksheet names an availability risk, mitigation owner, test, and assumption.

No terminal is needed. Lab 01 explains each prompt with an example.

threat-model.txt
THREAT MODEL / RECORDS API
Owner: __________   Review date: __________

1. ASSET: private note titles and their ownership.
2. FLOW: browser -> GET /records/:id -> identity lookup -> record lookup.
3. BOUNDARY: caller-controlled record ID enters the service.
4. THREAT: Bob requests Alice's record using a valid Bob identity.
5. CONTROL: compare authenticated user with record.owner on the server.
6. PROOF: Bob receives 403; response contains no record title.

Your turn:
Add one risk affecting availability: __________
Choose a mitigation and owner: __________
Describe how you would test it: __________
Record an assumption that may change: __________

Scope: synthetic local learning fixture. Real systems also need production
identity, data storage, transport security, abuse prevention, and operations.