3GPP 5G Security Architecture (TS 33.501)
3GPP Technical Specification 33.501 defines the security architecture and procedures for 5G systems, including authentication (5G-AKA and EAP-AKA'), key management, security between network functions, user plane integrity protection, and subscriber privacy through SUPI/SUCI encryption to prevent tracking and IMSI catching.
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (24)
Access Security
| Code | Title |
|---|---|
| 33.501-9 | Security for Non-3GPP Access |
Authentication
| Code | Title |
|---|---|
| 33.501-6.1 | Primary Authentication (5G AKA / EAP-AKA') |
Authentication Procedures
| Code | Title |
|---|---|
| TS33.501-6.1 | Authentication Framework |
| TS33.501-6.2 | Key Hierarchy and Derivation |
| TS33.501-6.3 | EAP-AKA' Authentication |
| TS33.501-6.4 | NAS Security |
Authentication and Key Management
5G authentication and cryptographic key hierarchy
| Code | Title |
|---|---|
| 6.1 | Malware Protection |
| 6.2 | Approach selection |
| 6.3 | Information security awareness, education and training |
| 6.4 | Logging and Monitoring |
| 6.5 | Preparing and Distributing Audit Report |
Core Network Security
| Code | Title |
|---|---|
| 33.501-8 | Security Aspects of UDM/UDR |
Cryptography
| Code | Title |
|---|---|
| 33.501-Annex-D | Cryptographic Algorithms |
General Security Architecture
| Code | Title |
|---|---|
| TS33.501-4.1 | 5G Security Architecture Overview |
| TS33.501-4.2 | Security Feature Groups |
| TS33.501-4.3 | Security Domains and Stratum |
| TS33.501-4.4 | Network Functions in the Security Architecture |
Identifiers and Privacy
| Code | Title |
|---|---|
| 33.501-5.1 | Subscription Permanent Identifier Protection |
Interworking
| Code | Title |
|---|---|
| 33.501-10 | Security for Interworking with EPS |
Key Management
| Code | Title |
|---|---|
| 33.501-6.2 | Key Hierarchy |
Management Security
| Code | Title |
|---|---|
| 33.501-OAM | Management Plane Security |
Network and Service Security
User plane, control plane, and SBA security
Non-3GPP Access Security
| Code | Title |
|---|---|
| TS33.501-7.1 | Untrusted Non-3GPP Access Security |
| TS33.501-7.2 | Security Visibility and Configurability |
| TS33.501-7.3 | Wireline Access Security |
Privacy
| Code | Title |
|---|---|
| 33.501-17 | Privacy and Pseudonymization |
Roaming Security
| Code | Title |
|---|---|
| 33.501-13.4 | SEPP and Inter-PLMN Security (N32) |
| 33.501-15 | Steering of Roaming Security |
SBA Security
| Code | Title |
|---|---|
| 33.501-13.1 | Service-Based Architecture Security (TLS) |
| 33.501-13.2 | Network Function Service Authorization (OAuth 2.0) |
Security Architecture
| Code | Title |
|---|---|
| 33.501-4.2 | Security Domains and Trust Model |
Security for NAS and AS Protocols
| Code | Title |
|---|---|
| TS33.501-6.5 | AS Security and PDCP Protection |
| TS33.501-6.6 | AS Security |
| TS33.501-6.7 | Security Key Hierarchy |
| TS33.501-6.8 | Security in Handover |
Security for Specific Services
| Code | Title |
|---|---|
| TS33.501-14.1 | Security for Network Slicing |
| TS33.501-14.2 | Security for Edge Computing |
| TS33.501-14.3 | Security for URLLC Services |
| TS33.501-14.4 | Security for IAB |
Service Based Architecture Security
| Code | Title |
|---|---|
| TS33.501-13.1 | NF Registration and Discovery Security |
| TS33.501-13.2 | NF Service Authorization |
| TS33.501-13.3 | N32 Interconnect Security |
| TS33.501-13.4 | OAuth 2.0 Authorization Framework |
Service Security
| Code | Title |
|---|---|
| 33.501-11 | Security Aspects of IMS |
Signaling Security
| Code | Title |
|---|---|
| 33.501-6.4 | NAS Security |
| 33.501-6.5 | AS Security (RRC and User Plane) |
| 33.501-6.7 | Security Mode Command Procedures |
Slicing
| Code | Title |
|---|---|
| 33.501-14 | Network Slicing Security |
User Plane
| Code | Title |
|---|---|
| 33.501-16 | Security for User Plane Integrity Protection |
Your Compliance Coverage
If you comply with 3GPP 5G Security Architecture (TS 33.501), you already cover:
OWASP SAMM
17%
8 controls mapped
Compare →ISO 15189:2022 - Medical Laboratories Requirements for Quality and Competence
17%
8 controls mapped
Compare →Azure Security Benchmark
17%
8 controls mapped
Compare →+ 555 more: AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) (17%), NIST SP 800-161 (17%)
See all 558 mapped frameworks ↓Maps to 558 other frameworks
Frequently Asked Questions
What is 3GPP 5G Security Architecture (TS 33.501)?
3GPP 5G Security Architecture (TS 33.501) is a compliance framework from International (3GPP) with 24 domains and 48 controls. 3GPP Technical Specification 33.501 defines the security architecture and procedures for 5G systems, including authentication (5G-AKA and EAP-AKA'), key management, security between network functions, user plane integrity protection, and subscriber privacy through SUPI/SUCI encryption to prevent tracking and IMSI catching. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does 3GPP 5G Security Architecture (TS 33.501) have?
3GPP 5G Security Architecture (TS 33.501) has 48 controls organised across 24 domains. The largest domains are Authentication and Key Management (5 controls), Authentication Procedures (4 controls), General Security Architecture (4 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does 3GPP 5G Security Architecture (TS 33.501) map to?
3GPP 5G Security Architecture (TS 33.501) maps to 558 other compliance frameworks. The top mapping partners are OWASP SAMM (17% coverage), ISO 15189:2022 - Medical Laboratories Requirements for Quality and Competence (17% coverage), Azure Security Benchmark (17% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with 3GPP 5G Security Architecture (TS 33.501) compliance?
Start your 3GPP 5G Security Architecture (TS 33.501) compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about 3GPP 5G Security Architecture (TS 33.501) requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 48 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 700 frameworks.
Get Started Free →Free forever — no credit card required