TheArtOfService
Cross-Framework Mapping

3GPP Security Architecture (TS 33.501 — 5G Security)vsLatvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018)

See exactly how 3GPP Security Architecture (TS 33.501 — 5G Security) controls map to Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018). Pre-computed mappings, identified gaps, and coverage analysis.

35
Controls Mapped
0
Gaps Found
23%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

3GPP Security Architecture (TS 33.501 — 5G Security) maps to Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018) with 23% coverage across 5 directly mapped controls. Analysis of 22 3GPP Security Architecture (TS 33.501 — 5G Security) controls identifies 17 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 20 of 35 mapped controls across 3 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

Authentication and Key Management(14 mappings)

6.3SUPI and SUCI Privacy7 targets
→Art. 2Consent Definition
→Art. 4Participating Institutions
→Sec. 10Powers of the Commission
→Sec. 2Interpretation
→Sec. 25Interpretation
→Sec. 26Notifiable Data Breaches
→Sec. 3Scope and Application
6.5AUSF and SEAF Functions7 targets
→Art. 2Consent Definition
→Art. 4Participating Institutions
→Sec. 10Powers of the Commission
→Sec. 2Interpretation
→Sec. 25Interpretation
→Sec. 26Notifiable Data Breaches
→Sec. 3Scope and Application

Radio and Access Network Security(6 mappings)

6.7Security Key Establishment for Radio Bearers6 targets
→Art. 2Consent Definition
→Art. 4Participating Institutions
→Sec. 10Powers of the Commission
→Sec. 2Interpretation
→Sec. 25Interpretation
→Sec. 26Notifiable Data Breaches

+15 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 693 frameworks.

Create Free Account →

Free forever — no credit card required

Related Comparisons

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

3GPP Security Architecture (TS 33.501 — 5G Security) vs NIST SP 800-171A Rev 3 — Assessing CUI Security Requirements15 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs NIS2 Directive Implementing Acts15 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs UK Telecommunications (Security) Act 202115 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs TISAX — Trusted Information Security Assessment Exchange13 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs FAA Cybersecurity Framework for Aviation13 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs South Korea ISMS-P13 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs NIST SP 800-82 Rev 3 — Guide to OT Security13 mappings3GPP Security Architecture (TS 33.501 — 5G Security) vs PAS 1192-5:2015 — Security-Minded Approach to BIM and Digital Built Environments13 mappings

Other Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018) comparisons

Botswana Data Protection Act (2024) vs Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018)17 mappingsEgypt Personal Data Protection Law (Law No. 151 of 2020) vs Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018)17 mappingsEthiopia Personal Data Protection Proclamation (No. 1321/2024) vs Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018)17 mappingsNorth Macedonia Law on Personal Data Protection (2020) vs Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018)17 mappingsMalta Data Protection Act (Cap. 586, 2018) vs Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018)17 mappingsConnecticut Data Privacy Act (CTDPA) vs Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018)17 mappingsAustralia Consumer Data Right — Banking (CDR) vs Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018)17 mappingsEU Network Code on Cybersecurity for the Electricity Sector vs Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018)17 mappings

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 →

Popular framework comparisons

NIST CSF vs NIST 800-53ISO 27001 vs NIST CSFCMMC vs NIST 800-53FedRAMP vs NIST 800-53NIST CSF vs SOC 2HIPAA vs NIST 800-53ISO 27001 vs SOC 2ISO 27001 vs ISO 27701

What are the key differences between 3GPP Security Architecture (TS 33.501 — 5G Security) and Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018)?

3GPP Security Architecture (TS 33.501 — 5G Security) has 22 controls across its framework, while Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018) covers 38 controls. Direct mapping analysis identifies 5 overlapping controls (23% 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 Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018) equivalent.

How many controls map between 3GPP Security Architecture (TS 33.501 — 5G Security) and Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018)?

Of 22 total 3GPP Security Architecture (TS 33.501 — 5G Security) controls, 5 map directly to Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018) controls — representing 23% 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 3GPP Security Architecture (TS 33.501 — 5G Security) to Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018)?

17 3GPP Security Architecture (TS 33.501 — 5G Security) controls have no direct equivalent in Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 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 Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 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.

Related Resources

How to Map Controls Across Frameworks|Multi-Framework Compliance Guide|Compliance Glossary

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.