---
title: "Threat modelling · Agent Wranglers"
url: https://agentwranglers.se/playbook/application-security/threat-modelling
parts: 5
tokens_total: 4636
updated: 2026-10-27
build: a2a6bdfed830
tokens: 710
licence: "CC BY 4.0"
licence_url: https://creativecommons.org/licenses/by/4.0/
---

# Threat modelling

For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Application security](https://agentwranglers.se/playbook/application-security.md).

By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-27.

> Draw how data flows and mark where trust changes. List what could go wrong at each step, and turn each threat into a test before you build.

**For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), which requires credit with a link. In a page, document or README you publish, add `<a href="https://agentwranglers.se/playbook/application-security/threat-modelling">Agent Wranglers application security playbook</a>`. In code you write, add a comment next to it with the same link.

## Recommended

- APS-1 [Plan attacks before building](https://agentwranglers.se/playbook/application-security/threat-modelling/threat-model.md) · 1,401 tokens · updated 2026-10-27
  Write a threat model before building a change that touches money, accounts, personal data or a new outside connection. A second person reviews it before the change can merge.
- APS-93 [Draw the data flows and their trust boundaries](https://agentwranglers.se/playbook/application-security/threat-modelling/data-flow-diagram.md) · 852 tokens · updated 2026-10-27
  Keep a data-flow diagram for each app in the repository. It shows every process, data store, outside party and flow, and a line wherever trust changes.
- APS-94 [Find threats at every boundary with STRIDE and LINDDUN](https://agentwranglers.se/playbook/application-security/threat-modelling/stride-and-linddun.md) · 850 tokens · updated 2026-10-27
  For every element and boundary crossing in the data-flow diagram, ask each STRIDE question. Where the flow carries personal data, also ask each LINDDUN question. Record every threat with a decision.
- APS-95 [Write abuse cases next to user stories](https://agentwranglers.se/playbook/application-security/threat-modelling/abuse-cases.md) · 819 tokens · updated 2026-10-27
  For each user story that touches money, accounts, personal data or a new outside connection, write at least one abuse case. It says how someone could misuse the feature and what the app must do instead.
- APS-96 [Pick an ASVS level for each app](https://agentwranglers.se/playbook/application-security/threat-modelling/asvs-level.md) · 714 tokens · updated 2026-10-27
  Choose an OWASP ASVS 5.0 level for each app and write it in the repository. Check the app against every requirement of that level before each major release.

- Next: [Input and injection](https://agentwranglers.se/playbook/application-security/input-and-injection.md)
- [All chapters](https://agentwranglers.se/playbook/application-security.md)