Cross-Framework Mapping

3GPP 5G Security Architecture (TS 33.501)vsSLSA

See exactly how 3GPP 5G Security Architecture (TS 33.501) controls map to SLSA. Pre-computed mappings, identified gaps, and coverage analysis.

12
Controls Mapped
16
Gaps Found
29%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

3GPP 5G Security Architecture (TS 33.501) maps to SLSA with 29% coverage across 8 directly mapped controls. Analysis of 28 3GPP 5G Security Architecture (TS 33.501) controls identifies 20 compliance gaps — primarily concentrated in Security for Specific Services.

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

Control Mappings

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

Authentication and Key Management(4 mappings)

6.3SUPI and SUCI Privacy
SLSA-04Roles and responsibilities definition
6.4Secondary Authentication
SLSA-13Authentication and password management
6.5AUSF and SEAF Functions2 targets
SLSA-04Roles and responsibilities definition
SLSA-13Authentication and password management

Service Based Architecture Security(5 mappings)

TS33.501-13.1NF Registration and Discovery Security
SLSA-14Privileged access management
TS33.501-13.2Service Based Interface Security3 targets
SLSA-18Encryption of data in transit
SLSA-19Certificate management
SLSA-20Key lifecycle management
TS33.501-13.4OAuth 2.0 Authorization Framework
SLSA-14Privileged access management

Authentication Procedures(1 mappings)

TS33.501-6.1Authentication Framework
SLSA-13Authentication and password management

Security for NAS and AS Protocols(2 mappings)

TS33.501-6.6AS Security2 targets
SLSA-17Encryption of data at rest
SLSA-18Encryption of data in transit

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 5G Security Architecture (TS 33.501) and SLSA?

3GPP 5G Security Architecture (TS 33.501) has 28 controls across its framework, while SLSA covers 31 controls. Direct mapping analysis identifies 8 overlapping controls (29% coverage). The frameworks diverge most significantly in Security for Specific Services, where 4 3GPP 5G Security Architecture (TS 33.501) controls have no direct SLSA equivalent.

How many controls map between 3GPP 5G Security Architecture (TS 33.501) and SLSA?

Of 28 total 3GPP 5G Security Architecture (TS 33.501) controls, 8 map directly to SLSA controls — representing 29% coverage. The remaining 20 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping 3GPP 5G Security Architecture (TS 33.501) to SLSA?

20 3GPP 5G Security Architecture (TS 33.501) controls have no direct equivalent in SLSA. The highest concentration of gaps is in Security for Specific Services 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 3GPP 5G Security Architecture (TS 33.501) and SLSA?

The domain with the highest gap count is Security for Specific Services (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.