Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Security

ADM

Administrative Access Condition

Security →

ADM is the highest-privilege administrative access condition in a UICC/USIM that controls file access, ensuring critical subscriber data and network parameters remain protected by the operator that created them.

Introduced
Rel-5
Where
Services
Specifications
11 specs
Also in
Core Network, Security
ADM Description Purpose What changed Neighbours Detected Changes Specifications

Description

ADM (Administrative Access Condition) is a fundamental security concept within 3GPP specifications for Universal Integrated Circuit Card (UICC) and Universal Subscriber Identity Module (USIM) applications. It functions as an access control flag or condition associated with specific Elementary Files (EFs) stored on the smart card. An EF marked with ADM can only be accessed (for reading, updating, or deleting) by entities possessing the correct ADM key or credentials, which are exclusively held by the administrative authority—usually the mobile network operator (MNO) or the service provider that created and personalized the UICC.

The mechanism operates within the framework of the UICC's security architecture, which includes a hierarchy of access conditions: ALWays (free access), NEVer (no access), CHV (Card Holder Verification using PIN), and ADM. ADM sits at the top of this hierarchy, providing the strongest protection. When an application on the terminal (Mobile Equipment) attempts to access an EF, the UICC's operating system checks the file's access conditions. If ADM is set, the terminal must present valid authentication using the ADM key, typically through a secure channel established with the card. This process often involves cryptographic challenges and responses to prove possession of the key without exposing it.

Key components involved in ADM enforcement include the EF's file descriptor (which stores the access condition), the UICC's security manager, and the authentication algorithms. The ADM condition is defined during the card personalization phase and is crucial for protecting sensitive files such as those containing network access credentials (like IMSI), operator-specific service parameters, and roaming lists. The administrative authority uses ADM to maintain control over these critical parameters, ensuring they can be updated securely over-the-air (OTA) or during physical maintenance while preventing tampering by end-users or unauthorized applications.

In the broader network architecture, ADM supports secure subscription management and service provisioning. It enables operators to remotely manage UICC content through OTA platforms by authenticating with ADM keys. This is essential for modern eSIM (eUICC) profiles and IoT deployments where remote management is paramount. The integrity of the ADM mechanism underpins trust in the subscriber identity module, as compromise could lead to unauthorized network access or service theft. Thus, ADM keys are among the most closely guarded secrets in an operator's security infrastructure, often managed through Hardware Security Modules (HSMs) in secure provisioning centers.

Purpose & Motivation

ADM was created to address the critical need for mobile network operators to maintain exclusive administrative control over sensitive data stored on subscriber identity modules. In early GSM systems, as smart cards evolved from simple authentication tokens to complex service platforms, operators required a mechanism to protect network-specific files from unauthorized access—whether by end-users, third-party applications, or malicious actors. Without ADM, operators would be unable to securely update essential parameters like IMSI, cryptographic keys, or service settings, compromising network security and service integrity.

The introduction of ADM in 3GPP Release 5 formalized this highest-level access control within the standardized security framework for UICC/USIM applications. It solved the limitation of earlier, more rudimentary access controls that lacked a clear hierarchy for administrative privileges. By defining ADM as a distinct condition, 3GPP enabled operators to delegate certain user-accessible functions (via CHV/PIN) while reserving ultimate authority over critical files. This separation of concerns is fundamental to modern subscription management, allowing users to personalize some aspects (like phonebooks) while ensuring network-critical data remains under operator control.

Historically, ADM's creation was motivated by the growing complexity of mobile services and the shift toward OTA updates. As operators began deploying value-added services and needed to manage subscriptions remotely, a robust administrative access mechanism became essential. ADM provided the technical foundation for secure OTA platforms, enabling trusted service management without physical card access. This capability has become even more crucial with the advent of eSIM and IoT, where remote provisioning and lifecycle management are standard requirements, making ADM a cornerstone of contemporary mobile security architectures.

What changed in its specifications

The latest release-to-release comparison of specifications that define ADM. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 28.540Rel-18 → Rel-19

Rel-19 adds management clauses for Ambient IoT, IAB nodes, and regenerative NTN with UE-Satellite-UE communication. It also shifts NTN responsibility from 5GC to 3GPP.

Full comparison in TS 28.540 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-19 2 changes
  • Updates to AIOTF and ADM to support temporary ID TS 23.369CR0101
  • ADM Service Operations Update TS 23.369CR0011
Rel-20 1 change
  • Add ADM as NF service consumer TS 29.504CR0348

Defining Specifications

3GPP specifications that define or reference ADM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.369 vk10 5GS Architecture for Ambient IoT Rel-20 read
TS 24.022 vj00 Radio Link Protocol (RLP) for Circuit Switched Data Rel-19 read
TS 28.540 vk40 5G Network Resource Model (NRM) Stage 1 Rel-20 read
TS 29.504 vk10 Nudr Unified Data Repository Services Rel-20 read
TS 31.103 vj10 IM Services Identity Module Specification Rel-19 read
TS 32.181 vj00 User Data Convergence Management Framework Rel-19 read
TR 32.901 vj00 UDC Application Data Models Study Rel-19 read
TS 33.369 vj40 AIoT Security Architecture and Procedures Rel-19 read
TS 33.713 vj00 Security Study for Ambient IoT in 5G Rel-19 read
TS 44.064 vj00 GPRS Logical Link Control (LLC) Protocol Rel-19 read