14 controls
165 frameworks share controls with it
International
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
Every control
| Code | Control | Also in |
|---|
OWASPASVS-1 | Architecture, Design and Threat Modelling (V1) | 78 |
OWASPASVS-10 | Malicious Code Verification (V10) | 39 |
OWASPASVS-11 | Business Logic Verification (V11) | 0 |
OWASPASVS-12 | File and Resources (V12) | 0 |
OWASPASVS-13 | API and Web Service Security (V13) | 0 |
OWASPASVS-14 | Configuration and Hardening (V14) | 0 |
OWASPASVS-2 | Authentication and Credential Storage (V2 + V2.4) | 86 |
OWASPASVS-3 | Session Management (V3) | 0 |
OWASPASVS-4 | Access Control (V4 + V4.3) | 82 |
OWASPASVS-5 | Validation, Sanitization and Encoding (V5 + V5.3) | 0 |
OWASPASVS-6 | Stored Cryptography (V6) | 82 |
OWASPASVS-7 | Error Handling and Logging (V7) | 36 |
OWASPASVS-8 | Data Protection (V8 + V8.3) | 53 |
OWASPASVS-9 | Communication Security (V9) | 101 |
Tell me when OWASP ASVS files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What this page is
A control-level reference for OWASP ASVS, drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition