|
Work item:
|
X.uc-zt-5g
|
|
Subject/title:
|
Security threats associated with use cases for applying zero trust to IMT-2020 private network deployments
|
|
Status:
|
Under study
|
|
Approval process:
|
TAP
|
|
Type of work item:
|
Recommendation
|
|
Version:
|
-
|
|
Equivalent number:
|
-
|
|
Timing:
|
2027-09 (Medium priority)
|
|
Liaison:
|
-
|
|
Supporting members:
|
-
|
|
Summary:
|
The purpose of this document is to present various use cases of application of zero trust model to IMT-2020 private network.
Zero Trust security means that no entity is trusted by default from inside or outside the network, and verification is required from every entity trying before being permitted access to resources on the network.
IMT-2020 private networks are non-public networks (NPN) that can use licensed, unlicensed, or shared spectrum. IMT-2020 private networks are meant to augment existing capabilities and introduce new possibilities that other systems are not able to support. IMT-2020 private networks support advanced applications like autonomous drones, IoT devices, and real-time data analytics, offering significant advantages in security, capacity, performance, and customization.
The typical application areas of IMT-2020 private networks includes applications for smart factory, smart e-health, and automotive car. They require ultra reliability and low latency while it requires very strong security requirement. It is necessary to identify use cases of application of zero trust model in the private IMT-2020 networks.
This work item is based on the network models defined in 3GPP. IMT-2020 and beyond for IMT-2020 private networks should enable the system owner to be able:
to have all network communications to have confidentiality and integrity protection.
to limit NF’s access to only the NF services it is authorized to access to complete its function.
to prevent network connections between NFs if either NF is in an insecure state.
to monitor and measure the integrity and security posture of all NFs.
|
|
Comment:
|
-
|
|
Reference(s):
|
|
|
Historic references:
|
|
Contact(s):
|
|
| ITU-T A.5 justification(s): |
|
|
|
|
First registration in the WP:
2025-04-16 17:53:10
|
|
Last update:
2025-04-22 17:46:52
|
