Part 7 of 12 · 1 min read
How to build it so it holds up
- Start with assets and the attacker's goals, not with a list of attacks.
- Draw the data-flow diagram with trust boundaries, including the model, tools, memory, vector stores, traces and third-party services.
- Enumerate with STRIDE per element, add agent-specific threats (injection, excessive agency, memory poisoning, tool and supply-chain risks, data leakage through traces) and check the MAESTRO layers.
- Flag trust-boundary crossings without controls first, and egress channels separately.
- Use attack trees for the top goals, with explicit assumptions; record who provided each number.
- Pick mitigations by covering all paths, counting shared controls, and keep a cost.
- Record decisions: mitigate, accept (with an owner and a date), transfer or avoid.
- Tie each mitigation to a test (module 8) and to monitoring (Level 9).
- Revisit on change: new tool, new data source, new model, new tenant, new region.
- Keep it short and living: a one-page model that is updated beats a long one that is not.