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

Glossary term · Security

Activation of security context

Activation of Security Context

Security →

Activation of security context is the process of taking a security context into use, enabling ciphering and integrity protection of signalling and user data between UE and network, a fundamental step in establishing a secure connection in 3GPP systems.

Introduced
Rel-8
Where
Security
Specifications
2 specs
Activation of security context Description Purpose What changed Specifications

Description

Activation of security context is a core security procedure in 3GPP networks, defined in TS 33.401 for EPS (LTE/EPC) and TS 33.501 for 5GS. A security context is a set of security parameters — including the root key (KASME in EPS, KSEAF in 5GS), derived intermediate keys (KNAS, KRRC, KUP), selected ciphering and integrity algorithms, and the associated counters (NAS COUNT, PDCP COUNT) — that together allow the UE and the network to protect signalling and user-plane traffic. Activation means that this context is not merely stored but is actually taken into use: the keys are installed in the relevant protocol layers, the chosen algorithms are applied, and subsequent messages are ciphered and integrity-protected.

In EPS, security activation is performed during the initial attach or tracking area update. After authentication (EPS-AKA) and NAS security mode command/procedure, the MME activates NAS security by sending a NAS Security Mode Command (SMC) containing the selected NAS ciphering and integrity algorithms. The UE verifies the SMC integrity, activates the corresponding NAS security context, and replies with a NAS Security Mode Complete, which is the first integrity-protected NAS message. Subsequently, the eNB activates AS security via the AS Security Mode Command, after which RRC and user-plane traffic are protected. The activation is thus a two-stage process (NAS then AS) with strict ordering to prevent bidding-down attacks.

In 5GS, the procedure is analogous but uses the 5G-AKA or EAP-AKA' authentication framework and the KSEAF hierarchy. The AMF activates NAS security with a NAS Security Mode Command, and the gNB activates AS security with an AS Security Mode Command. 5GS additionally supports horizontal and vertical key derivation, key refresh, and the concept of a partially activated security context (e.g., NAS security active but AS security not yet active). The activation state is tracked per UE and per RAT, and handovers between EPS and 5GS require mapping or re-derivation of the security context.

Activation is tightly coupled with the security mode command procedure, which is designed to be protected against downgrade attacks: the UE must accept the network's selected algorithms unless it has a local configuration that forbids them, and the SMC itself is integrity-protected using the newly derived keys. The activation also establishes the starting values for NAS and PDCP COUNTs, which are critical for replay protection and ciphering synchronisation.

From a management perspective, activation of security context is a prerequisite for any subsequent protected procedure, including handover, service request, and data transfer. Failure to activate security correctly results in rejection of the connection or fallback to unprotected operation, which is prohibited in most deployment scenarios. The term has remained stable across releases, with only editorial wording changes, reflecting the maturity of the underlying security architecture.

Purpose & Motivation

Activation of security context exists to ensure that once a UE and network have authenticated each other and agreed on keys and algorithms, those security parameters are actually enforced on the air interface and in the core network. Without an explicit activation step, a UE could hold a valid security context that is never applied, leaving signalling and user data unprotected. The procedure also prevents downgrade attacks by binding the algorithm selection to an integrity-protected Security Mode Command.

Historically, early 3G systems already had security mode procedures, but the EPS and 5GS architectures generalised the concept into a layered security context with separate NAS and AS activation. This separation allows the core network to secure NAS signalling before the radio access network activates AS security, which is important because the eNB/gNB may not yet be trusted with the full context. The 5GS further refined the concept with key hierarchies and the ability to refresh keys without full re-authentication.

The term itself has been stable since Rel-8, with only editorial changes in Rel-19 and Rel-20, indicating that the fundamental mechanism has not required architectural revision. Its persistence across releases reflects its role as a foundational building block of 3GPP security.

What changed in its specifications

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

TS 33.401Rel-18 → Rel-19

Rel-19 adds security annex clauses for Store and Forward Satellite operation to TS 33.401. It also adds definitions for feeder link, service link, Store and Forward Satellite operation, and IOPS-enabled UE.

Full comparison in TS 33.401 →
TS 33.501Rel-18 → Rel-19

Rel-19 TS 33.501 adds roaming and inter-PLMN indirect communication authorization, fast re-authentication for non-3GPP mobility, and AI/ML security clauses for positioning and federated learning. It also adds NPN security, NRF access token key retrieval, LTM security, and monitoring-of-signalling-traffic protection.

Full comparison in TS 33.501 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-8 Initial

Initial definition introduced in TS 33.401 for EPS: the process of taking into use a security context, covering NAS and AS security activation via Security Mode Command procedures.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8, while TS 33.501 introduced the 5GS security architecture with KSEAF-based context activation.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Definition carried over unchanged from Rel-8.

Wording changed editorially: the definition was reformatted to 'The process of taking a security context into use.' with no substantive change to the meaning.

Definition retained the Rel-19 wording: 'The process of taking a security context into use.'

Defining Specifications

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

SpecificationTitleRelease
TS 33.401 vj20 EPS Security Architecture Rel-19 read
TS 33.501 vk30 5G Security Architecture Rel-20 read