Cross-Framework Mapping

3GPP Security Architecture (TS 33.501 — 5G Security)vsLebanon Electronic Transactions and Personal Data Protection Law (Law No. 81/2018)

See exactly how 3GPP Security Architecture (TS 33.501 — 5G Security) controls map to Lebanon Electronic Transactions and Personal Data Protection Law (Law No. 81/2018). Pre-computed mappings, identified gaps, and coverage analysis.

14
Controls Mapped
8
Gaps Found
27%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

3GPP Security Architecture (TS 33.501 — 5G Security) maps to Lebanon Electronic Transactions and Personal Data Protection Law (Law No. 81/2018) with 27% coverage across 6 directly mapped controls. Analysis of 22 3GPP Security Architecture (TS 33.501 — 5G Security) controls identifies 16 compliance gaps — primarily concentrated in Subscriber Privacy and Service Security.

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

Control Mappings

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

Authentication and Key Management(8 mappings)

6.3SUPI and SUCI Privacy2 targets
Art. 2Consent Definition
Art. 4Participating Institutions
6.4Secondary Authentication2 targets
CTDPA-9Consent for Sensitive Data
TIPA-8Sensitive Data Consent
6.5AUSF and SEAF Functions4 targets
Art. 2Consent Definition
Art. 4Participating Institutions
CTDPA-9Consent for Sensitive Data
TIPA-8Sensitive Data Consent

Radio and Access Network Security(4 mappings)

6.7Security Key Establishment for Radio Bearers2 targets
Art. 2Consent Definition
Art. 4Participating Institutions
6.9Handover Security2 targets
Art. 2Consent Definition
Art. 4Participating Institutions

Non-3GPP and Inter-Network Security(2 mappings)

9.2Network Domain Security2 targets
Art. 2Consent Definition
Art. 4Participating Institutions

Related Comparisons

Other 3GPP Security Architecture (TS 33.501 — 5G Security) comparisons

Other Lebanon Electronic Transactions and Personal Data Protection Law (Law No. 81/2018) comparisons

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 3GPP Security Architecture (TS 33.501 — 5G Security) and Lebanon Electronic Transactions and Personal Data Protection Law (Law No. 81/2018)?

3GPP Security Architecture (TS 33.501 — 5G Security) has 22 controls across its framework, while Lebanon Electronic Transactions and Personal Data Protection Law (Law No. 81/2018) covers 33 controls. Direct mapping analysis identifies 6 overlapping controls (27% coverage). The frameworks diverge most significantly in Subscriber Privacy and Service Security, where 5 3GPP Security Architecture (TS 33.501 — 5G Security) controls have no direct Lebanon Electronic Transactions and Personal Data Protection Law (Law No. 81/2018) equivalent.

How many controls map between 3GPP Security Architecture (TS 33.501 — 5G Security) and Lebanon Electronic Transactions and Personal Data Protection Law (Law No. 81/2018)?

Of 22 total 3GPP Security Architecture (TS 33.501 — 5G Security) controls, 6 map directly to Lebanon Electronic Transactions and Personal Data Protection Law (Law No. 81/2018) controls — representing 27% coverage. The remaining 16 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping 3GPP Security Architecture (TS 33.501 — 5G Security) to Lebanon Electronic Transactions and Personal Data Protection Law (Law No. 81/2018)?

16 3GPP Security Architecture (TS 33.501 — 5G Security) controls have no direct equivalent in Lebanon Electronic Transactions and Personal Data Protection Law (Law No. 81/2018). The highest concentration of gaps is in Subscriber Privacy and Service Security 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 3GPP Security Architecture (TS 33.501 — 5G Security) and Lebanon Electronic Transactions and Personal Data Protection Law (Law No. 81/2018)?

The domain with the highest gap count is Subscriber Privacy and Service Security (5 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.