43 controls
69 frameworks share controls with it
International (3GPP)
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
3GPP TS 33.501 5G Security Evidence & Implementation Kit
43 controls is the documentation set somebody has to write. This is that set,
already written: an adopt-ready artifact for every control in policy and procedure text you
edit rather than draft, and the evidence checklist an auditor asks for against each.
See what is in it, $249
The same set every buyer of this kit receives. Nothing here is produced on request.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
Every control
| Code | Control | Also in |
33.501-10 | Security for Interworking with EPS | 1 |
33.501-11 | Security Aspects of IMS | 1 |
33.501-13.1 | Service-Based Architecture Security (TLS) | 1 |
33.501-13.2 | Network Function Service Authorization (OAuth 2.0) | 1 |
33.501-13.4 | SEPP and Inter-PLMN Security (N32) | 2 |
33.501-14 | Network Slicing Security | 1 |
33.501-15 | Steering of Roaming Security | 1 |
33.501-16 | Security for User Plane Integrity Protection | 2 |
33.501-17 | Privacy and Pseudonymization | 1 |
33.501-4.2 | Security Domains and Trust Model | 2 |
33.501-5.1 | Subscription Permanent Identifier Protection | 1 |
33.501-6.1 | Primary Authentication (5G AKA / EAP-AKA') | 2 |
33.501-6.2 | Key Hierarchy | 2 |
33.501-6.4 | NAS Security | 2 |
33.501-6.5 | AS Security (RRC and User Plane) | 2 |
33.501-6.7 | Security Mode Command Procedures | 1 |
33.501-8 | Security Aspects of UDM/UDR | 2 |
33.501-9 | Security for Non-3GPP Access | 1 |
33.501-Annex-D | Cryptographic Algorithms | 2 |
33.501-OAM | Management Plane Security | 1 |
TS33.501-13.1 | NF Registration and Discovery Security | 33 |
TS33.501-13.2 | NF Service Authorization | 46 |
TS33.501-13.3 | N32 Interconnect Security | 1 |
TS33.501-13.4 | OAuth 2.0 Authorization Framework | 33 |
TS33.501-14.1 | Security for Network Slicing | 1 |
TS33.501-14.2 | Security for Edge Computing | 1 |
TS33.501-14.3 | Security for URLLC Services | 1 |
TS33.501-14.4 | Security for IAB | 1 |
TS33.501-4.1 | 5G Security Architecture Overview | 2 |
TS33.501-4.2 | Security Feature Groups | 1 |
TS33.501-4.3 | Security Domains and Stratum | 1 |
TS33.501-4.4 | Network Functions in the Security Architecture | 1 |
TS33.501-6.1 | Authentication Framework | 35 |
TS33.501-6.2 | Key Hierarchy and Derivation | 2 |
TS33.501-6.3 | EAP-AKA' Authentication | 2 |
TS33.501-6.4 | NAS Security | 2 |
TS33.501-6.5 | AS Security and PDCP Protection | 2 |
TS33.501-6.6 | AS Security | 39 |
TS33.501-6.7 | Security Key Hierarchy | 2 |
TS33.501-6.8 | Security in Handover | 1 |
TS33.501-7.1 | Untrusted Non-3GPP Access Security | 1 |
TS33.501-7.2 | Security Visibility and Configurability | 1 |
TS33.501-7.3 | Wireline Access Security | 1 |
Tell me when 3GPP 5G Security Architecture (TS 33.501) files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What an auditor will ask you to produce
The artefacts named on the failure modes this framework speaks to.
- Access control matrices
- KMS configuration
- Encryption coverage report
- Key rotation records
- Information security policy
- Risk assessment and treatment plan
- mTLS configuration
- Certificate inventory and expiry tracking
- Server authentication design documentation
- TLS certificate inventory
How programmes fail on this
Failure modes named by this framework and others. Each opens the full record.
What this page is
A control-level reference for 3GPP 5G Security Architecture (TS 33.501), drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition