Key Freshness

Description

Key freshness is a fundamental security concept in 3GPP networks, defined as the property that a key can be guaranteed to be new, as opposed to an old key being reused through actions of either an adversary or an authorised party. This concept is critical in authentication and key agreement (AKA) protocols, where session keys must be unique for each communication session to prevent replay attacks, key reuse, and other cryptographic vulnerabilities. In 3GPP, key freshness is achieved through the use of random challenges (e.g., RAND in AKA), sequence numbers (e.g., SQN in EPS-AKA and 5G-AKA), and nonces. The authentication server (e.g., HSS, UDM) generates authentication vectors that include a random challenge and a sequence number, which the UE verifies to ensure the freshness of the derived keys. If the sequence number is not within an acceptable range, the UE rejects the authentication, preventing the reuse of old keys. Key freshness is applicable across various 3GPP access technologies, including UTRAN, E-UTRAN, and 5G NR, and is specified in multiple security specifications such as 33.102 (3G security), 33.105 (cryptographic algorithm requirements), 33.203 (IMS security), 33.204 (network domain security), 33.210 (IP network layer security), and 33.234 (wireless LAN interworking). The concept ensures that even if an attacker compromises a key from a previous session, they cannot use it to impersonate a user or decrypt current traffic. Key freshness also protects against authorised parties (e.g., a rogue network element) replaying old keys. The definition has remained consistent across all releases from Rel-8 to Rel-19, indicating its enduring importance and stability. In practice, key freshness is implemented through mechanisms like the authentication and key agreement procedure, where a new authentication vector is used for each authentication, and the derived keys are session-specific. Additionally, key refresh procedures (e.g., re-authentication) can be triggered to ensure freshness during long sessions. The property is essential for maintaining the security of both control plane and user plane data, and it underpins the trust model of 3GPP networks.

Purpose & Motivation

Key freshness exists to address the critical security requirement that cryptographic keys must not be reused across sessions or contexts. Without key freshness, an attacker could replay old authentication messages or reuse compromised keys to impersonate a legitimate user or network element. In early mobile networks (e.g., GSM), key reuse was a vulnerability, and the introduction of sequence numbers and random challenges in UMTS (3G) significantly improved security. The concept was formalized in 3GPP specifications to provide a clear definition and requirements for all subsequent generations. It solves the problem of replay attacks, where an adversary captures a valid authentication exchange and replays it to gain unauthorized access. It also prevents key reuse by authorised parties, such as a compromised network node, from undermining security. The motivation for key freshness is to ensure that each session has unique keys, thereby limiting the impact of key compromise and providing forward secrecy. The definition has remained unchanged since Rel-8, reflecting its fundamental nature and the maturity of the security architecture. As networks evolve to 5G and beyond, key freshness continues to be a cornerstone of security, adapted to new authentication frameworks like 5G-AKA and EAP-AKA'. It is also relevant in IoT contexts, where resource-constrained devices require efficient yet secure key management. Overall, key freshness is a timeless principle that ensures the integrity and confidentiality of mobile communications.