Cross-Framework Mapping

NIST SP 1800-32vsAPI 1164

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

68
Controls Mapped
0
Gaps Found
36%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

NIST SP 1800-32 maps to API 1164 with 36% coverage across 16 directly mapped controls. Analysis of 44 NIST SP 1800-32 controls identifies 28 compliance gaps — primarily concentrated in Protect.

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

Control Mappings

Showing 20 of 68 mapped controls across 5 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

NIST SP 1800-32: Asset Identification & Governance(4 mappings)

NIST1800-32-02System security categorization2 targets
API1164-02Risk Management Framework
API1164-02Risk Management Framework
NIST1800-32-05Security policy for operational technology2 targets
API1164-05Network Segmentation and Zones
API1164-05Network Segmentation and Zones

NIST SP 1800-32: Access Management(16 mappings)

NIST1800-32-07Personnel risk assessment7 targets
API1164-06Access Control
API1164-06Access Control
API1164-07Remote Access
API1164-07Remote Access
API1164-09Patch and Vulnerability Management
API1164-09Patch and Vulnerability Management
API1164-24Vulnerability assessment for critical systems
NIST1800-32-08Electronic access perimeter management6 targets
API1164-06Access Control
API1164-06Access Control
API1164-07Remote Access
API1164-07Remote Access
API1164-09Patch and Vulnerability Management
API1164-09Patch and Vulnerability Management
NIST1800-32-09Interactive remote access security3 targets
API1164-06Access Control
API1164-06Access Control
API1164-07Remote Access

+48 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 718 frameworks.

Create Free Account →

Free forever — no credit card required

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 (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 NIST SP 1800-32 and API 1164?

NIST SP 1800-32 has 44 controls across its framework, while API 1164 covers 24 controls. Direct mapping analysis identifies 16 overlapping controls (36% coverage). The frameworks diverge most significantly in Protect, where 6 NIST SP 1800-32 controls have no direct API 1164 equivalent.

How many controls map between NIST SP 1800-32 and API 1164?

Of 44 total NIST SP 1800-32 controls, 16 map directly to API 1164 controls — representing 36% coverage. The remaining 28 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping NIST SP 1800-32 to API 1164?

28 NIST SP 1800-32 controls have no direct equivalent in API 1164. The highest concentration of gaps is in Protect with 6 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 1800-32 and API 1164?

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