CAVE-based authentication

<h2 id="network-entities">Network entities</h2>
<p>In CAVE-based authentication, two main components work together when a user is roaming on a mobile network:
</p>
<ul><li>Authentication Center (AC) (also known as HLR/AC or AuC): This is located in the user's home network and manages the authentication process. It either directly verifies the identity of the <a href="/facts/Mobile_Station/2nntUYVJ">Mobile Station</a> (MS, commonly known as a mobile phone) or shares a security key (called SSD) with the Visitor Location Register (VLR) in the network the user is visiting. The AC must have a specific security key (A-key) for each mobile device. Authentication depends on both the device and the AC having the same A-key. The AC is usually part of the Home Location Register (HLR) but can also exist as a separate system that serves multiple HLRs. Although "AuC" is the abbreviation used in GSM networks, it is sometimes incorrectly applied to CDMA networks as well.</li>
<li>Visitor Location Register (VLR): This is the network component in the visited network (the one the user is currently connected to while roaming). If the SSD key is shared with this network, the VLR can authenticate the user locally. If not, it acts as a middleman, passing authentication requests to the user's home AC for verification.</li></ul>
<p>This system ensures that users can be securely authenticated even when they are using networks outside their home area.
</p>
<h2 id="keys">Keys</h2>
<p>In mobile network authentication, the <i>authentication controller</i> is responsible for determining whether the response from the <a href="/facts/Mobile_Station/2nntUYVJ">Mobile Station</a> (MS, or mobile phone) is correct. Depending on the situation, this controller can either be the Authentication Center (AC) in the user's home network or the Visitor Location Register (VLR) in the network the user is currently roaming in. This process uses two shared keys in CAVE-based authentication, which relies on the CAVE (Cellular Authentication and Voice Encryption) <a href="/facts/Algorithm/fnl5NmRt">algorithm</a>:
</p>
<ul><li>Authentication key (A-key): This is a 64-bit secret key that is only known to the MS and the AC. If the mobile phone uses a <a href="/facts/RUIM/a72Nwvbn">RUIM</a> card (similar to a SIM card), the A-key is stored on the RUIM; otherwise, it is stored in the device's memory. The A-key is never shared with other networks. However, it is used to create another key called Shared Secret Data (SSD), which can be shared with a roaming network to allow local authentication.</li>
<li>Shared Secret Data (SSD): This is a 128-bit key created using the CAVE algorithm during a procedure known as an SSD update.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> Both the MS and the AC in the user’s home network independently calculate this SSD. The SSD, not the A-key, is used during the actual authentication process. SSD may or may not be shared between the user’s home network and a roaming network. If it is shared, it allows the roaming network to authenticate the user locally. The SSD is divided into two parts:
<ul><li>SSD_A: Used for generating authentication signatures.</li>
<li>SSD_B: Used to create session keys for encryption and voice privacy.</li></ul></li></ul>
<p>This process allows users to be securely authenticated without revealing the most sensitive key (A-key) to other networks.
</p>
<h2 id="authentication-challenges">Authentication challenges</h2>
<p>CAVE-based authentication uses two types of challenges to verify the identity of a mobile phone (MS):
</p>
<ul><li>Global challenge: This is a process where every mobile device trying to access the network must respond to a common challenge. This challenge is broadcast to all devices in the area through the network's overhead messages. To respond, the mobile phone creates an <i>authentication signature response</i> (called AUTHR) using the CAVE algorithm. It combines the challenge value, the phone’s electronic serial number (ESN), and either the last six digits dialed (if the user is making a call) or a part of the subscriber’s unique identification number (IMSI_S1). It also uses part of the shared secret data (SSD_A) to generate this response.</li>
<li>Unique challenge: This process allows the network (either the home network or a roaming network if SSD is shared) to specifically challenge a particular mobile phone. This might happen for security reasons or to verify the device’s identity. The phone generates a different <i>authentication signature response</i> (called AUTHU), using the CAVE algorithm with inputs from the unique challenge value, ESN, IMSI_S1, and SSD_A.</li></ul>
<p>CAVE-based authentication is a <i>one-way process</i>, meaning the network always authenticates the mobile phone, but the phone does not authenticate the network. The only exception is during an SSD update, where the phone may challenge the base station.
</p>
<h2 id="specification">Specification</h2>
<p>CAVE-based authentication procedures are outlined in the TIA-41 standard, which is part of the specifications created by <a href="/facts/3GPP2/6bNoq0n6">3GPP2</a> (3rd Generation Partnership Project 2). These procedures explain how mobile phones and networks verify each other in CDMA-based systems, ensuring secure communication. TIA-41, also known as X.S0004, provides detailed guidelines for how this verification, or authentication, is performed using the CAVE algorithm.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Channel_access_method/CdCGxpcu">Channel access method</a></li>
<li><a href="/facts/Authentication_and_Key_Agreement/foCkqkB4">Authentication and Key Agreement</a> (AKA) - a successor authentication type</li>
<li><a href="/facts/Cellular_Message_Encryption_Algorithm/EfRCAnUX">Cellular Message Encryption Algorithm</a> - an algorithm similar to CAVE</li></ul>

<h2 id="external-links">External links</h2>
<ul><li><a href="https://www.3gpp2.org/Public_html/Specs/X.S0004-000-E_v1.0_040406.pdf">TIA-41 - 3GPP2 X.S0004 (March 2004)</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Zhang, Chi; Liu, Jun-Rong; Gu, Da-Wu; Wang, Wei-Jia; Lu, Xiang-Jun; Guo, Zheng; Lu, Hai-Ning (1 September 2019). "Side-Channel Analysis for the Authentication Protocols of CDMA Cellular Networks". Journal of Computer Science and Technology. 34 (5): 1079–1095. doi:10.1007/s11390-019-1961-5. ISSN 1860-4749. Retrieved 18 June 2024. <a href="https://link.springer.com/article/10.1007/s11390-019-1961-5" target="_blank">https://link.springer.com/article/10.1007/s11390-019-1961-5</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Miceli, Andrew (2003). Wireless technician's handbook (PDF) (2. ed.). Boston, Mass.: Artech House. ISBN 978-1580533577. Retrieved 18 June 2024. <a href="978-1580533577" target="_blank">978-1580533577</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
</ol>

CAVE-based authentication open-in-new

CAVE-based authentication