Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 33.861
Study on evolution of Cellular Internet of Things (CIoT) Security for the 5G System

V16.1.0 (Wzip)  2020/09  73 p.
Rapporteur:
Mr. Normann, Henrik Andreas
Ericsson LM

full Table of Contents for  TR 33.861  Word version:  16.1.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
0Introduction  p. 9
1Scope  p. 10
2References  p. 10
3Definitions of terms, symbols and abbreviations  p. 11
3.1Terms  p. 11
3.2Symbols  p. 11
3.3Abbreviations  p. 11
4Security aspects of the CIoT features in the 5G System  p. 12
4.1Background  p. 12
4.2High level potential security requirements  p. 12
5Key issues  p. 12
5.1Key Issue #1: Efficient frequent small data transmissions  p. 12
5.1.1Key issue details  p. 12
5.1.2Security threats  p. 12
5.1.3Potential security requirements  p. 12
5.2Key Issue #2: Integrity protection of small data  p. 12
5.2.1Key issue details  p. 12
5.2.2Security threats  p. 13
5.2.3Potential security requirements  p. 13
5.3Key Issue #3: Encryption of small data  p. 13
5.3.1Key issue details  p. 13
5.3.2Security threats  p. 13
5.3.3Potential security requirements  p. 14
5.4Key Issue #4: Signalling overload due to Malicious Applications on the UE  p. 14
5.4.1Introduction  p. 14
5.4.2Security Threats  p. 14
5.4.3Potential security requirements  p. 14
5.5Key Issue #5: gNB Protection from CIoT DoS attack  p. 14
5.5.1Key issue details  p. 14
5.5.2Security threats  p. 15
5.5.3Potential Security requirements  p. 15
5.6Key issue #6: Avoiding AS security for application security enabled UEs.  p. 15
5.6.0General  p. 15
5.6.1Potential security threat  p. 15
5.6.2Potential security requirements  p. 15
5.7Key Issue #7: Key refreshing for protection of small data  p. 16
5.7.1Key issue details  p. 16
5.7.2Security threats  p. 16
5.7.3Potential security requirements  p. 16
5.8Key Issue #8: Key and mac size for protection of small data  p. 16
5.8.1Key issue details  p. 16
5.8.2Security threats  p. 16
5.8.3Potential security requirements  p. 16
5.9Key Issue #9: Protection of NIDD interfaces  p. 17
5.9.2Security Threats  p. 17
5.9.3Potential security requirements  p. 17
5.10Key issue #10: User Plane data transmission with Connectionless signalling.  p. 17
5.10.1Description  p. 17
5.10.2Potential security threat  p. 17
5.10.3Potential security requirements  p. 18
5.11Key Issue #11: Bidding down attack for NAS based redirection between core networks  p. 18
5.11.1Key issue details  p. 18
5.11.2Security threats  p. 18
5.11.3Potential security requirements  p. 18
5.12Key Issue #12: Privacy protection of new parameters for CIoT included in NAS message  p. 19
5.12.1Key issue details  p. 19
5.12.2Security threats  p. 19
5.12.3Potential security requirements  p. 19
5.13Key Issue #13: Security Handling in RRC Connection Re-Establishment for the control plane for NB-IoT connected to 5GC  p. 19
5.13.1Key issue details  p. 19
5.13.2Security threats  p. 20
5.13.3Potential security requirements  p. 20
5.14Key issue #14: Preventing User Plane Botnet Attacks from Improper CIOT Device Usage  p. 20
5.14.1Description  p. 20
5.14.2Potential security threat  p. 20
5.14.3Potential security requirements  p. 20
5.15Key Issue #15: Protection of UE capability transfer for UEs without AS security  p. 20
5.15.1Key issue details  p. 20
5.15.2Security threats  p. 21
5.15.3Potential security requirements  p. 21
6Solutions  p. 21
6.1Solution #1: Security Solution for small data transmission via NAS signaling  p. 21
6.1.1Introduction  p. 21
6.1.2Solution details  p. 22
6.1.3Evaluation  p. 22
6.2Solution #2: Efficient integrity protection for frequent small data transmissions  p. 22
6.2.1Introduction  p. 22
6.2.2Solution details  p. 22
6.2.3Evaluation  p. 23
6.3Solution #3: Security solution for MO SMS at AMF re-allocation  p. 24
6.3.1Introduction  p. 24
6.3.2Solution details  p. 24
6.3.2.1MO SMS included in initial NAS message  p. 24
6.3.3Evaluation  p. 26
6.4Solution #4: Security solution for UL small data transfer in RRC Suspend and Resume with early data transmission (EDT)  p. 26
6.4.1Introduction  p. 26
6.4.2Solution details  p. 26
6.4.2.1UL data transmission from CM-IDLE (SUSPEND) with Early Data Transmission to old eNB  p. 26
6.4.2.2UL UP EDT from RRC SUSPEND to new eNB  p. 28
6.4.2.3Connection Suspend procedure using the Early Data Transmission (EDT) feature  p. 28
6.4.3Evaluation  p. 28
6.5Solution #5: Security solution for small data included in initial NAS signalling at mobility  p. 28
6.5.1Introduction  p. 28
6.5.2Solution details  p. 29
6.5.3Evaluation  p. 31
6.6Solution #6: Detecting and handling signalling overload due to Malicious Applications on the UE  p. 31
6.6.1Introduction  p. 31
6.6.2Solution details  p. 31
6.6.2.1Architecture  p. 31
6.6.2.2Procedures  p. 33
6.6.3Evaluation  p. 34
6.7Solution #7: Procedure for protecting gNB from RRC resume and RRC Re-establishment DoS attack  p. 34
6.7.1Introduction  p. 34
6.7.2Solution details  p. 35
6.7.3Evaluation  p. 37
6.8Solution #8: Security solution for protection of interface used by NIDD procedures  p. 37
6.8.1Introduction  p. 37
6.8.2Solution details  p. 37
6.8.3Evaluation  p. 37
6.9Solution #9: Security protection of small data at idle mobility  p. 37
6.9.1Introduction  p. 37
6.9.2Solution details  p. 38
6.9.3Evaluation  p. 39
6.10Solution #10: Security solution for small data at idle mobility using the Registration Complete message  p. 39
6.10.1Introduction  p. 39
6.10.2Solution details  p. 39
6.10.3Evaluation  p. 40
6.11Solution #11: Security-Property-Group-based Mitigation for DDoS Attack Triggered by Malicious Applications on the UE  p. 41
6.11.1Introduction  p. 41
6.11.2Solution details  p. 41
6.11.2.1Security-Property-Group assignment mechanism  p. 41
6.11.2.1.1Principle of assignment  p. 41
6.11.2.1.2Assignment Procedure  p. 42
6.11.2.2DDoS attack mitigation  p. 42
6.11.2.2.1DDoS attack on AMF/SMF  p. 42
6.11.2.2.2DDoS attack on UPF/NEF  p. 42
6.11.3Evaluation  p. 43
6.12Solution #12: Security Solution on DDoS attack mitigation  p. 43
6.12.1Introduction  p. 43
6.12.2Solution details  p. 43
6.12.2.1Architecture  p. 43
6.12.2.2Procedure  p. 43
6.12.3Evaluation  p. 44
6.13Solution #13: Security solution for small data using key refreshing  p. 45
6.13.1Introduction  p. 45
6.13.2Solution details  p. 45
6.13.2.1Support for infrequent small data transmission  p. 45
6.13.2.2Frequent small data communication  p. 45
6.13.3Evaluation  p. 45
6.14Solution #14: Privacy protection of new parameters for CIoT included in NAS messages  p. 45
6.14.1Introduction  p. 45
6.14.2Solution details  p. 45
6.14.3Evaluation  p. 46
6.15Solution #15: Efficient integrity protection for small data transmissions with immediate result  p. 46
6.15.1Introduction  p. 46
6.15.2Solution details  p. 46
6.15.2.1General  p. 46
6.15.2.2Receiver behaviour  p. 47
6.15.3Evaluation  p. 47
6.16Solution #16: Solution to Identify Misbehaving UEs  p. 48
6.16.1Introduction  p. 48
6.16.2Solution details  p. 48
6.16.3Evaluation  p. 48
6.17Solution #17: Solution to Mitigate DDoS Attack based on RAN caused by Massive Number of Misbehaving CIoT UEs  p. 48
6.17.1Introduction  p. 48
6.17.2Solution details  p. 49
6.17.2.1Architecture  p. 49
6.17.2.2Procedure  p. 49
6.17.3Evaluation  p. 50
6.18Solution #18: Security solution for UL small data transfer in RRC Suspend and Resume with early data transmission (EDT)  p. 51
6.18.1Introduction  p. 51
6.18.2Solution details  p. 51
6.18.2.1UL data transmission from CM-IDLE with Early Data Transmission  p. 51
6.18.2.2Connection Suspend procedure using the Early Data Transmission (EDT) feature  p. 52
6.18.3Evaluation  p. 52
6.19Solution #19: Solution to Mitigate DDoS Attack on AMF caused by Massive Number of Misbehaving CIoT UEs  p. 52
6.19.1Introduction  p. 52
6.19.2Solution details  p. 52
6.19.2.1Architecture  p. 52
6.19.2.2Procedure  p. 53
6.19.3Evaluation  p. 54
6.20Solution 20: RRC Connection Re-Establishment for the Control Plane for NB-IoT connected to 5GC  p. 54
6.20.1Introduction  p. 54
6.20.2Solution Details  p. 55
6.20.2.1RRC Connection Re-Establishment Procedure without KAMF Change  p. 55
6.20.2.2RRC Connection Re-Establishment Procedure with KAMF Change  p. 55
6.20.3Evaluation  p. 56
6.21Solution 21: Protection of NAS Redirection Message  p. 56
6.21.1Introduction  p. 56
6.21.2Solution Details  p. 57
6.21.2.1Procedure of Authorization for Public Key of the AMF  p. 57
6.21.2.2Procedure of Protection of NAS message  p. 58
6.21.2.3Abnormal Cases  p. 58
6.21.3Evaluation  p. 59
6.22Solution #22: Security solution for UP IP in PDCP to protect UL EDT data in Msg 3  p. 60
6.22.1Introduction  p. 60
6.22.2Solution details  p. 60
6.22.2.1UL data transmission from CM-IDLE with Early Data Transmission  p. 60
6.22.2.2Connection Suspend procedure using the Early Data Transmission (EDT) feature  p. 61
6.22.3Evaluation  p. 61
6.23Solution #23: Mitigate DDoS Attack on RAN based on RANs coordination  p. 62
6.23.1Introduction  p. 62
6.23.2Solution details  p. 62
6.23.3Evaluation  p. 62
6.24Solution #24: Using NAS security for protection of NAS Redirection message  p. 62
6.24.1Introduction  p. 62
6.24.2Solution details  p. 62
6.24.3Evaluation  p. 62
6.25Solution #25: Security solution for preventing Botnet Attacks from Improper CIOT Device Use  p. 63
6.25.1Introduction  p. 63
6.25.2Solution A details  p. 63
6.25.3Solution B details  p. 63
6.25.4Solution C details  p. 64
6.25.5Evaluation  p. 64
6.26Solution #26: Hash based UE capability protection for CP optimization only CIoT UE  p. 64
6.26.1Introduction  p. 64
6.26.2Solution details  p. 64
6.26.3Evaluation  p. 65
6.27Solution #27: Network resilience for UEs without AS security  p. 66
6.27.1Introduction  p. 66
6.27.2Solution details  p. 66
6.27.3Evaluation  p. 66
6.28Solution #28: Protection of UE capability transfer for UEs without AS security  p. 66
6.28.1Introduction  p. 66
6.28.2Solution details  p. 66
6.28.3Evaluation  p. 67
6.29Solution #29: Security solution for UE Capability Transfer for UE with no AS security.  p. 67
6.29.1Introduction  p. 67
6.29.2Solution details  p. 68
6.29.3Evaluation  p. 68
6.30Solution #30: AMF verification of the UE radio capabilities for CP optimization only CIoT UE  p. 69
6.30.1Introduction  p. 69
6.30.2Solution details  p. 69
6.30.3Evaluation  p. 70
7Conclusions  p. 70
7.1Key Issue #1: Efficient frequent small data transmissions  p. 70
7.2Key Issue 2: Integrity protection of small data  p. 70
7.3Key Issue 3: Encryption of small data  p. 70
7.4Key Issue 4: Signalling overload due to Malicious Applications on the UE  p. 70
7.5Key Issue 5: gNB Protection from CIoT DoS attack  p. 70
7.6Key Issue 6: Avoiding AS security for application security enabled UEs.  p. 70
7.7Key Issue 7: Key refreshing for protection of small data  p. 71
7.8Key Issue 8: Key and mac size for protection of small data  p. 71
7.9Key Issue 9: Protection of NIDD interfaces  p. 71
7.10Key Issue 10: User Plane data transmission with Connectionless signalling.  p. 71
7.11Key Issue 11: Bidding down attack for NAS based redirection between core networks  p. 71
7.12Key Issue 12: Privacy protection of new parameters for CIoT included in NAS message  p. 71
7.13Key Issue 13: Security Handling in RRC Connection Re-Establishment for the control plane for NB-IoT connected to 5GC  p. 71
7.14Key Issue 14: Preventing User Plane Botnet Attacks from Improper CIOT Device Usage  p. 71
$Change history  p. 72

Up   Top