1-s2.0-S259000562200087X-main
1-s2.0-S259000562200087X-main
1-s2.0-S259000562200087X-main
Array
journal homepage: www.elsevier.com/locate/array
Keywords: The end user’s Quality of Experience (QoE) will be improved while accessing services in Fifth Generation
5G Mobile Network (5G), supported by enhanced security and privacy. The security guarantees offered by the
EAP-AKA’ Authentication and Key Agreement (AKA) protocols will be depended upon by end users and network operators.
Security protocol
The AKA protocols have been standardized for 5G networks, and the Extensible Authentication Protocol (EAP)-
Formal methods
AKA’ protocol is one of the main authentication mechanisms that has been specified for User Equipment (UE)
Verification
Authentication
and network mutual authentication. This article models the EAP-AKA’ protocol and conducts an extensive
ProVerif formal verification of the EAP-AKA’ protocol as defined in the 5G security standard to determine whether the
Applied pi calculus protocol is verifiably secure for 5G. It provides a security evaluation of the EAP-AKA’ protocol based on the
Performance evaluation current 5G specifications using ProVerif, a security protocol proof verifier. It also presents security properties
that support the security verification, as well as quantitative properties that are used to assess the protocol’s
performance. Finally, it compares the EAP-AKA’ and 5G-AKA protocols’ security and performance results.
∗ Corresponding author.
E-mail addresses: [email protected] (E.K.K. Edris), [email protected] (M. Aiash), [email protected] (J. Loo).
https://doi.org/10.1016/j.array.2022.100254
Received 1 September 2022; Received in revised form 10 October 2022; Accepted 25 October 2022
Available online 28 October 2022
2590-0056/© 2022 The Author(s). Published by Elsevier Inc. This is an open access article under the CC BY license (http://creativecommons.org/licenses/by/4.0/).
E.K.K. Edris et al. Array 16 (2022) 100254
considerations are discussed. Section 7 presents the performance eval- The authors in [5] modelled the entire architecture of the 5G EAP-
uation of the protocol. The concluding remarks and future work are AK’A protocol through symbolic model verification with analysis. They
summarized in Section 8. also formally verified the security of the protocol. With a thorough
formal investigation of the security-related characteristics of the 5G
2. Related work EAP-TLS authentication protocol, the authors in [3] reviewed EAP
using ProVerif. The authors discussed the EAP framework and anal-
The authors in [3–5] reviewed the EAP concept that was spec- ysed the security features based on 5G-AKA in [12,15]. With security
ified under Request for Comment (RFC) 3748 as an authentication analysis based on Lowe’s taxonomy, the authors in [16] formally mod-
framework. [6]. It can be used on dedicated links, wired and wireless elled and examined the EAP-AKA’ using Tamarin. The related work
networks, and runs directly on data link layers without requiring an in officially analysed the EAP-AKA’ protocol using formal methods
IP address. 3GPP designed the EAP-AKA protocol, which was then with various automated tools, but they did not evaluate the protocol’s
confirmed by the EAP WG in RFC 4187 [7]. It was later specified effectiveness. In contrast, this research formally analysed and evaluated
as an EAP method for authentication and session key distribution for the protocol’s performance using the two techniques that are covered
Universal Mobile Telecommunications System (UMTS). Identity privacy in the next sections.
support, result indications, and a fast re-authentication procedure were
all added to the EAP-AKA. This made the use of AKA method for 3. EAP-AKA’ protocol
primary authentication possible within the EAP framework, later im-
proved in RFC 9048 [8] with a new EAP method, EAP-AKA’. A new 3GPP defined the EAP-AKA’ protocol as one of the main methods
key derivation function was added, which binds the derived keys with of AKA between a mobile device and its HN in the 5G security stan-
the name of the access network, preventing binding attacks [4]. dard [1]. The authentication protocol includes a home control feature
In addition, the EAP-AKA’ can be used to authenticate the UE to that enables the HN operator to determine whether the device is au-
network access in a 5G, non-3GPP networks and integrated in security thenticated in each network and make the final authentication decision.
frameworks [9]. The protocol was specified in TS 33.501 [1] as a 5G After a successful run of the protocol, all parties should be able to derive
primary authentication method. The EAP-AKA’ uses cipher key (CK’) and agree on an anchor key, which is used to generate session keys for
and integrity key (IK’) as specified in TS33.402 [10] with an updated communication between UEs and Next Generation Node B (gNodeB) in
hash function Secure Hashing Algorithm (SHA)-256 and Hash based the local network. Additionally, for secondary authentication between
Message Authentication Code (HMAC)-SHA-256 [4]. the UE and external DN, EAP method is preferred.
The AKA is an authentication process where parties involved ex- The 5G system consists of the following:
change messages to verify one another through mutual authentication
and session key agreement. The 5G system supports AKA between the • UE: A Mobile Equipment (ME) which stores the Universal Sub-
UE and SN, authorized by the HN. It provides ciphering, integrity scriber’s Identity Module (USIM) with cryptographic capabili-
and replay protection and privacy within the 5G, enabling the UE to ties like symmetric encryption algorithms, HMAC, and session
access the HN via SN securely. 5G support primary authentication and counter, Subscriber’s Permanent Identifier (SUPI), public key of
secondary authentication methods for accessing the network in 5G and its HN, key K.
services from external DN, respectively. The EAP framework can be • HN: Comprises security functions and the database that support
used for both methods, as specified in 5G standard [1]. authentication, generates vectors and stores user subscription
data.
2.2. Protocol verification using formal methods and automated proof veri- • SN: The radio access network to which the UE connects to access
fier the HN.
2
E.K.K. Edris et al. Array 16 (2022) 100254
• The backend authentication server is represented by the AUSF key derivation using the at_kdf_input parameters. The keys related to
with the support of ARPF and UDM. authentication include keys: K, CK, IK, CK’, and IK’ which are used
to generate the EMSK (𝐾𝐴𝑈 𝑆𝐹 ) then 𝐾𝑆𝐸𝐴𝐹 and later used to derive
The main EAP-AKA’ Attributes in the EAP-request/response are
other keys to secure communication between the UE and other network
AT_RAND, AT_AUTN, AT_RES, AT_MAC, AT_KDF, AT_KDF_INPUT,
AT_MAC, AT_AUTS. There are some significant changes that have been entities. In addition, the KDF input parameters for CK’ and IK’ are the
made in EAP-AKA’, as per 5G security specifications [8] as follows: same only separated by the return of a 256-bit output, with CK’s 128
most significant bits and IK’s 128 least significant bits [10].
• Network name field: Both the UE and the SEAF must generate the
SNN, setting the service code to ‘‘5G’’ and the network identifier
to ‘‘SNID’’ for the network to which the UE is authenticating and 4. Modelling of EAP-AKA’ protocol
for the SEAF to SN to which the AUSF is delivering authentication
data.
• The identifiers: SUPI, SUCI, SNID. In this modelling, the values used for Authentication Vectors (AV)
• Inputs in key derivation: It is critical for identity privacy, privacy- are defined in Table 1: They include a random nonce RAND as a
friendly and non trackable identifiers in 5G. challenge, AUTN as an authentication token to validate the challenge’s
• Session identifiers: = EAP Type code ∥ RAND ∥ AUTN. It carries freshness and authenticity, and an expected reply as XRES to the
the AT_KDF_INPUT attribute, which ensures that the UE and AUSF challenge. The EAP-AKA’ protocol is modelled with four entities (UE,
are both aware of the access network’s name. To enable future SEAF, AUSF, and ARPF/UDM). The focus is on authentication and
extensions, it offers key derivation function negotiation via the authentication failure, not re-authentication. XOR and HN public keys
AT_KDF parameter. with Elliptic Curve Integrated Encryption Scheme (ECIES) profiles are
used to conceal the SQN and SUPI, respectively. By including ‘‘SNN’’ in
3.2. Keys derivation the chain of key derivations parameters, the anchor key 𝐾𝑆𝐸𝐴𝐹 binding
with SN is enforced, guaranteeing that the anchor key is specific for an
During the derivation of 𝐾𝑆𝐸𝐴𝐹 from the 𝐾𝐴𝑈 𝑆𝐹 following a suc- authentication process between a network and a UE. 5G authentication
cessful authentication procedure between the UE and the HN, the that utilizes the ARPF and USIM directly provides a stronger guarantee,
UE’s identity and the access network ID are used as inputs in the similar to fast re-authentication in EAP-AKA’.
3
E.K.K. Edris et al. Array 16 (2022) 100254
Table 1 long-term IPSec, (D)TLS, or DIAMETER sessions. SEAF and AUSF are
5G EAP-AKA’ notation and description.
Diameter-based systems that run over IPSec or TLS.
Notation Description 3GPP tries to address security issues of fake base station and non-
SNname/SNN Service code:SNID repudiation by increasing home control. This is achieved by AUSF
K Symmetric key (UE, HN)
sending authentication confirmation to ARPF, HN confirming the UE’s
𝑃 𝐾𝐻𝑁 Public key (HN)
𝑆𝐾𝐻𝑁 Private key (HN) identity and authorizing the SN sending the SNN to UE [1,11]. The
SIDF Decrypt SUCI function assumption is that EAP-AKA’ provides the same security as EAP-AKA
RAND Random nonce challenge or better. However, the EAP-AKA’ can be affected by same attacks
SUCI/SUPI User’s Network Access as 5G-AKA protocol like monitoring, location, desynchronization and
Identifier (NAI)
AUTN (SQNHN ⊕ AK,MAC,AMF)
linkability attacks, which affects the privacy properties [18].
MAC,MAC2 f1(K, (SQNHN, Rand,AMF) There have been no revealed attacks that compromise the AKA
RES, XRES f2(K, Rand) security properties defined under the originally assumed trust model
CK f3(K, Rand) and that of EAP-AKA’ [8]. Despite this, the diameter protocol is still
IK f4(K, Rand)
vulnerable to man-in-the-middle, malware, and DDoS attacks [11,19].
AK f5(K, Rand)
CK’ ik, ck, snn, (sqn⊕ak) Diameter dependent on the peer-to-peer principle rather than end-to-
IK’ ik, ck, snn, (sqn ⊕ak) end encryption. Furthermore, interception and information gathering
𝐾𝐴𝑈 𝑆𝐹 /EMSK KDF((CK’, IK’), is possible due to diameter’s use of same route for request/response
(SNN, SQN ⊕ AK)) message exchange.
𝐾𝑆𝐸𝐴𝐹 KDF(𝐾𝐴𝑈 𝑆𝐹 , SNN)
SQN Sequence Number
MACS f1* (AMF, RAND, K, SQNUE) 4.2. Protocol message exchange
AK* f5* (K, Rand)
AUTS (SQNUE ⊕ AK) ∥ MACS The EAP-AKA’ protocol process is divided into the following three
h(x) Hash value of message x
{x}{k} Encrypted message x
stages using authentication vectors (AV) and exchange messages (msg),
as shown in Table 1.
Stage 1: Initiation and Method Selection
It involves the initialization and authentication method selection. As
4.1. Security assumptions and requirements shown in Fig. 3, the SEAF initiates authentication process with the UE.
Msg1. SEAF→UE: (EAP-Request/Identity)
If the channel between the SN and HN is presumed to be secure, 1. The SEAF send Identity request to UE.
it should provide confidentiality, integrity, authenticity, and replay Msg2. UE→ SEAF: (SUCI)
protection using cryptographic primitives, keys and HMAC, according 2. The UE sends authentication request in msg2 which includes SUCI
to the standards in TS 33.501 [1]. In case where the SN-HN channel is and HNID.
not secure, it is exposed to the same attacks as the UE-SN channel [11]. Msg3. SEAF → AUSF: (SUCI, SNN)
The entities which execute the diameter protocol, as well as the 3. The SEAF receives msg2 sends SUCI and SN name to AUSF in msg3.
AKA itself, could be compromised if attacker capabilities grow. This as- Msg4. AUSF → ARPF: (SUCI, SNN)
sumption is supported by 5G characteristics that increase the attacker’s The AUSF sends msg4 to UDM/ARPF in HN. Before using the SNN,
vector [11]. It is also possible that the attacker might have the actual AUSF checks and verifies that the SEAF is authorized. When the ARPF
USIM under his or her control, in which case the attacker might have receives msg4, SUCI is de-concealed into SUPI using SIDF and chooses
access to all secret values contained in the USIM, including SUPI, K, and an authentication method.
SQN. Although EAP-AKA’ lacks cipher suite negotiation capabilities, Phase 2: The Protocol
it does have a mechanism for determining key derivation functions. The EAP-AKA’ protocol flows in a form of EAP Challenge-Response
Mutual authentication, secrecy, cryptographic binding, and session between entities as illustrated in Fig. 4.
independence are all security qualities provided by SHA-256, which are Msg5.ARPF → AUSF:EAP-AKA’ AV (RAND, AUTN,
comparable to those supplied by EAP-AKA [8]. It is also assumed that XRES, SNN, CK’ ∥ IK’, SUPI)
because SHA-256 is a pseudo-random function, an attacker will not be UDM/ARPF produces authentication vectors AV with AMF* after re-
able to deduce the pre-shared secret from any keys in any practically ceiving SUPI. RAND and SQN are generated first, followed by XRES and
feasible way. Different identifiers are used by EAP-AKA’ to identify the AUTN. Calculates CK and IK, as well as CK’ and IK’. In msg4, the ARPF
authenticating UE. Even though the protocol key strength precludes transmits EAP-Response/AKA’AV to the AUSF, signalling that EAP-AKA’
brute force assaults, it does not provide channel binding. would be utilized.
Secrecy, confidentiality, integrity, authenticity, and privacy are the Msg6. AUSF → SEAF: (RAND, AUTN, SNN)
desired security features for the EAP-AKA’ protocol [1]. The UE must When the AUSF receives msg5, it stores XRES and SUPI before sending
safely assume only SN authorized by their HN can be used for authenti- EAP-Request/AKA’-Challenge to the SEAF in msg6.
cation. The UE must use implicit key authentication and confirmation Msg7. SEAF → UE: (RAND, AUTN, ngKSI, ABBA)
to authenticate SN with the SNN. After key confirmation, a UE must In Auth-Request, msg7, the SEAF sends RAND and AUTN to the UE. The
get weak agreement on SNN with its HN. ABBA parameter must be included in this message to enable binding
In the process of AKA between UE and HN, the SN must be able down protection.
to verify the UE by authenticating SUPI. EAP-AKA’ is responsible for Msg8. UE → SEAF: (RES, MAC)
maintaining the secrecy of 𝐾𝑆𝐸𝐴𝐹 and since it is the anchor key. It When the UE receives msg7, it forwards RAND and AUTN to the USIM,
emphasizes that the same 𝐾𝑆𝐸𝐴𝐹 should never be generated twice. Pri- which checks if the AUTN may be accepted to verify the AV’s freshness.
vacy in 5G has been strongly defined, subscription privacy is concerned It generates AK and obtains SQN. Then it generates MAC2, checks to see
with subscribers’ personal data to ensure confidentiality, anonymity, (i) if MAC2 = MAC and (ii) if SQN is in the range, if SQNUE < SQNHN.
and untraceability and avoid attacks [17]. 5G has precise requirements USIM calculates RES if (i) and (ii) are the predicted responses. Finally,
on privacy, the SUPI and SQN must remain secret in presence of passive it calculates CK and IK. The UE receives RES, CK, and IK from the USIM,
attacks to avoid attack such as data leakage. Over communication then compute CK’, IK’ and returns RES with MAC2.
channels, these security features are utilized to construct and maintain Msg9. SEAF → AUSF: (RES, MAC)
4
E.K.K. Edris et al. Array 16 (2022) 100254
The SEAF transparently forwards msg8 as msg9 to AUSF. There is an SEAF sends Success message in msg11 with ngKSI and the ABBA pa-
optional exchange of further EAP messages after msg9. rameter. The UE drives EMSK (𝐾𝐴𝑈 𝑆𝐹 ) from CK’and IK’ and generates
𝐾𝑆𝐸𝐴𝐹 using the same methods as the AUSF.
Msg10. AUSF → SEAF:EAP-Success (KSEAF, SUPI)
Phase 3: Re-synchronization
When AUSF receives RES and MAC2, it verifies them by comparing If the SQN is out of sync, the re-synchronization technique is used to
RES with XRES; if the two are equal, AUSF consider the authentication update it on the HN side. This is initiated by an AUTN verification
successful and informs the UDM. If not, it sends error message to SEAF. fail, whereby the USIM lets the UE know whether it is a MAC or
Otherwise it derives EMSK (𝐾𝐴𝑈 𝑆𝐹 ) from CK’ and IK’, the calculates synchronization failure, and sends the AUTS parameter to the UE, as
𝐾𝑆𝐸𝐴𝐹 from 𝐾𝐴𝑈 𝑆𝐹 . Then sends 𝐾𝑆𝐸𝐴𝐹 to SEAF in msg10 as the anchor shown in Fig. 5.
Msg12. UE → SEAF: (Mac_failure, Synch_failure, AUTS)
key.
In msg 12 with AUTS, the UE sends mac_failure and synch_failure to
Msg11. SEAF → UE: EAP-Success (ngKSI,ABBA) SEAF.
5
E.K.K. Edris et al. Array 16 (2022) 100254
6
E.K.K. Edris et al. Array 16 (2022) 100254
Except for e2, which checks if xsqn = xor(xored sqn, ak), by the attack derivation, but the genuine attack is represented by the
xmac = f1((xsqn, xrand), ki), xmac = mac and if attack trace, which is an executable trace of the considered process.
xsqn = sqnue. If the inputs are true, a 𝑅𝐸𝑆 message is conveyed; The derivation and trace are a set of steps, inputs, and outputs on the
otherwise, a MAC_failure or synch_failure message is sent for communication channel, as well as related events.
authentication failure or re-authentication initiation.
However, because msg4 can be replayed, resulting in many e2
5.3.1. Attack derivation and trace
for a single e1, this correspondence cannot be proved directly in
The attacker 𝐼 intercepts communication between entities, imper-
ProVerif. The study also discovers that event e2, which has res as an
sonates the UE, and continues the protocol with SEAF, which completes
argument that cannot be executed before autn and rand have been
the protocol with the attacker instead of the UE. The attacker’s actions
sent, i.e. before e1. Which fails as false in ProVerif.
are depicted in Fig. 7 and concisely explained in steps below; some
content has been excluded for simplicity:
5.3. The attack against EAP-AKA’ protocol
• The event(endSEAF(x1_80)) ==> event
As illustrated in Figs. 6 and 7, the ProVerif results indicate that there (beginSEAF(x1_80)) is queried, the attacker’s goal is achie-
was an attack on the protocol. The attacker’s behaviour is represented ved, when he gets suci_4228 using attacker(suci_4228)
7
E.K.K. Edris et al. Array 16 (2022) 100254
and attacker (rand_4227) for rand_4227 together with 6.2. Security analysis 2
function SHA256 to obtain SHA256(rand_4227, x1_4230).
• The attacker’s goal is also achieved when event endSEAF(a) • Secrecy: Since SUPI’s secrecy is maintained, then this require-
is executed in session copy a_4234, SEAF completes a session ment is met. Key derivations parameters are protected in transit
with the attacker at event {57}. The injective agreement fails and storage by employing XOR and anonymity keys. F1 and
when event endSEAF(a_5801) is completed during session F* give 𝑆𝑄𝑁 privacy protection. The protocol’s confidentiality
a_5800. maintained and privacy are preserved.
• Aliveness: HN obtains the aliveness of UE from the SN, with
the UE agreeing to a non-injective agreement on 𝑆𝑁𝑁. Further-
6. Protocol security analysis more, the HN acquires fresh aliveness as a result of the injective
agreement on 𝐾𝑆𝐸𝐴𝐹 with the UE.
This section analyses the EAP-AKA’ protocol’s security properties • Weak Agreement: This is met when SN obtains non-injective
using taxonomies defined in [20,21] for security analysis 1 and 2, agreement with UE on 𝑆𝑈 𝑃 𝐼 and the key confirmation using
respectively, utilized to check formal methods outcome. 𝑆𝑁𝑁 as parameter. However, as the ProVerif results show, the
weak agreement does not hold.
• Non-injective Agreement: After 𝐾𝑆𝐸𝐴𝐹 confirmation and 𝐻𝑁𝐼𝐷
6.1. Security analysis 1
being part of SUPI, the UE gets non-injective agreement on 𝑆𝑁𝑁
with its HN. The UE receives injective agreements on 𝐾𝑆𝐸𝐴𝐹 from
• Mutual Entity Authentication: If RES = XRES, the UE is implicitly both the SN and the UE. This due to 𝐾𝑆𝐸𝐴𝐹 ’s derivation involving
authenticated to the HN and SN, as SNN is included in the suc- 𝐴𝑇 _𝑅𝐴𝑁𝐷 from HN and SNN from SN, any agreement on 𝐾𝑆𝐸𝐴𝐹
cessful authentication and 𝐾𝑆𝐸𝐴𝐹 confirmation. This is enforced between the HN and the UE ensures that the UE is attached to an
when SUPI and SNN are transmitted to the HN and are proven to authorized SN. But the SN-UE authentication fails due to a change
hold. in the channel security assumption.
• Mutual Key Authentication: The UE and HN authentication is • Injective Agreement: The injective agreement on 𝐾𝑆𝐸𝐴𝐹 between
predicated on the secrecy of 𝐾𝑆𝐸𝐴𝐹 , it is implicitly authenticated the UE and the SN is critical to the protocol’s goal, and estab-
by incorporating 𝐾𝐴𝑈 𝑆𝐹 and SNN in its derivation parameters. lishing this for various pairs of parties means 𝐾𝑆𝐸𝐴𝐹 cannot be
• Mutual Key Confirmation: This condition is enforced by a success- derived twice in the same session. As a result, using 𝐴𝑇 _𝑅𝐴𝑁𝐷
ful AKA roundtrip between the entities and with 𝐾𝑆𝐸𝐴𝐹 confirma- in the 𝐾𝑆𝐸𝐴𝐹 derivation ensures injective agreement on 𝐾𝑆𝐸𝐴𝐹
tion. between the HN and the UE. It is worth noting that any agreement
• Key Freshness: Although there is no function in ProVerif to check with HN on 𝐾𝑆𝐸𝐴𝐹 based on SNN informs the UE that SN is
key freshness, the UE validates the AUTN freshness during the trustworthy. To ensure that the session with SN was authorized by
authentication process by checking if SQNUE > SQNHN. Addi- the HN, the UE obtains an injective agreement on 𝐾𝑆𝐸𝐴𝐹 from the
tionally, every 𝐾𝑆𝐸𝐴𝐹 is linked to SN by SNN, which guarantees HN. The SN, on the other hand, is unable to gain the same level
the key freshness, 𝐾𝑆𝐸𝐴𝐹 from prior sessions cannot be reused in of trust from the UE since the SN-UE injective agreement does not
new sessions. occur.
• Unknown-Key Share: In ProVerif, the reachability property is
It must be considered that key K could be leaked through eavesdrop-
utilized to check for aliveness. This attack is prevented by the
ping on the communication channel, hacking the USIM card, an insider
entities’ identity and key binding. SUPI, HNID and SNN in the
attack via the USIM vendor, mobile provider or side channels [11]. This
derivation of 𝐾𝑆𝐸𝐴𝐹 , and the dependence on a preshared key K would allow an attacker to impersonate a user to the SN, compromising
between UE and HN also prove this condition. Moreover, 𝐾𝑆𝐸𝐴𝐹 the UE’s privacy. Misuse of keys, on the other hand, could cause the SN
is only provided to SEAF after AUSF has verified the RES and to send traffic on behalf of the UE. However, knowing the 𝐾𝑆𝐸𝐴𝐹 es-
MAC2. tablished in one session is not enough to derive 𝐾𝑆𝐸𝐴𝐹 from a previous
• Key Compromise Impersonation Resilience: 𝐾𝑆𝐸𝐴𝐹 is implicitly session or a future session in 5G. The network name binding in the EAP-
authenticated and stays a secret. However, even if the attacker AKA’ protocol can also help to mitigate some of the attacks that affect
discovers 𝐾𝑆𝐸𝐴𝐹 keys used in all previous sessions and the key the old EAP-AKA protocol, such as privacy attacks, but its configuration
K material is compromised, the current session remains confi- should not be based on the location of where a request originates
dential. It does not, however, hold for forward secrecy or post- unless the location information can be confirmed using cryptographic
compromise secrecy. EAP-AKA’ fails to meet these standards be- methods. In case, the SN requests a large number of authentication
cause knowing key K allows an attacker to deduce all previous runs for a UE from a HN to induce a DoS, resynchronization and
and future keys. tracking/monitoring mechanisms should prevent this type of attack by
limiting the number of authentication tries [8].
8
E.K.K. Edris et al. Array 16 (2022) 100254
9
E.K.K. Edris et al. Array 16 (2022) 100254
Table 4 Table 5
Cost description. Cost labels for the protocols.
Term Description EAP-AKA’ 5G-AKA
𝑛 message size c1 = 2s + e c1 = 2s+e
𝑚𝑖 𝑖th encryption size c2 = 3s c2 = 3s
𝑒 unitary encryption cost c3 = 3s c3 = 3s
𝑑 unitary decryption cost c4 = d c4 = d
𝑠 unitary output cost c5 = 5s + 8e c5 = 5s+7e
𝑙𝑖 label of the state c6 = 5s c6 = 5s
𝑐𝑖 cost of the label c7 = 5s c7 = 5s
c8 = 5d c8 = 4d
c9 = 2s + e c9 = s+e
c10 = 2s c10 = s
∑
transition, the cost of transmission is equal to 𝑛 ∗ 𝑠+ 𝑙𝑖=1 𝑚𝑖 ∗ 𝑒 the cost c11 = d c11 = 2s
of decryption is equal to 𝑛 ∗ 𝑑, and the terms are specified in Table 4. C12 = 2s c12 = 2s
C13 = s c13 = d
The cost 𝑐𝑖 of the protocol in relation to its label 𝑙𝑖 are presented in
Section 7.1.2. Cryptography primitives, system architecture, protocols,
and encryption algorithms such as ECC, SQN, AKA challenge, and XOR
influence the cost. from binding with process 𝑃 𝑖 to 𝑃 𝑗. As a result, it is equivalent to the
sum of all viable transition costs from 𝑃 𝑖 to 𝑃 𝑗, and rates correlate
7.1.1. Quantitative measurement with individual costs inside a transition system, as stated in [26]. A
The enhanced operational semantics are used to obtain the quan- CTMC C is represented as a directed graph, where the nodes are the
tifiable data required to generate the Continuous-time Markov chain states of C and states reachable from one another are connected by
(CTMC) process [28]. CTMC is made up of a number of states, labelled
arcs, as shown in Figs. 9 and 10. Because of this, the rates at which the
transitions in those states, and a sequence of random values, the
process switches between states can be organized in a square/generator
probabilities of which depend on the values of previous states [29].
matrix represented as . The graph’s adjacency matrix contains a
In [26], the costs are regarded as exponential distributions’ parameters,
when the transitions’ exponential distributions are calculated, the arcs representation of the CTMC for the process (𝐶𝑇 𝑀𝐶(𝑃 )). Moreover,
that share a source and a target are collapsed, resulting in the numerical the elements of 𝑄 are used to illustrate the instantaneous transition
process 𝑃 . rates [26]. The transition rate between two states 𝑃 𝑖 and 𝑃 𝑗, denoted
Additionally, the parameter rate 𝑟 is connected to a transition to by the symbol 𝑞(𝑃𝑖 , 𝑃𝑗 ), is the rate at which transitions between these
estimate the rate, or transition probabilities at which a system switches states take place using Eq. (1).
10
E.K.K. Edris et al. Array 16 (2022) 100254
Box I.
Box II.
11
E.K.K. Edris et al. Array 16 (2022) 100254
[ ]
𝑀 𝑀 𝑀 𝑀 𝑀 𝑀 𝑀 𝑀 𝑀 𝑀 𝑀 𝑀 𝑀
𝛱1 = , , , , , , , , , , , , (5)
𝑥 3𝑠 3𝑠 𝑑 𝑧 5𝑠 5𝑠 5𝑑 𝑥 2𝑠 𝑑 2𝑠 𝑠
[ ]
𝑁 𝑁 𝑁 𝑁 𝑁 𝑁 𝑁 𝑁 𝑁 𝑁 𝑁 𝑁 𝑁
𝛱2 = , , , , , , , , , , , , (6)
𝑥 3𝑠 3𝑠 𝑑 𝑦 5𝑠 5𝑠 4𝑑 𝑤 2𝑠 2𝑠 2𝑠 𝑑
EAP-AKA’ Protocol: Tables 5 and 6 illustrate the cost and transition
association, while Fig. 9 displays the transition state and labels. To
ensure that the transition system has stationary distributions and has
both finite and cyclic beginning states, the following generator matrix
𝑄1 = CTMC (EAP-AKA’) is generated, and the stationary distribution is
𝛱1 (see Box I) and Eq. (5), where 𝑀 = 30𝑠 + 10𝑒 + 7𝑑.
Where:
13𝑀
𝑀= (7)
30𝑠 + 10𝑒 + 7𝑑
5G-AKA Protocol: Tables 5 and 6 illustrate the cost and transition
association while Fig. 10 displays the status of the transition and
the labels. The following generator matrix 𝑄2 = CTMC (5G-AKA) is
generated, and the stationary distribution is 𝛱2 (see Box II) and Eq. (6),
where 𝑁 = 29𝑠 + 9𝑒 + 6𝑑.
Where:
13𝑁
𝑁= (8)
29𝑠 + 9𝑒 + 6𝑑
12
E.K.K. Edris et al. Array 16 (2022) 100254
Table 8
Cryptographic operations compute time.
Notation Description Computational
time (ms)
𝑇𝐸 execution 21.5
𝑇𝐴𝑣 authentication vector 33.5
𝑇𝐾𝐷𝐹 key generation 12.0
𝑇ℎ hash digest function 5
𝑇𝑆𝑒 symmetric encoding 4
𝑇𝑆𝑑 symmetric decoding 5.5
𝑇𝐴𝑒 asymmetric encoding 8
𝑇𝐴𝑑 asymmetric decoding 9.5
𝑇𝑉 verification 12.5
Table 9
Cryptographic primitive length/size.
Cryptographic primitive Value
Strings 32 bits
SQN 48 bits
Identity 64 bits Fig. 13. EAP-AKA’ protocol communication cost based on simulation approach.
MAC 64 bits
Nonce 128 bits
Symmetric key 128 bits
Asymmetric key 256 bits estimated times in milliseconds (ms) as illustrated in Table 8. The
RES 256 bits
variations in computational times of the protocols are shown in Fig. 12.
SHA256 256 bits
13
E.K.K. Edris et al. Array 16 (2022) 100254
Table 11
Protocols computational cost.
Protocols Time values Time (ms)
EAP-AKA’ 𝑇𝐸 + 7𝑇𝑆𝑒 + 𝑇𝐴𝑒 + 7𝑇𝑆𝑑 + 𝑇𝐴𝑑 + 1𝑇𝐴𝑣 + 8𝑇𝐾𝐷𝐹 + 12𝑇𝑉 557.2
5G-AKA 𝑇𝐸 + 6𝑇𝑆𝑒 + 𝑇𝐴𝑒 + 6𝑇𝑆𝑑 + 𝑇𝐴𝑑 + 1𝑇𝐴𝑣 + 8𝑇𝐾𝐷𝐹 + 2𝑇ℎ + 11𝑇𝑉 542.5
8. Conclusion
Data availability
References
Fig. 14. 5G-AKA protocol communication cost based on simulation approach. [1] 3GPP. Security architecture; procedures for 5G system. Technical specifica-
tion (TS), (3GPP TS 33.501 V17.4.1 (2022-01)). Third Generation Partner-
Table 12 ship Project; 2022, URL https://portal.3gpp.org/desktopmodules/Specifications/
Protocols communication cost. SpecificationDetails.aspx?specificationId=3169.
[2] Blanchet B, Smyth B, Cheval V, Sylvestre M. ProVerif 2.01: automatic crypto-
Protocol Number of Communication
graphic protocol verifier, user manual and tutorial. In: Version from. 2020, URL
messages cost (bits)
https://prosecco.gforge.inria.fr/personal/bblanche/proverif.
(𝑚) (𝑛)
[3] Zhang J, Yang L, Cao W, Wang Q. Formal analysis of 5G EAP-tls authentication
EAP-AKA’ 10 5966 protocol using ProVerif. IEEE Access 2020.
5G-AKA 10 5898 [4] Edris EKK, Aiash M, Loo J, Alhakeem MS. Formal verification of secondary
authentication protocol for 5G secondary authentication. Int J Secur Netw
2021;16(4):223–34. http://dx.doi.org/10.1504/IJSN.2021.119379.
[5] Ajit M, Sankaran S, Jain K. Formal verification of 5G EAP-aka protocol. In: 2021
takes 557.2 ms compared to 545.6 ms for 5G-AKA. However, there is 31st international telecommunication networks and applications conference.
ITNAC, 2021, p. 140–6. http://dx.doi.org/10.1109/ITNAC53136.2021.9652163.
a slight difference in messages 4, 6, 8 and 9 of the protocols.
[6] Vollbrecht JR, Aboba B, Blunk LJ, Levkowetz H, Carlson J. Extensible authenti-
Additionally, the overall communication costs are listed in Table 12. cation protocol (EAP). RFC Editor, IETF; 2004, URL https://tools.ietf.org/html/
Figs. 13 and 14 illustrate throughput and latency plot graphs that were rfc3748.
created from NS-3 simulation with almost identical graphs. Both proto- [7] Arkko J, Lehtovirta V, Eronen P. Improved extensible authentication protocol
method for 3rd generation authentication and key agreement (EAP-AKA’). RFC
cols have the same amount of messages 𝑚 = 10, EAP-AKA’ has a higher
Editor,IETF; 2009, URL https://tools.ietf.org/html/rfc5448.
communication cost than 5G-AKA i.e., 5996 𝑏𝑖𝑡𝑠 𝑛 compared to 5898 [8] Arkko J, Lehtovirta V, Torvinen V, Eronen P. Improved extensible authen-
𝑏𝑖𝑡𝑠 𝑛. 5G-AKA’ has a better performance in terms of throughput and tication protocol method for 3GPP mobile network authentication and key
latency but simulation produces comparable results due the similarity agreementsw (EAP-AKA’). Tech. rep, (9048). IETF; 2021, http://dx.doi.org/10.
17487/RFC9048, URL https://www.rfc-editor.org/info/rfc9048.
in number messages, primitives and entities used. The usage of MAC2
[9] Edris EKK, Aiash M, Loo J. An introduction of a modular framework for
and a success message in EAP-AKA’ increases the cost slightly, even securing 5G networks and beyond. Network 2022;2(3):419–39. http://dx.doi.org/
though the hash of RES is only used in 5G-AKA. 10.3390/network2030026.
14
E.K.K. Edris et al. Array 16 (2022) 100254
[10] 3GPP. 3GPP system architecture evolution (SAE) system aspects, secu- [20] Menezes AJ, Oorschot PCV, Vanstone SA. Handbook of applied cryptography.
rity aspects of non-3GPP accesses. Technical specification (TS), (3GPP Boca Raton, Florida, USA: CRC Press; 2018, Includes bibliographical references
TS 33.402 V16.0.0(2020-07)). Third Generation Partnership Project; 2020, and index. ID: alma991001301199704781.
URL https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails. [21] Lowe G. A hierarchy of authentication specifications. In: Proceedings 10th
aspx?specificationId=2297. computer security foundations workshop. IEEE; 1997, p. 31–43. http://dx.doi.
[11] Edris EKK, Aiash M, Loo J. Formal verification and analysis of primary authen- org/10.1109/CSFW.1997.596782, ID: ieee_s596782.
tication based on 5G-AKA protocol. In: The third international symposium on 5g [22] Dehnel-Wild M, Cremers C. Security vulnerability in 5G-AKA draft. Tech. rep,
emerging technologies. 5GET 2020, Paris, France: IEEE; 2020, p. 256–61. Department of Computer Science, University of Oxford; 2018.
[12] Basin D, Dreier J, Hirschi L, Radomirović S, Sasse R, Stettler V. A formal analysis [23] Engel T. Ss7: Locate. Track. Manipulate. In: Talk at 31st chaos communication
of 5G authentication. In: Proceedings of the 2018 ACM SIGSAC conference on congress. 2014.
computer and communications security. 2018, p. 1383–96. http://dx.doi.org/10. [24] RIFS G. Diameter roaming security - proposed permanent reference document.
1145/3243734.3243846. Tech. rep., GSMA; 2016.
[13] Meier S, Schmidt B, Cremers C, Basin D. The TAMARIN prover for the symbolic [25] Edris EKK, Aiash M, Loo J. Security protocol performance evaluation using
analysis of security protocols. In: Sharygina N, Veith H, editors. Computer applied Pi calculus and Markov chain based on 5G security. Comput Secur 2022,
aided verification, Vol. 8044. Berlin, Heidelberg: Springer Berlin Heidelberg; Submitted for Publication.
2013, p. 696–701. http://dx.doi.org/10.1007/978-3-642-39799-8_48, URL https: [26] Bodei C, Curti M, Degano P, Buchholtz M, Nielson F, Nielson HR, et al.
//www.research-collection.ethz.ch/handle/20.500.11850/68108. Performance evaluation of security protocols specified in Lysa. Electron Notes
[14] Armando A, Basin DA, Boichut Y, Chevalier Y, Compagna L, Cuellar JR, Theor Comput Sci 2005;112:167–89.
et al. The AVISPA tool for the automated validation of internet security [27] Abadi M, Blanchet B, Fournet C. The applied Pi calculus: Mobile val-
protocols and applications. Comput Aided Verif Proc 2005;3576:281–5, ID: ues, new names, and secure communication. J ACM 2017;65(1):1–41, ID:
wos000230755800027. hal_soai_HAL_hal_01423924v1.
[15] Cremers C, Dehnel-Wild M. Component-based formal analysis of 5G-AKA: Chan- [28] Stewart WJ. Introduction to the numerical solution of markov chains. Princeton
nel assumptions and session confusion. In: Network and distributed system University Press; 1994.
security symposium. NDSS, Internet Society; 2019. [29] Hillston J. A compositional approach to performance modelling, Vol. 12.
[16] Caixia LIU, Xinxin HU, Shuxin LIU, Wei YOU, Yu ZHAO. Security analysis of 5G Cambridge University Press; 2005.
network EAP-AKAṕrotocol based on Lowe’s taxonomy. J Electron Inf Technol [30] Bodei C, Curti M, Degano P, Buchholtz M, Nielson F, Nielson HR, et al. On
2019;41(8):1800–7. evaluating the performance of security protocols. In: International conference on
[17] van DB, Verdult R, de Ruiter J. Defeating IMSI catchers. In: Proceedings of parallel computing technologies. Springer; 2005, p. 1–15.
the 22Nd ACM SIGSAC conference on computer and communications security, [31] Nsnam. Ns-3 a discrete-event network simulator for internet systems. (NS-3.33).
Vol. 2015. 2015, p. 340–51. http://dx.doi.org/10.1145/2810103.2813615, ID: 2021.
acm2813615. [32] Mezzavilla M, Zhang M, Polese M, Ford R, Dutta S, Rangan S, et al.
[18] Koutsos A. The 5G-AKA authentication protocol privacy. In: 2019 IEEE eu- End-to-end simulation of 5G mmwave networks. IEEE Commun Surv Tutor
ropean symposium on security and privacy. IEEE; 2019, p. 464–79, ID: 2018;20(3):2237–63. http://dx.doi.org/10.1109/COMST.2018.2828880.
proquest2135414227. [33] Banerjee S, Odelu V, Das AK, Chattopadhyay S, Park Y. An efficient, anony-
[19] Enisa. Signalling security in telecom SS7/Diameter/5G. Tech. rep, Enisa; 2018, mous and robust authentication scheme for smart home environments. Sensors
URL https://www.enisa.europa.eu/publications/signalling-security-in-telecom- 2020;20(4):1215.
ss7-diameter-5g.
15