Bootstrapping Server Function for Legacy Wireless Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy wireless communication systems, such as GSM, are vulnerable to replay attacks and key exposure due to weaknesses in their security protocols, lacking the advanced authentication and key agreement mechanisms found in 3G networks, which hinders secure key bootstrapping for mobile network applications.
Innovation Solution
A challenge-response key exchange method is implemented between a bootstrapping server function and mobile terminals using a server-authenticated public key mechanism, leveraging pre-shared secret keys and Diffie-Hellman public keys to securely derive and verify application security keys, thereby extending the Generic Authentication Architecture to support legacy systems without introducing new vulnerabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If GSM authentication and key agreement protocols are used for legacy mobile terminals, then compatibility with existing systems is maintained, but security vulnerabilities arise including susceptibility to replay attacks and key exposure
Solution Approach 1:
A bootstrapping server function is introduced as an intermediary between the legacy mobile terminal and the network. This server implements the GAA protocol to establish secure authentication and key agreement, while the legacy terminal continues to use its existing SIM card and GSM protocols. The intermediary translates and bridges the security mechanisms, allowing legacy terminals to benefit from enhanced security without requiring hardware replacement.
Solution Approach 2:
The authentication system is segmented into two independent layers: the legacy GSM authentication layer (using SIM card and existing protocols) and the new GAA bootstrapping layer (using the bootstrapping server). This segmentation allows each layer to operate independently, preserving legacy compatibility while adding enhanced security capabilities through the bootstrapping mechanism that prevents replay attacks and key exposure.
2Reliability
If 3G AKA protocol with USIM is implemented, then security against replay attacks is improved, but legacy GSM terminals cannot be authenticated
Solution Approach 1:
The bootstrapping server function is designed with multi-functionality to support both legacy GSM terminals and modern 3G terminals. It implements the GAA protocol universally, allowing any terminal with a SIM card to undergo secure authentication and key agreement regardless of whether it is a legacy GSM device or a 3G device. This universal approach enables the system to provide enhanced security to legacy terminals without requiring them to upgrade to USIM cards.
3Device complexity
If GSM security mechanisms are used, then simplicity of implementation is maintained, but weaknesses in encryption algorithms and lack of network authentication create security vulnerabilities
Solution Approach 1:
The bootstrapping server acts as an intermediary that handles the complex security operations, including implementation of the GAA protocol, random challenge generation, and secure key derivation. This allows legacy terminals to maintain their simple GSM implementation while the server compensates for security weaknesses by providing robust authentication and key agreement mechanisms that address encryption algorithm weaknesses and implement proper network authentication.
Data Source
AI summary
A mutual authentication method is provided for securely agreeing application-security keys with mobile terminals supporting legacy Subscriber Identity Modules (e.g., GSM SIM and CDMA2000 R-UIM, which do not support 3G AKA mechanisms). A challenge-response key exchange is implemented between a bootstrapping server function (BSF) and mobile terminal (MT). The BSF generates an authentication challenge and sends it to the MT under a server-authenticated public key mechanism. The MT receives the challenge and determines whether it originates from the BSF based on a bootstrapping server certificate. The MT formulates a response to the authentication challenge based on keys derived from the authentication challenge and a pre-shared secret key. The BSF receives the authentication response and verifies whether it originates from the MT. Once verified, the BSF and MT independently calculate an application security key that the BSF sends to a requesting network application function to establish secure communications with the MT.