Cross-Framework Mapping

OWASP ASVSvsNIST SP 800-137

See exactly how OWASP ASVS controls map to NIST SP 800-137. Pre-computed mappings, identified gaps, and coverage analysis.

11
Controls Mapped
3
Gaps Found
57%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

OWASP ASVS maps to NIST SP 800-137 with 57% coverage across 8 directly mapped controls. Analysis of 14 OWASP ASVS controls identifies 6 compliance gaps — primarily concentrated in V14 Configuration.

Source: TheArtOfService Knowledge Graph | 14 controls analysed | 723 frameworks | 332K+ cross-framework mappings

Control Mappings

Showing 11 of 11 mapped controls across 8 domains. Sign up to explore all 332K+ mappings across 723 frameworks.

V1 Architecture and Threat Modelling(1 mappings)

OWASPASVS-1Architecture, Design and Threat Modelling (V1)
NISTSP137-1ISCM Strategy, Governance, and Volatility Assessment

V10 Malicious Code(2 mappings)

OWASPASVS-10Malicious Code Verification (V10)2 targets
NISTSP137-5Vulnerability + Patch + Configuration Status Monitoring
NISTSP137-6Malware, Identity Access, and Network Boundary Monitoring

V2 Authentication(1 mappings)

OWASPASVS-2Authentication and Credential Storage (V2 + V2.4)
NISTSP137-6Malware, Identity Access, and Network Boundary Monitoring

V4 Access Control(1 mappings)

OWASPASVS-4Access Control (V4 + V4.3)
NISTSP137-6Malware, Identity Access, and Network Boundary Monitoring

V6 Cryptography at Rest(1 mappings)

OWASPASVS-6Stored Cryptography (V6)
NISTSP137-5Vulnerability + Patch + Configuration Status Monitoring

V7 Error Handling and Logging(1 mappings)

OWASPASVS-7Error Handling and Logging (V7)
NISTSP137-4Security Status Reporting and Risk Score Aggregation

V8 Data Protection(2 mappings)

OWASPASVS-8Data Protection (V8 + V8.3)2 targets
NISTSP137-1ISCM Strategy, Governance, and Volatility Assessment
NISTSP137-7Incident Response Integration and Ongoing Authorization

V9 Communication(2 mappings)

OWASPASVS-9Communication Security (V9)2 targets
NISTSP137-5Vulnerability + Patch + Configuration Status Monitoring
NISTSP137-6Malware, Identity Access, and Network Boundary Monitoring

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 723 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 723 framework browser
  • Cross-framework mappings (332K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between OWASP ASVS and NIST SP 800-137?

OWASP ASVS has 14 controls across its framework, while NIST SP 800-137 covers 8 controls. Direct mapping analysis identifies 8 overlapping controls (57% coverage). The frameworks diverge most significantly in V14 Configuration, where 1 OWASP ASVS controls have no direct NIST SP 800-137 equivalent.

How many controls map between OWASP ASVS and NIST SP 800-137?

Of 14 total OWASP ASVS controls, 8 map directly to NIST SP 800-137 controls — representing 57% coverage. The remaining 6 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping OWASP ASVS to NIST SP 800-137?

6 OWASP ASVS controls have no direct equivalent in NIST SP 800-137. The highest concentration of gaps is in V14 Configuration with 1 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between OWASP ASVS and NIST SP 800-137?

The domain with the highest gap count is V14 Configuration (1 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.