Cross-Framework Mapping

OWASP SAMMvsNIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices

See exactly how OWASP SAMM controls map to NIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices. Pre-computed mappings, identified gaps, and coverage analysis.

13
Controls Mapped
0
Gaps Found
60%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

OWASP SAMM maps to NIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices with 60% coverage across 3 directly mapped controls. Analysis of 5 OWASP SAMM controls identifies 2 compliance gaps — primarily concentrated in Verification.

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

Control Mappings

Showing 13 of 13 mapped controls across 3 domains. Sign up to explore all 330K+ mappings across 718 frameworks.

Governance(3 mappings)

OWASPSAMM-1Governance: Strategy, Policy, Compliance, Education, Champions3 targets
MD124-CTL-04OS and Application Updates
MD124-POL-02BYOD Policy
MD124-POL-03Mobile Data Protection Policy

Design(6 mappings)

OWASPSAMM-2Design: Threat Assessment, Security Requirements, Security Architecture6 targets
MD124-CTL-01Device Authentication and Lock
MD124-CTL-02Device Encryption
MD124-POL-01Mobile Device Security Policy
MD124-POL-03Mobile Data Protection Policy
MD124-POL-04Mobile Device Lifecycle Management
MD124-TECH-05VPN and Secure Communication

Operations(4 mappings)

OWASPSAMM-5Operations: Incident Management, Environment Management, Operational Management4 targets
MD124-CTL-06Network Security for Mobile
MD124-POL-01Mobile Device Security Policy
MD124-TECH-03Mobile Application Vetting
MD124-TECH-05VPN and Secure Communication

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 718 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 OWASP SAMM and NIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices?

OWASP SAMM has 5 controls across its framework, while NIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices covers 34 controls. Direct mapping analysis identifies 3 overlapping controls (60% coverage). The frameworks diverge most significantly in Verification, where 1 OWASP SAMM controls have no direct NIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices equivalent.

How many controls map between OWASP SAMM and NIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices?

Of 5 total OWASP SAMM controls, 3 map directly to NIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices controls — representing 60% coverage. The remaining 2 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping OWASP SAMM to NIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices?

2 OWASP SAMM controls have no direct equivalent in NIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices. The highest concentration of gaps is in Verification 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 SAMM and NIST SP 800-124 Revision 2 - Guidelines for Managing the Security of Mobile Devices?

The domain with the highest gap count is Verification (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.