API 1164vsO-RAN WG11 Security Specification
See exactly how API 1164 controls map to O-RAN WG11 Security Specification. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
API 1164 maps to O-RAN WG11 Security Specification with 21% coverage across 10 directly mapped controls. Analysis of 24 API 1164 controls identifies 35 compliance gaps — primarily concentrated in API 1164: Incident Response & Recovery.
Source: TheArtOfService Knowledge Graph | 24 controls analysed | 723 frameworks | 332K+ cross-framework mappings
Control Mappings
Showing 10 of 10 mapped controls across 7 domains. Sign up to explore all 332K+ mappings across 723 frameworks.
Access(2 mappings)
API 1164: Access Management(3 mappings)
Vulnerability(1 mappings)
Resilience(1 mappings)
API 1164: Systems Security(1 mappings)
Regulatory(1 mappings)
API 1164: Supply Chain & Configuration(1 mappings)
Related Comparisons
Other API 1164 comparisons
Other O-RAN WG11 Security Specification comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 723 frameworks — at a fraction of consulting costs.
Free
- ✓ 723 framework browser
- ✓ Cross-framework mappings (332K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between API 1164 and O-RAN WG11 Security Specification?
API 1164 has 24 controls across its framework, while O-RAN WG11 Security Specification covers 8 controls. Direct mapping analysis identifies 10 overlapping controls (21% coverage). The frameworks diverge most significantly in API 1164: Incident Response & Recovery, where 5 API 1164 controls have no direct O-RAN WG11 Security Specification equivalent.
How many controls map between API 1164 and O-RAN WG11 Security Specification?
Of 24 total API 1164 controls, 10 map directly to O-RAN WG11 Security Specification controls — representing 21% coverage. The remaining 35 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 O-RAN WG11 Security Specification?
35 API 1164 controls have no direct equivalent in O-RAN WG11 Security Specification. The highest concentration of gaps is in API 1164: Incident Response & Recovery 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 O-RAN WG11 Security Specification?
The domain with the highest gap count is API 1164: Incident Response & Recovery (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
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.