Cross-Framework Mapping

API 1164vsNIST SP 800-124 Rev 2 — Mobile Device Security

See exactly how API 1164 controls map to NIST SP 800-124 Rev 2 — Mobile Device Security. Pre-computed mappings, identified gaps, and coverage analysis.

9
Controls Mapped
15
Gaps Found
33%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

API 1164 maps to NIST SP 800-124 Rev 2 — Mobile Device Security with 33% coverage across 8 directly mapped controls. Analysis of 24 API 1164 controls identifies 16 compliance gaps — primarily concentrated in API 1164: Access Management.

Source: TheArtOfService Knowledge Graph | 24 controls analysed | 693 frameworks | 819K+ cross-framework mappings

Control Mappings

Showing 9 of 9 mapped controls across 3 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

API 1164: Systems Security(3 mappings)

API1164-12Malware prevention for operational systems
MD124-TECH-03Mobile Application Vetting
API1164-13Network security monitoring2 targets
MD124-CTL-06Network Security for Mobile
MD124-TECH-05VPN and Secure Communication

API 1164: Incident Response & Recovery(3 mappings)

API1164-17Recovery plan for critical systems
MD124-POL-04Mobile Device Lifecycle Management
API1164-18Reporting obligations to authorities
MD124-POL-04Mobile Device Lifecycle Management
API1164-19Coordination with sector-specific agencies
MD124-POL-04Mobile Device Lifecycle Management

API 1164: Supply Chain & Configuration(3 mappings)

API1164-21Supply chain risk management for critical components
MD124-POL-04Mobile Device Lifecycle Management
API1164-22Configuration management for OT systems
MD124-POL-04Mobile Device Lifecycle Management
API1164-23Change management procedures
MD124-POL-04Mobile Device Lifecycle Management

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 693 framework browser
  • Cross-framework mappings (819K+)
  • 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 API 1164 and NIST SP 800-124 Rev 2 — Mobile Device Security?

API 1164 has 24 controls across its framework, while NIST SP 800-124 Rev 2 — Mobile Device Security covers 15 controls. Direct mapping analysis identifies 8 overlapping controls (33% coverage). The frameworks diverge most significantly in API 1164: Access Management, where 5 API 1164 controls have no direct NIST SP 800-124 Rev 2 — Mobile Device Security equivalent.

How many controls map between API 1164 and NIST SP 800-124 Rev 2 — Mobile Device Security?

Of 24 total API 1164 controls, 8 map directly to NIST SP 800-124 Rev 2 — Mobile Device Security controls — representing 33% coverage. The remaining 16 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping API 1164 to NIST SP 800-124 Rev 2 — Mobile Device Security?

16 API 1164 controls have no direct equivalent in NIST SP 800-124 Rev 2 — Mobile Device Security. The highest concentration of gaps is in API 1164: Access Management with 5 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 API 1164 and NIST SP 800-124 Rev 2 — Mobile Device Security?

The domain with the highest gap count is API 1164: Access Management (5 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.