Cross-Framework Mapping

NIST SP 800-92vsOWASP ASVS

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

12
Controls Mapped
47
Gaps Found
29%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

NIST SP 800-92 maps to OWASP ASVS with 29% coverage across 7 directly mapped controls. Analysis of 59 NIST SP 800-92 controls identifies 1 compliance gaps — primarily concentrated in Integration with NIST Family and Maturity.

Source: TheArtOfService Knowledge Graph | 59 controls analysed | 700 frameworks | 330K+ cross-framework mappings

Control Mappings

Showing 12 of 12 mapped controls across 7 domains. Sign up to explore all 330K+ mappings across 700 frameworks.

Log Management Programme(1 mappings)

NISTSP92-1Log Management Programme, Policy, Roles, and Operational Runbooks
OWASPASVS-1Architecture, Design and Threat Modelling (V1)

Log Generation(1 mappings)

NISTSP92-2Log Generation: OS, Application, Security Tools, Network, Cloud, Required Event Content
OWASPASVS-8Data Protection (V8 + V8.3)

Log Infrastructure(2 mappings)

NISTSP92-3Log Infrastructure: Architecture, Centralisation, Transport Security, SIEM Governance2 targets
OWASPASVS-6Stored Cryptography (V6)
OWASPASVS-9Communication Security (V9)

Log Management Operations(4 mappings)

NISTSP92-4Log Management: Time Synchronisation, Parsing, Storage, Integrity, Access Control4 targets
OWASPASVS-2Authentication and Credential Storage (V2 + V2.4)
OWASPASVS-4Access Control (V4 + V4.3)
OWASPASVS-6Stored Cryptography (V6)
OWASPASVS-9Communication Security (V9)

Log Analysis and Detection(2 mappings)

NISTSP92-5Log Analysis: Correlation, Baselining, Anomaly Detection, Alerting, Manual Review2 targets
OWASPASVS-10Malicious Code Verification (V10)
OWASPASVS-7Error Handling and Logging (V7)

Log Retention and Disposition(1 mappings)

NISTSP92-6Log Retention: Policy, Tiered Storage, Backup, Secure Disposal, Legal Hold
OWASPASVS-8Data Protection (V8 + V8.3)

Privacy + Cloud/SaaS Logs(1 mappings)

NISTSP92-7Privacy in Logs, Sensitive Content Handling, Cloud and SaaS Log Considerations
OWASPASVS-8Data Protection (V8 + V8.3)

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 700 framework browser
  • Cross-framework mappings (330K+)
  • 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 NIST SP 800-92 and OWASP ASVS?

NIST SP 800-92 has 59 controls across its framework, while OWASP ASVS covers 49 controls. Direct mapping analysis identifies 7 overlapping controls (29% coverage). The frameworks diverge most significantly in Integration with NIST Family and Maturity, where 1 NIST SP 800-92 controls have no direct OWASP ASVS equivalent.

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

Of 59 total NIST SP 800-92 controls, 7 map directly to OWASP ASVS controls — representing 29% coverage. The remaining 1 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

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

1 NIST SP 800-92 controls have no direct equivalent in OWASP ASVS. The highest concentration of gaps is in Integration with NIST Family and Maturity 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 NIST SP 800-92 and OWASP ASVS?

The domain with the highest gap count is Integration with NIST Family and Maturity (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.