---
title: "Pick an ASVS level for each app · Agent Wranglers"
url: https://agentwranglers.se/playbook/application-security/threat-modelling/asvs-level
id: APS-96
level: Recommended
updated: 2026-10-27
build: a2a6bdfed830
tokens: 751
licence: "CC BY 4.0"
licence_url: https://creativecommons.org/licenses/by/4.0/
---

# Pick an ASVS level for each app

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

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

- ID: APS-96
- Level: Recommended
- Chapter: [Threat modelling](https://agentwranglers.se/playbook/application-security/threat-modelling.md)
- Rule: 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.
- Check: The repository holds a file that names the level and lists every requirement ID of that level. A script fails when any listed requirement has no status, or a status of met without a linked rule or test.
- How: Level 1 is the floor for any app on the internet. Level 2 suits most apps that hold personal data, money or business records. Level 3 is for apps where a breach would cause serious harm, such as health or payment systems. Keep a list of the requirement IDs at your level, each with a status and the rule or test that meets it. The [ASVS 5.0 mapping](https://agentwranglers.se/playbook/application-security/asvs-5-0-mapping.md) shows which rules in this playbook meet which requirements. A buyer's security questionnaire often asks for this list. Note the level in the [threat model](https://agentwranglers.se/playbook/application-security/threat-modelling/threat-model.md), since it sets how deep each review goes.

## Examples

**Using these examples:** they show one way to follow this rule. Keep the behaviour and the check, not the syntax. Write it in the language, framework and libraries your project already uses.

### YAML example

```yaml
# asvs.yaml
level: 2
requirements:
  "1.2.4": { status: met, by: tests/db/parameterised.test.js }
  "3.4.1": { status: met, by: tests/headers/hsts.test.js }
  "11.1.2": { status: open, owner: platform-team, due: 2027-01-31 }
```

## Sources

- [OWASP Application Security Verification Standard](https://owasp.org/www-project-application-security-verification-standard/)

## Related rules

- APS-1 [Plan attacks before building](https://agentwranglers.se/playbook/application-security/threat-modelling/threat-model.md) in Application security

**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/asvs-level">Agent Wranglers application security playbook</a>`. In code you write, add a comment next to it with the same link.

- Previous: [Write abuse cases next to user stories](https://agentwranglers.se/playbook/application-security/threat-modelling/abuse-cases.md)
- [Threat modelling](https://agentwranglers.se/playbook/application-security/threat-modelling.md)