Framework overlap

Does ISO 27799 cover O-RAN WG11 Security Specification?

You hold ISO 27799 and have been told to do O-RAN WG11 Security Specification. Here is how much overlaps, control by control.

75% of O-RAN WG11 Security Specification you already have

ISO 27799 already covers about 75% of O-RAN WG11 Security Specification, leaving 2 of 8 controls as genuinely new work.

Already covered 3 Likely covered 3 New work 2

What is genuinely new work

Nothing in ISO 27799 reaches these. This is the list to scope.

ORANWG11-4
RIC, xApp/rApp Lifecycle, AI/ML Security
ORANWG11-5
O-Cloud, Container Security, Secure Configuration, Patching
Show the 6 you already have
ORANWG11-2
O-RAN Interface Security: E2, A1, O1, O2, Open Fronthaul
ORANWG11-3
Cryptography, TLS, SSH, IPsec, and PKI Lifecycle Management
ORANWG11-7
Logging, Monitoring, Incident Response, and Denial-of-Service Resilience
ORANWG11-1
O-RAN Threat Model, Risk Management, and Security Architecture
ORANWG11-6
Security Test Specifications, Certification, and Conformance
ORANWG11-8
Supply Chain, Secure Development Lifecycle, Privacy, Multi-Vendor Trust

How this is calculated

Already covered means a mapping runs from a control in ISO 27799 to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition