sec-compliance

Audits code against OWASP ASVS controls and produces an evidence-based compliance gap report.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/real-case/marvin-toolkit --skill sec-compliance-real-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sec-compliance
Source: https://github.com/real-case/marvin-toolkit/tree/main/plugins/marvin/skills/sec-compliance
Command: npx skills add https://github.com/real-case/marvin-toolkit --skill sec-compliance-real-case

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams preparing for security reviews or certifications lack a structured way to verify their application against the OWASP ASVS standard, often relying on guesswork instead of evidence-backed control-by-control assessment. ## Core Features & Use Cases - ASVS Level Selection: Supports L1, L2, and L3 verification levels with guidance on which chapters apply to your application type. - Automated and Manual Verification: Runs grep-based checks for authentication, session, validation, TLS, and configuration controls, then performs manual review for requirements needing judgment. - Compliance Matrix and Remediation Roadmap: Produces a Pass/Fail/N-A/Cannot-Verify matrix with evidence, summary statistics, and a prioritized remediation plan written to .marvin/security/compliance-asvs.md. - Use Case: Before a release, ask for an ASVS L2 audit of your web app and receive a control-by-control gap analysis with file:line evidence and effort estimates for each failure. ## Quick Start Ask the assistant to run an ASVS L2 compliance audit on this project and report the gaps with remediation steps.

Frequently Asked Questions about sec-compliance

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

FAQPage Schema
How do I check my code against OWASP ASVS requirements?▼

Run an ASVS compliance audit that selects a verification level (L1, L2, or L3), then checks each applicable requirement through automated grep-based scans and manual code review. The output is a Pass/Fail/N-A matrix with evidence and remediation for every control.

What is the difference between ASVS L1, L2, and L3?▼

L1 covers roughly 130 requirements as a minimum baseline for any application. L2 adds controls for apps handling sensitive data like PII or financial data, and L3 targets high-value systems such as banking or healthcare with about 286 requirements.

Can a static code audit verify every ASVS requirement?▼

No. Requirements needing runtime behavior, such as session idle timeouts, are marked Cannot Verify with a note on what testing is needed. Only controls with clear code or configuration evidence are marked Pass.

Where is the ASVS compliance report saved?▼

The report is written to .marvin/security/compliance-asvs.md, including a summary, failure details, the full compliance matrix, and a prioritized remediation roadmap. A machine-readable audit-report JSON block is appended for dashboard consumption.

What are the limitations of an ASVS gap analysis?▼

The audit is evidence-based, so controls without verifiable code or configuration are marked Cannot Verify rather than assumed compliant. It also does not replace penetration testing or runtime security testing for business-logic flaws.