Cross-Framework Mapping

AWS Well-Architected Security PillarvsO-RAN Alliance Security Specifications (O-RAN.WG11)

See exactly how AWS Well-Architected Security Pillar controls map to O-RAN Alliance Security Specifications (O-RAN.WG11). Pre-computed mappings, identified gaps, and coverage analysis.

11
Controls Mapped
14
Gaps Found
32%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

AWS Well-Architected Security Pillar maps to O-RAN Alliance Security Specifications (O-RAN.WG11) with 32% coverage across 8 directly mapped controls. Analysis of 25 AWS Well-Architected Security Pillar controls identifies 17 compliance gaps — primarily concentrated in AWS Well-Architected Security Pillar: Data Protection in Cloud.

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

Control Mappings

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

AWS Well-Architected Security Pillar: Cloud Governance(3 mappings)

AWS-WA-01Shared responsibility model definition3 targets
ORAN-SEC-2.1Interface Security Requirements
ORAN-SEC-3.1TLS Implementation
ORAN-SEC-4.1Security Test Specifications

AWS Well-Architected Security Pillar: Identity & Access in Cloud(4 mappings)

AWS-WA-06Cloud identity management
ORAN-SEC-3.3Certificate Management
AWS-WA-07Multi-factor authentication for cloud
ORAN-SEC-2.1Interface Security Requirements
AWS-WA-08Privileged access in cloud environments2 targets
ORAN-SEC-2.1Interface Security Requirements
ORAN-SEC-2.3Least Privilege and Zero Trust

AWS Well-Architected Security Pillar: Data Protection in Cloud(1 mappings)

AWS-WA-12Encryption of cloud-stored data
ORAN-SEC-3.1TLS Implementation

AWS Well-Architected Security Pillar: Cloud Infrastructure Security(1 mappings)

AWS-WA-16Virtual network segmentation
ORAN-SEC-2.3Least Privilege and Zero Trust

AWS Well-Architected Security Pillar: Cloud Operations & Monitoring(2 mappings)

AWS-WA-21Cloud security monitoring and logging
ORAN-SEC-4.2Security Log Management
AWS-WA-23Cloud vulnerability management
ORAN-SEC-1.1Threat Modeling and Remediation

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 AWS Well-Architected Security Pillar and O-RAN Alliance Security Specifications (O-RAN.WG11)?

AWS Well-Architected Security Pillar has 25 controls across its framework, while O-RAN Alliance Security Specifications (O-RAN.WG11) covers 13 controls. Direct mapping analysis identifies 8 overlapping controls (32% coverage). The frameworks diverge most significantly in AWS Well-Architected Security Pillar: Data Protection in Cloud, where 4 AWS Well-Architected Security Pillar controls have no direct O-RAN Alliance Security Specifications (O-RAN.WG11) equivalent.

How many controls map between AWS Well-Architected Security Pillar and O-RAN Alliance Security Specifications (O-RAN.WG11)?

Of 25 total AWS Well-Architected Security Pillar controls, 8 map directly to O-RAN Alliance Security Specifications (O-RAN.WG11) controls — representing 32% coverage. The remaining 17 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping AWS Well-Architected Security Pillar to O-RAN Alliance Security Specifications (O-RAN.WG11)?

17 AWS Well-Architected Security Pillar controls have no direct equivalent in O-RAN Alliance Security Specifications (O-RAN.WG11). The highest concentration of gaps is in AWS Well-Architected Security Pillar: Data Protection in Cloud 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 AWS Well-Architected Security Pillar and O-RAN Alliance Security Specifications (O-RAN.WG11)?

The domain with the highest gap count is AWS Well-Architected Security Pillar: Data Protection in Cloud (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.