Cross-Framework Mapping

API 1164vsNIST SP 800-218

See exactly how API 1164 controls map to NIST SP 800-218. Pre-computed mappings, identified gaps, and coverage analysis.

15
Controls Mapped
9
Gaps Found
38%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

API 1164 maps to NIST SP 800-218 with 38% coverage across 9 directly mapped controls. Analysis of 24 API 1164 controls identifies 15 compliance gaps — primarily concentrated in API 1164: Asset Identification & Governance.

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

Control Mappings

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

API 1164: Asset Identification & Governance(1 mappings)

API1164-02System security categorization
NIST218-08Information classification and labeling

API 1164: Access Management(9 mappings)

API1164-06Physical and logical access controls3 targets
NIST218-11Access control policy and enforcement
NIST218-13Authentication and password management
NIST218-15Access review and recertification
API1164-07Personnel risk assessment3 targets
NIST218-11Access control policy and enforcement
NIST218-13Authentication and password management
NIST218-15Access review and recertification
API1164-09Interactive remote access security3 targets
NIST218-11Access control policy and enforcement
NIST218-13Authentication and password management
NIST218-15Access review and recertification

API 1164: Systems Security(2 mappings)

API1164-12Malware prevention for operational systems
NIST218-22Protection from malware
API1164-13Network security monitoring
NIST218-27Network security management

API 1164: Incident Response & Recovery(3 mappings)

API1164-17Recovery plan for critical systems
NIST218-23Backup and recovery procedures
API1164-18Reporting obligations to authorities
NIST218-23Backup and recovery procedures
API1164-19Coordination with sector-specific agencies
NIST218-23Backup and recovery procedures

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-218?

API 1164 has 24 controls across its framework, while NIST SP 800-218 covers 31 controls. Direct mapping analysis identifies 9 overlapping controls (38% coverage). The frameworks diverge most significantly in API 1164: Asset Identification & Governance, where 4 API 1164 controls have no direct NIST SP 800-218 equivalent.

How many controls map between API 1164 and NIST SP 800-218?

Of 24 total API 1164 controls, 9 map directly to NIST SP 800-218 controls — representing 38% coverage. The remaining 15 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-218?

15 API 1164 controls have no direct equivalent in NIST SP 800-218. The highest concentration of gaps is in API 1164: Asset Identification & Governance with 4 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-218?

The domain with the highest gap count is API 1164: Asset Identification & Governance (4 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.