OWASP ASVS 5.0 Application Security Verification Standard Guide
An in-depth technical guide to OWASP ASVS 5.0, covering Level 1 to Level 3 verification baselines, 17 security chapters, and penetration testing methodologies for modern web applications.
- Target Audience
- Software development teams, security architects, DevSecOps engineers, and penetration testers assessing web applications and cloud services
- Testing and Review Frequency
- Continuous verification within CI/CD pipelines, supplemented by annual penetration testing or prior to major software releases
- Assessment Scope
- 17 security chapters (V1 to V17) covering architecture, authentication, access control, cryptography, tokens, APIs, and WebRTC
- Relevant Risks
- Business logic vulnerabilities, authorization bypasses (BOLA/BFLA), token counterfeiting, and enterprise procurement disqualification
The Three Verification Levels (L1, L2, L3) in ASVS 5.0
Stratified application security verification aligned with organizational risk, from automated baselines to critical infrastructure.

An explanatory overview. Read the article for scope, applicability and supporting evidence.
- L1: first-layer defence — Start with essential requirements
- L2: broader coverage — Combine L1 and L2 requirements
- L3: defence in depth — Include applicable requirements at all levels

- Level 1 contains 70 requirements for an initial verification baseline. Select methods and evidence for each applicable requirement. Black-box penetration testing alone does not establish complete coverage.
- Level 2 (L2 - Standard): Standard verification baseline for business applications processing PII, financial transactions, or sensitive corporate data. Includes applicable L1 and L2 requirements, approximately 70% of the catalog. Select verification methods for each requirement.
- Level 3 includes applicable requirements from all three levels in the 345-requirement catalog. Select the target level according to risk and document exclusions for requirements that do not apply.
- Documented Security Decisions: ASVS 5.0 introduces explicit upfront security decision documentation requirements at the beginning of core chapters, ensuring security design choices remain auditable throughout the application lifecycle.
17 Security Chapters and Modern Architectural Enhancements in ASVS 5.0
Categorization of V1 through V17 verification chapters, featuring dedicated controls for modern tokens, federated identity, and real-time communications.

An explanatory overview. Read the article for scope, applicability and supporting evidence.
- V1 — Encoding and Sanitization
- V2 — Validation and Business Logic
- V3 — Web Frontend Security
- V4 — API and Web Service
- V5 — File Handling
- V6 — Authentication
- V7 — Session Management
- V8 — Authorization
- V9 — Self-contained Tokens
- V10 — OAuth and OIDC
- V11 — Cryptography
- V12 — Secure Communication
- V13 — Configuration
- V14 — Data Protection
- V15 — Secure Coding and Architecture
- V16 — Security Logging and Error Handling
- V17 — WebRTC

- Dedicated Chapters for Self-contained Tokens (V9) and OAuth/OIDC (V10): ASVS 5.0 establishes separate domains for JWT, PASETO, and federated identity flows, enforcing cryptographic signature validation, claim verification, and token lifecycle policies.
- Real-Time Communications via WebRTC (V17): New verification requirements for peer-to-peer data channels, media transport security, signaling authorization, and mandatory DTLS/SRTP encryption.
- Secure Coding and Architecture (V15): Upfront verification of architectural security, explicit trust boundaries, least-privilege compartmentalization, and attack surface minimization.
- Security Logging and Error Handling (V16): Rigorous standards for tamper-resistant audit trails, protection against log injection, and strict prevention of sensitive PII or credentials in log streams.
Integrating ASVS into DevSecOps Pipelines and Software Attestation
Practical implementation of ASVS 5.0 across penetration testing, automated security gates, and audit evidence delivery.

Tools support verification, but assessed requirements need evidence. OWASP does not certify applications or assessors.
- Define scope — Select level and applicable requirements
- Use supporting tools — Review code and configuration
- Perform manual verification — Test access and business logic
- Remediate and report — Retest and record results and limitations

- Target Verification Level Scoping: Establish the target ASVS level (L1, L2, or L3) during system conception, translating requirements into enforceable acceptance criteria within the Secure SDLC.
- Hybrid Verification Pipeline: Combine automated SAST, DAST, and SCA tooling in CI/CD pipelines with manual, independent penetration testing to comprehensively audit V2 business logic and V8 authorization controls.
- Audit-Ready Verification Reports: Generate structured attestation documentation mapping test outcomes directly to ASVS clause IDs, complete with proof-of-concept logs, clean retest records, and formally approved risk exceptions.
- Harmonization with Global Standards: ASVS verification evidence can support other assessments where the tested requirements map to the applicable controls. Assess each framework’s scope and evidence requirements separately.
References and Assessment Scope
Summary of source references, assessment scope, and review timing in the context of each item.
| Reference | Topic | Assessment Scope | Testing Cycle |
|---|---|---|---|
| ASVS Level 1 (L1 - Baseline) | Essential Baseline Application Security Verification | Protects against common opportunistic threats (70 requirements) covering configuration, access control and input validation, with methods and evidence selected per requirement | Set verification timing according to application risk and changes |
| ASVS Level 2 (L2 - Standard) | Standard Application Security Verification for Sensitive Data | Covers applications handling PII or financial transactions; includes applicable L1 and L2 requirements, approximately 70% of the full catalog | Set verification timing according to application risk and changes |
| ASVS Level 3 (L3 - Advanced) | Advanced Security Verification for Critical Infrastructure | Verify applicable requirements from all three levels in the 345-requirement catalog and document justified exclusions. | Comprehensive audit during architectural reviews and ongoing risk cycles |
| ASVS Chapter V9 & V10 | Self-contained Tokens and OAuth / OpenID Connect Verification | Cryptographic validation of JWT/PASETO signatures, token lifecycles, scope enforcement, replay mitigations, and redirect URIs | Evaluated whenever identity providers, authentication flows, or API gateways change |
Implementation Checklist
Select items your organization has completed. The percentage shows selected items only and does not assess security or compliance.
Frequently Asked Questions (FAQ)
Key answers and practical guidance addressing common compliance questions.
How does OWASP ASVS 5.0 differ from the OWASP Top 10?
The OWASP Top 10 is an awareness document highlighting the ten most prevalent web application security risks. In contrast, OWASP ASVS is an exhaustive technical standard comprising 17 chapters and 345 specific verification requirements designed as an actionable baseline for designing, building, and formally auditing secure applications.
How should organizations decide between ASVS Level 1, Level 2, and Level 3?
Choose a level according to application risk, data sensitivity and user expectations. L1 is a starting point, with L2 and L3 adding coverage. Verify applicable requirements and document justified exclusions.
Does ASVS verification require source code access?
ASVS does not prescribe one verification method. Assessors may need documentation, source code, configuration and developer input alongside testing, especially for L2 and L3. Select evidence that verifies each applicable requirement and disclose the methods in the report.
