Legacy Key

Description

In 3GPP security architecture, the Legacy Key (LK) refers to a cryptographic key that is used to support interoperability with older or legacy devices, network nodes, or procedures. The term is specified in the 35.240, 35.243, and 35.246 series, which define the 3GPP cryptographic algorithms and their usage. The LK is typically derived from or equivalent to a key that was used in an earlier release, and it is maintained in newer releases to ensure that a UE or network element that only supports the older security mechanisms can still establish a secure connection.

The need for a Legacy Key arises because mobile networks evolve gradually. When a new security feature is introduced — for example, a new key derivation function or a new encryption algorithm — not all devices in the field will support it immediately. To avoid service disruption, the network must be able to fall back to a legacy security context. The LK represents that fallback key. It may be a static key stored in the UE's SIM/USIM or a key derived during an authentication procedure that is compatible with older standards.

From an architectural perspective, the LK is managed by the security functions in the UE and the network. During initial attach or handover, the network and UE negotiate the security capabilities. If the UE indicates support only for legacy algorithms, the network selects the LK for ciphering and integrity protection. The LK is then used to initialize the appropriate legacy ciphering algorithm, such as those defined for earlier releases. The 35.240 series provides the specifications for how the LK is derived, stored, and used, including test vectors to verify correct implementation.

The LK is also relevant in interworking scenarios between different radio access technologies (RATs). For example, when a UE moves from a 5G network to an LTE network, the security context may need to be mapped. The LK can serve as a common key that is understood by both systems, allowing a smooth transition without re-authentication. This is particularly important for voice calls and other real-time services that cannot tolerate long interruptions.

Security considerations for the LK include the need to protect it from compromise and to limit its lifetime. Because legacy algorithms may be weaker than modern ones, the LK should be used only when necessary and should be replaced with stronger keys as soon as the UE and network support them. The 3GPP specifications include guidelines for key freshness and for transitioning from legacy to modern security contexts. The LK is therefore a pragmatic solution that balances security with the reality of a diverse device ecosystem.

Purpose & Motivation

The Legacy Key exists to solve the problem of backward compatibility in mobile security. When new security mechanisms are standardized, networks cannot immediately require all devices to support them, because many devices remain in use for years. The LK allows a network to provide secure service to older devices by using a key that those devices understand, while still allowing newer devices to use stronger keys.

Historically, the introduction of each new generation of mobile technology has been accompanied by a need to interwork with previous generations. For example, the transition from 3G to LTE required mechanisms to map security contexts between different core networks. The LK concept formalizes this by defining a specific key that can be used across generations. It also addresses the case where a device may not support the latest key derivation functions, ensuring that such a device can still authenticate and communicate securely.

The LK is not intended to be the primary key for new deployments; rather, it is a fallback. Its existence highlights the importance of security agility and the need to manage the lifecycle of cryptographic keys in a heterogeneous network. By specifying the LK in 3GPP standards, vendors can implement interoperable solutions that protect users even when legacy devices are present.