Cross-Framework Mapping

O-RAN WG11 Security SpecificationvsISO/IEC 27400:2022

See exactly how O-RAN WG11 Security Specification controls map to ISO/IEC 27400:2022. Pre-computed mappings, identified gaps, and coverage analysis.

17
Controls Mapped
0
Gaps Found
62%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

O-RAN WG11 Security Specification maps to ISO/IEC 27400:2022 with 62% coverage across 5 directly mapped controls. Analysis of 8 O-RAN WG11 Security Specification controls identifies 3 compliance gaps — primarily concentrated in Logging, Monitoring, IR, DoS.

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

Control Mappings

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

Threat Model and Risk Management(2 mappings)

ORANWG11-1O-RAN Threat Model, Risk Management, and Security Architecture2 targets
27400-5.1IoT Security and Privacy Governance
27400-5.1IoT Security and Privacy Governance

O-RAN Interface Security(5 mappings)

ORANWG11-2O-RAN Interface Security: E2, A1, O1, O2, Open Fronthaul5 targets
27011-1Scope
27011-3Terms and definitions
27400-3Terms and definitions
27400-6.1Secure Device Design
27400-6.1Secure Device Design

Cryptography, Protocols, PKI(5 mappings)

ORANWG11-3Cryptography, TLS, SSH, IPsec, and PKI Lifecycle Management5 targets
27011-1Scope
27011-3Terms and definitions
27400-3Terms and definitions
27400-6.2Device Identity and Authentication
27400-6.2Device Identity and Authentication

Security Test and Certification(3 mappings)

ORANWG11-6Security Test Specifications, Certification, and Conformance3 targets
27011-1Scope
27011-3Terms and definitions
27400-3Terms and definitions

Supply Chain, SDLC, Privacy, Trust(2 mappings)

ORANWG11-8Supply Chain, Secure Development Lifecycle, Privacy, Multi-Vendor Trust2 targets
27400-6.3Secure Update Mechanism
27400-6.3Secure Update Mechanism

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 O-RAN WG11 Security Specification and ISO/IEC 27400:2022?

O-RAN WG11 Security Specification has 8 controls across its framework, while ISO/IEC 27400:2022 covers 32 controls. Direct mapping analysis identifies 5 overlapping controls (62% coverage). The frameworks diverge most significantly in Logging, Monitoring, IR, DoS, where 1 O-RAN WG11 Security Specification controls have no direct ISO/IEC 27400:2022 equivalent.

How many controls map between O-RAN WG11 Security Specification and ISO/IEC 27400:2022?

Of 8 total O-RAN WG11 Security Specification controls, 5 map directly to ISO/IEC 27400:2022 controls — representing 62% coverage. The remaining 3 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping O-RAN WG11 Security Specification to ISO/IEC 27400:2022?

3 O-RAN WG11 Security Specification controls have no direct equivalent in ISO/IEC 27400:2022. The highest concentration of gaps is in Logging, Monitoring, IR, DoS 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 O-RAN WG11 Security Specification and ISO/IEC 27400:2022?

The domain with the highest gap count is Logging, Monitoring, IR, DoS (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.