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

Glossary term · Security

Forward security

Forward Security (Key Derivation)

Security →

Forward security is a security property ensuring that compromise of a current key does not allow prediction of future keys, protecting handover key derivation in LTE and 5G networks against a compromised base station.

Introduced
Rel-8
Where
Security
Specifications
2 specs
Forward security Description Purpose What changed Neighbours Specifications

Description

Forward security is a cryptographic property defined in 3GPP security specifications 33.401 (EPS) and 33.501 (5G System) that governs how keys are derived during handovers. In the LTE context, the property is stated in terms of the KeNB, the base key used between the UE and the eNB. Forward security means that an eNB which knows the KeNB shared with a UE cannot computationally predict any future KeNB that will be used between the same UE and another eNB. This prevents a compromised or malicious base station from pre-computing the keys that will protect the UE's subsequent communications with other cells.

The mechanism that provides forward security is the hierarchical key derivation chain anchored at the ASME (Access Security Management Entity) in the core network. The ASME holds the long-term key K and derives the Kasme, from which the KeNB is derived at initial context setup. During handovers, the source eNB does not simply pass the current KeNB to the target eNB. Instead, a fresh KeNB is derived using a one-way key derivation function (KDF) that takes the current KeNB and a freshness parameter, such as the target cell's physical cell identity (PCI) and downlink frequency (EARFCN-DL), as inputs. Because the KDF is a one-way function, knowledge of the current KeNB does not permit computation of the next KeNB without also knowing the inputs and the derivation direction.

The specifications further define n-hop forward security: an eNB is unable to compute keys that will be used between the UE and another eNB to which the UE connects after n or more handovers, where n is 1 or 2. This is achieved by ensuring that each handover derives a new KeNB from the previous one through the KDF, so that after n derivation steps the original eNB's knowledge is insufficient to reconstruct the key. The value of n reflects the depth of the derivation chain that the network guarantees to be opaque to any single eNB.

In the 5G System, the same principle is applied to the KgNB, the corresponding base key between the UE and the gNB. The security architecture in 33.501 defines key derivation for handovers and for mobility between different radio access technologies, preserving the forward security property across LTE and NR. The key hierarchy includes K, KAUSF, KSEAF, KAMF, and KgNB, with each level derived through a KDF, ensuring that compromise at one level does not cascade to future keys at lower levels.

Forward security is closely related to backward security, which ensures that a compromised key does not reveal past keys. Together they form the basis of the key freshness guarantees in cellular networks. The property is enforced through the standardized key derivation functions and the requirement that freshness parameters be included in each derivation, preventing replay and ensuring that each handover produces a distinct key. In Release 20, the definition was generalized from the KeNB-specific wording to a generic statement about any key Km, reflecting the broadening of the concept across multiple key types and access technologies.

Purpose & Motivation

Forward security exists to limit the damage that a compromised base station can inflict on a user's communications. In a cellular network, base stations are physically accessible and potentially vulnerable to attack; if an attacker gains control of an eNB or gNB, they obtain the current keys used with the UEs attached to that cell. Without forward security, the attacker could use those keys to derive or predict the keys that will be used after the UE hands over to other cells, enabling long-term interception of the user's traffic. Forward security ensures that the compromised node's knowledge becomes useless for future keys.

The concept was introduced in Release 8 with the LTE security architecture in 33.401. Earlier generations of cellular security did not formalize this property in the same way, and the flat, IP-based LTE architecture with direct eNB-to-eNB handover interfaces (X2) made it important to constrain what a compromised eNB could learn. The n-hop formulation was adopted to give a precise, testable guarantee about the depth of the derivation chain that remains opaque.

With the introduction of 5G in Release 15, the property was carried into 33.501 for the KgNB and the 5G key hierarchy, preserving continuity across radio access technologies. The Release 20 rewording generalizes the definition beyond the KeNB to any key Km, acknowledging that forward security applies to multiple key types and reflecting the maturation of the concept from an LTE-specific rule to a general security principle in the 3GPP key hierarchy.

What changed in its specifications

The latest release-to-release comparison of specifications that define Forward security. 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

Introduced with the LTE security architecture in 33.401. Defined forward security in terms of the KeNB, specifying that an eNB with knowledge of the KeNB cannot predict future KeNBs used between the same UE and another eNB, and introduced the n-hop forward security property with n=1 or 2.

Definition carried over unchanged; the forward security property continued to apply to LTE handover key derivation.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged in 33.401; the 5G security specification 33.501 introduced the corresponding property for the KgNB in the 5G key hierarchy.

Definition carried over unchanged.

Definition carried over unchanged; only formatting of the text was normalized, with no change in meaning.

Definition carried over unchanged; only formatting of the text was normalized, with no change in meaning.

Definition carried over unchanged; the KeNB-based wording was retained.

Wording changed: the definition was generalized from the KeNB-specific statement to a generic property about any key Km. It now states that for an entity with knowledge of Km used between that entity and a second entity, it is computationally infeasible to predict any future Km+n (n>0) used between a third entity and the second entity, broadening the concept beyond LTE handover keys to the general 3GPP key hierarchy.

Defining Specifications

3GPP specifications that define or reference Forward security, 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