Generic Bootstrapping Architecture

Description

The Generic Bootstrapping Architecture (GBA), also referred to as Generic Authentication Architecture (GAA), is a standardized security framework defined by 3GPP that provides a method for user equipment (UE) and network application servers (NAFs) to derive shared session keys. It reuses the robust authentication and key agreement (AKA) procedures already established between the UE and the mobile network's Home Subscriber Server (HSS). The core idea is to 'bootstrap' application-layer security from this proven network-layer authentication, creating a trusted security association for services without requiring users to manage additional usernames and passwords.

The architecture involves several key functional entities: the Bootstrapping Server Function (BSF), the Network Application Function (NAF), the Home Subscriber Server (HSS), and the User Equipment (UE). The process begins with a bootstrapping procedure between the UE and the BSF. The UE and BSF perform a mutual authentication using the 3GPP AKA protocol, facilitated by the HSS which provides authentication vectors. Upon successful authentication, both the UE and the BSF derive a shared, session-specific key called the Bootstrapping Transaction Identifier (B-TID) and a related key material, Ks. The B-TID serves as a reference to this shared secret.

Subsequently, when the UE needs to access a service provided by a NAF (e.g., a streaming server or a corporate portal), it presents the B-TID to the NAF. The NAF, in turn, contacts the BSF using the Zn interface, providing the B-TID. The BSF verifies the B-TID and, if valid, derives a NAF-specific key, Ks_NAF, from the master key Ks and the NAF's identifier. The BSF then sends this Ks_NAF securely to the NAF. Now, both the UE (which can independently derive the same Ks_NAF) and the NAF possess a shared secret key. They can use this key to secure their communication, for instance, by using it within TLS-PSK (Pre-Shared Key) or to generate keys for encryption and integrity protection at the application layer. This entire process allows for single sign-on-like experience across different services hosted by different NAFs, all secured by the user's SIM card credentials.

Purpose & Motivation

GBA was created to address the growing need for secure authentication to internet-based application services (like video streaming, email, or banking) accessed from mobile devices, without forcing users to remember and enter separate credentials for each service. Before GBA, application servers either relied on weak username/password combinations, required complex public key infrastructure (PKI) deployment on UEs, or had no integrated security with the mobile operator's trust domain. This led to poor user experience, security vulnerabilities, and fragmented identity management.

The primary motivation was to leverage the strong, SIM-based authentication already present in mobile networks. The 3GPP AKA protocol provides mutual authentication and strong key establishment between the UE and the network core. GBA repurposes this infrastructure to create a generic key distribution service for the application layer. This solves the problem of credential proliferation and allows mobile operators to offer value-added services with built-in, high-grade security derived from the SIM.

Furthermore, GBA enables new business models by allowing third-party application providers (the NAFs) to rely on the mobile operator's authentication infrastructure. A content provider can offer a service securely to a subscriber without needing to operate its own authentication system; it simply integrates with the operator's BSF. This created a trusted ecosystem, facilitated the deployment of IP Multimedia Subsystem (IMS) services, and provided a foundation for secure machine-to-machine (M2M) communication, addressing the limitations of previous ad-hoc and less secure application authentication methods.

Key Features

• Leverages existing 3GPP AKA and SIM/USIM for strong authentication
• Bootstraps application-layer security from network-layer credentials
• Enables single sign-on across multiple application servers (NAFs)
• Defines clear functional entities: BSF, NAF, HSS, UE
• Supports key derivation for specific application servers (Ks_NAF)
• Facilitates secure service access for both HTTP-based and non-HTTP services

Evolution Across Releases

Defining Specifications