The model

A wyrm threat model is an Open Threat Model (OTM) file β€” seven kinds of object that reference each other. Here's what each is, how they connect, and β€” the part that trips people up β€” who fills each one in.

Who fills what

Three sources populate the model, and it's worth knowing which is which:

The seven objects

ObjectWhat it isReferencesFilled by
projectName/owner of the system being modeledβ€”init
trustZonesSecurity boundaries, each with a trustRating 0–100 (internetβ‰ˆ10, privateβ‰ˆ80)β€”init (network/zone resources)
componentsServices, datastores, gateways, identities β€” the nodesparent.trustZone β†’ a zone Β· assets β†’ assetsinit
assetsThe data worth protecting, with CIA ratings 0–100referenced by components & dataflowsyou (sensitivity isn't in infra)
dataflowsTraffic between components β€” the edges. Tags like tls mark encryptionsource/destination β†’ components Β· assets β†’ assetsinit (compose/k8s) Β· you (Terraform, via flows:)
mitigationsControls that reduce risk (WAF, auth, encryption). Link one with appliesTo (element ids) + riskReduction 0–100 and analyze down-ranks matching findings β€” 100 resolves them. addresses scopes it to specific rules so a WAF can't mute an encryption findingappliesTo β†’ components/dataflowsinit (detected WAF/Armor, untargeted) Β· you (link + rate)
threatsManually-declared threats. Findings are NOT here β€” analyze computes thoseβ€”rarely used; usually []

So an empty assets: [] / dataflows: [] on a fresh Terraform baseline is expected β€” Terraform describes resources, not sensitivity or traffic. That's the annotation step. And threats: [] stays empty on purpose: your threats live in wyrm analyze, computed fresh every run.

How they connect

flowchart LR
  P["project"] --- Z["trustZones"]
  Z -->|contains| C["components"]
  C -->|source / destination| D["dataflows"]
  A["assets"] -.->|processed / stored by| C
  A -.->|carried on| D
  M["mitigations"] -.->|reduce risk on| D
  T["threats = computed by analyze,\nnot stored in the file"]
  classDef you stroke:#ffd24d,stroke-width:2px;
  class A,D you
  classDef derived stroke:#5db0ff,stroke-dasharray:4;
  class T derived
      

Amber = the bits you supply (assets, and β€” for Terraform β€” dataflows). Blue = derived, never written to the file.

How a finding happens

A rule reads the graph: e.g. a dataflow whose source and destination live in different trustZones, carrying an asset with high confidentiality, with no tls tag β†’ WYRM-T001. Every input to that sentence is an object above. Miss the asset (sensitivity) or the dataflow (traffic) and the rule can't fire β€” which is why the annotation step matters, and why a bare Terraform inventory reports nothing until you add context.