asvs-requirements

Provide OWASP ASVS 5.0 requirements with chapter mappings and verification levels.

9|2|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/Zate/cc-plugins --skill asvs-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asvs-requirements
Source: https://github.com/Zate/cc-plugins/tree/main/plugins/security/skills/asvs-requirements
Command: npx skills add https://github.com/Zate/cc-plugins --skill asvs-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralized access to OWASP ASVS 5.0 requirements for security audits, including chapter mappings and verification levels.

Core Features & Use Cases

  • Chapter mapping: quick reference to V1-V17 domains.
  • Verification levels: L1-L3 depth guidance for audits.
  • Auditor alignment: helps plan checks and evidence collection.

Quick Start

Use ASVS references to scope an audit and map findings to ASVS controls.

Frequently Asked Questions about asvs-requirements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use ASVS requirements to scope a security audit?

ASVS 5.0 provides 17 chapters (V1-V17) mapping functional and technical security domains. Reference the relevant chapters for your audit scope, then select verification levels (L1-L3) to define audit depth—L1 for foundational controls, L3 for comprehensive coverage. This guides which requirements to verify and what evidence to collect.

What are ASVS verification levels and how do they apply to audits?

ASVS defines three verification levels: L1 covers basic security controls, L2 addresses advanced threats, and L3 provides defense-in-depth. Use these levels to align audit scope with organizational risk tolerance and resources, ensuring checks match the required assurance depth.

Can I map security findings across all ASVS domains?

Yes. The ASVS database supports cross-domain references across all 17 chapters, enabling you to categorize and trace findings to specific requirements. This creates structured audit reports and ensures comprehensive coverage without gaps or duplicates.

How do I build an auditor agent using ASVS requirements?

ASVS 5.0 provides structured functional and technical requirements accessible as a database. Parse the relevant chapters and verification levels for your audit scope, then embed this mapping into your agent logic to automate requirement selection, evidence matching, and finding classification.

What's the difference between functional and technical ASVS requirements?

Functional requirements define what security controls must achieve (e.g., authentication enforcement). Technical requirements specify how to implement them (e.g., password hashing algorithms). ASVS 5.0 structures both separately, enabling audit planning at either abstraction level.