Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Security

KSF

Key Server Function

Security →

KSF is the 3GPP Release 19 security entity that manages cryptographic keys for authentication and encryption in 5G networks, providing centralized key distribution and lifecycle management for vertical applications.

Introduced
Rel-19
Where
Security
Specifications
2 specs
KSF Description Purpose What changed Neighbours Specifications

Description

The Key Server Function (KSF) is a security-related functional entity introduced in 3GPP Release 19, specified in TS 33.127 (Security aspects of the Service Enabler Architecture for Verticals) and TR 33.727. It is part of the security architecture for enabling vertical industries (e.g., automotive, factory automation, energy) to use 5G networks securely. The KSF is responsible for the management and distribution of cryptographic keys used to protect communications between application servers, edge enablers, and user equipment (UEs) within a vertical domain. Its primary role is to act as a trusted anchor for key generation, storage, and distribution, ensuring that only authorized entities can access the keys needed to encrypt, decrypt, or authenticate data.

Architecturally, the KSF resides in the 5G core network or in an edge/vertical application environment, depending on deployment. It interacts with other security functions such as the Authentication Server Function (AUSF) and the Unified Data Management (UDM) for subscriber authentication, but it specifically focuses on application-layer and service-layer keys for verticals. The KSF may be deployed as part of the SEAL (Service Enabler Architecture for Verticals) framework, which provides common services (e.g., group management, location management, key management) to vertical applications. In this context, the KSF is the entity that generates, distributes, and manages keys for secure group communication, multicast, and unicast among vertical application clients.

The KSF operates by establishing security associations with entities that need keys. When a UE or application server wants to join a secure group or initiate a secure session, it authenticates to the KSF (possibly using credentials derived from the 5G primary authentication). The KSF then provides the necessary keys, often using a key hierarchy where a root key is stored in the KSF and derived keys are distributed to participants. The KSF also handles key updates, revocation, and rekeying when group membership changes or keys expire. It supports both symmetric and asymmetric key mechanisms, depending on the security requirements of the vertical application. The KSF may also interface with the network exposure function (NEF) or other core network functions to ensure authorized access.

Security is a critical requirement for vertical industries. The KSF ensures confidentiality, integrity, and authenticity of data exchanged among vertical applications. For example, in a smart factory, robots and controllers need to communicate securely; the KSF provides the keys for encrypting their messages. In V2X (vehicle-to-everything), the KSF can manage keys for vehicle-to-vehicle and vehicle-to-infrastructure communication. The KSF also supports lawful interception and key escrow if required by regulation. It must be highly available and scalable, as it may serve thousands of devices. The KSF's design in 3GPP Release 19 focuses on interoperability, so that different vendors' vertical applications can securely interoperate.

The KSF is distinct from the 5G core network's authentication and key agreement (AKA) functions, which handle network access security. Instead, the KSF handles application-layer security for vertical services. It may use the 5G network's security capabilities (e.g., derived keys from the AKA) to bootstrap trust. In Release 19, the KSF is defined as part of the SEAL key management service, and TR 33.727 studies its security threats and requirements. The KSF can be deployed in a centralized or distributed manner, and it can be integrated with edge computing platforms to provide low-latency key distribution.

In summary, the KSF is a specialized key management function that enables secure communication for vertical applications in 5G. It addresses the need for scalable, interoperable, and standards-based key management beyond traditional network security, supporting the diverse requirements of industries using 5G. Its introduction in Release 19 reflects the growing importance of vertical-specific security in 5G-Advanced networks.

Purpose & Motivation

The KSF was created to address the security needs of vertical industries using 5G networks. Traditional 3GPP security focused on network access and core network protection, but vertical applications (e.g., industrial IoT, V2X, smart grids) require secure group communication, multicast, and application-layer encryption. Before the KSF, verticals had to deploy proprietary key management systems, which lacked interoperability and were not integrated with 5G security. The KSF standardizes key management for verticals, enabling secure, multi-vendor deployments.

The problem it solves is the lack of a standardized, scalable key distribution mechanism for group-oriented services in 5G. In many vertical use cases, devices need to communicate in groups (e.g., platooning vehicles, factory robots) and require dynamic key management as groups change. The KSF provides this, leveraging 5G security anchors and SEAL architecture. It also addresses regulatory requirements for lawful interception and key escrow.

The KSF's creation was motivated by the 3GPP's broader effort to support verticals through the SEAL framework, which provides common services to vertical applications. The KSF is a key component of SEAL, ensuring that all vertical communication can be secured with standardized, interoperable key management. Its introduction in Release 19 aligns with the commercial rollout of 5G for industry and the need for robust security in critical communications.

What changed in its specifications

The latest release-to-release comparison of specifications that define KSF. Each summary describes the whole specification, not only this term.

TS 33.127Rel-18 → Rel-19

Rel-19 adds lawful interception architectures and events for IMS-HSS, 5G LAN, WebRTC, ProSe and 5G PIN. It also adds mission critical security clauses, satellite access charging aspects, and Uncrewed Aerial System interception at the NEF/UAS NF. Further additions cover AR avatar communications and NF discovery by target PLMN.

Full comparison in TS 33.127 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-19 Initial

Initial introduction of the Key Server Function (KSF) in 3GPP. Release 19 defined the KSF as part of the SEAL key management service, specifying its architecture, interfaces, and procedures in TS 33.127 and studying security threats and requirements in TR 33.727. The KSF provides standardized key management for vertical applications, enabling secure group communication and application-layer encryption.

Defining Specifications

3GPP specifications that define or reference KSF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.727 vj00 Lawful Interception with End-to-End Encryption in 5G Rel-19 read