8.4 Enhancements in LTE and LTE-A

In 3G there are still some security problems, as the IMSI may be sent in clear text, and the transmission of the IMEI is not protected. The user can also be enticed to camp on a fake BS (e.g. with high transmit power). Then it is out of reach of paging by its network. If encryption is disabled, which is still allowed, a man-in-the-middle attack can be played.
UMTS security enhancements have been mutual authentication, integrity keys, public algorithms, deeper encryption, and longer key length. The LTE architecture in addition is flat and separates control plane and user plane, uses eNode Bs replacing Node B/RNC, uses an all IP-network, interworking with legacy and non 3GPP networks. The characteristics of LTE security are therefore, reuse of UMTS authentication and key agreement (AKA), extended key hierarchy, possibility for longer keys, better protection for backhaul, and integrated interworking security for legacy and non 3GPP networks.

The LTE security architecture handles different sets of security features:
Network access security comprises the set of security features that provides the UEs with secure access to the EPC and to protect against various attacks on the radio link. Network domain security is the set of security features that protects against attacks on the wire line network and enables nodes to exchange signaling data und user data in a secure manner. User domain security is the set of security features that provides a mutual authentication between USIM and ME. Application domain security is the set of security features that enables applications in the UE and in the provider domain to securely exchange messages. Non 3GPP domain security is the set if features that enables the UE to securely access to the EPC via non-3GPP access networks and provides security protection on the radio access link (e.g. IEEE 802.11).
The LTE security of the network comprises LTE cellular security, LTE handover security, IMS security, eNode B security, and MTC security.

Device and network authentication are handled by authentication and key agreement. The AKA protocol is used for devices to authenticate with the carrier to gain network access. Cryptographic keys needed to encrypt calls are generated upon completion of the AKA protocol (Figure 8-5).
There are UE, eNodeB, MME and AuC (HSS). 1. The UE sends NAS Attach Request with the IMSI to the MME. 2. The MME sends Authentication Data Request with IMSI and SN_id to the AuC. 3. The AuC answers with Authentication Data Response with AUTN, XRES, RAND, and KASME 4. The MME sends NAS Authentication Request with AUTN, RAND ans KASME to the UE. 5. The US answers with NAS Authentication Response with RES. 6. The MME sends NAS SMC Confidentiality And Integrity Algorithm to the UE. 7.	The UE sends NAS Security Mode Complete to the MME. 8. The MME sends Initial context setup to the eNodeB. 9. The eNodeB sends RRC SMC Confidentiality And Integrity Algorithm to the UE. 10. The UE answers with RRC Security Mode Complete.
Figure 8-5: Authentication in LTE (AKA).

The security in the handover process for intra E-UTRAN mobility is as follows: Current eNode B and target eNode B are managed by the same MME. A new key management mechanism is designed with different ways to derive the new eNode B keys based on vertical or horizontal key derivations. After an initial access authentication, MME and UE shall derive a key KeNB and a next hop (NH) parameter from KASME. In the initial setup KeNB is derived directly from KASME and is associated with a virtual NH parameter with NH chaining counter (NCC) zero. The UE and the eNode B use KeNB to secure the communication on the air interface. In handovers, a new session key K*eNB used between UE and target eNode B is derived from either the active KeNB or from the NH parameter (Figure 8-6).
There are UE, source eNodeB, target eNodeB and MME. 1. The UE sends Measurement Report to the source eNodeB. 2. K*eNB = KDF (NHNCC, PCI, EARFCN-DL) is calculated in the source eNodeB. 3. The source eNodeB sends Handover Request with K*eNB and NCC to the target eNodeB. 4. The target eNodeB sends Handover Request Acknowledge with NCC to the source eNodeB. 5. The source eNodeB sends Handover Command to the UE. 6. K**eNB = KDF (NHNCC, PCI, EARFCN-DL) and KUPenc, KRRCint, KRRCenc are derived in the target eNodeB. 7. K*eNB, K**eNB, NH*NCC = KDF (KASME, KeNB) are derived in the UE. 8. As well as KUPenc, KRRCint, KRRCenc. 9. The UE sends Handover Confirm to the target eNodeB. 10. The target eNode B sends S1 Path Switch Request with TAI and ECGI to the MME. 11. K*eNB, NH*NCC, and update NH*NCC are derived in the MME. 12. The MME sends S1 Path Switch Request Acknowledge with NH*NCC and NCC+1 to the target eNodeB. 13. NH*NCC is stored in the target eNodeB.
Figure 8-6: Inter eNode B Handover in LTE (with KDF: key derivation function).

The mobility between E-UTRAN and UTRAN/GERAN is a little different. A handover from E-UTRAN starts with UE and MME deriving CK and IK from KASME. Upon receiving CK’||IK’ with KSI’ from MME, the target SGSN and the UE shall replace all stored parameters CK, IK, KSI with CK’, IK’, KSI’. In a handover from UTRAN/GERAN the target MME and the UE shall derive K’ASME from CK and IK or GPRS Kc received from SGSN. Target MME and UE shall derive KeNB and the corresponding NAS keys according to the key hierarchy of LTE. For mobility with non-3GPP networks several different mobility scenarios between heterogeneous access systems exist in the LTE networks. The UE, the target access network and the PCC will implement a full access authentication procedure before the UE handovers to the new access network.

The current keys are derived by two separate algorithms specified in addition to the NULL algorithm. The length in use is 128 bit but may be extended to 256 bit in the future. The confidentiality protection of NAS/AS signaling is recommended, the integrity protection is mandatory. The integrity key is derived by the algorithm EIA with input COUNT, message, direction, and bearer. It is attached to the original message and the receiver compares it with the values calculated in the receiver. The algorithms are based on SNOW 3G stream ciphers with a keystream provided by linear feedback shift registers (LFSR) and a finite state machine (FSM). It therefore differs from KASUMI used in UMTS and allows for low power consumption and low gate count implementation in hardware. Alternatively, an AES block cipher is defined as a second algorithm, and a third algorithm is based on Chinese ZUC stream cipher. The key hierarchy is deeper than in LTE: Based on the secret key K (128 bit) CK and IK will be the next level, followed by KASME (256 bit) derived from CK and IK. From KASME there are derived KNASenc and KNASint protecting NAS and KeNB. From the latter KUPint, KUPenc, KRRCint, KRRCenc for protecting UP traffic and RRC are calculated.

In LTE the backhaul shall also be protected. The S1 interface from E-UTRAN to S-GW is confidentiality protected using hardware appliances, security gateways and IP-tunneling.
In general LTE is markedly more secure than its predecessors, but a lot of the security mechanisms are only optional. A problem is also posed by the handovers to and from non-3GPP networks.
On the left is the transmitter, on the right the receiver. Each has a block EEA which has the following input: from the top COUNT, bearer, direction, and length, from the left Key. The output of each box is Key Stream Block. Thereunder is a line with plaintext block followed by XOR, cipher text block, another XOR and plain text block.
Figure 8-7: Ciphering in LTE.
Sie haben 0% der Lektion erledigt.
0%