Armenia Law on Protection of Personal Data (2015)vsO-RAN WG11 Security Specification
See exactly how Armenia Law on Protection of Personal Data (2015) controls map to O-RAN WG11 Security Specification. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
Armenia Law on Protection of Personal Data (2015) maps to O-RAN WG11 Security Specification with 6% coverage across 1 directly mapped controls. Analysis of 18 Armenia Law on Protection of Personal Data (2015) controls identifies 17 compliance gaps — primarily concentrated in Marketing.
Source: TheArtOfService Knowledge Graph | 18 controls analysed | 723 frameworks | 332K+ cross-framework mappings
Control Mappings
Showing 1 of 1 mapped controls across 1 domains. Sign up to explore all 332K+ mappings across 723 frameworks.
Lifecycle(1 mappings)
Related Comparisons
Other Armenia Law on Protection of Personal Data (2015) 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 Armenia Law on Protection of Personal Data (2015) and O-RAN WG11 Security Specification?
Armenia Law on Protection of Personal Data (2015) has 18 controls across its framework, while O-RAN WG11 Security Specification covers 8 controls. Direct mapping analysis identifies 1 overlapping controls (6% coverage). The frameworks diverge most significantly in Marketing, where 1 Armenia Law on Protection of Personal Data (2015) controls have no direct O-RAN WG11 Security Specification equivalent.
How many controls map between Armenia Law on Protection of Personal Data (2015) and O-RAN WG11 Security Specification?
Of 18 total Armenia Law on Protection of Personal Data (2015) controls, 1 map directly to O-RAN WG11 Security Specification controls — representing 6% 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 Armenia Law on Protection of Personal Data (2015) to O-RAN WG11 Security Specification?
17 Armenia Law on Protection of Personal Data (2015) controls have no direct equivalent in O-RAN WG11 Security Specification. The highest concentration of gaps is in Marketing 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 Armenia Law on Protection of Personal Data (2015) and O-RAN WG11 Security Specification?
The domain with the highest gap count is Marketing (1 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.