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

Glossary term · Security

Security Domain

Security Domain

Security →

Security Domain is a group of users or networks sharing common security requirements and policies, whose members in MCX share a KMS and KMS certificate to enable consistent key management and policy enforcement.

Introduced
Rel-8
Where
Security
Specifications
5 specs
Also in
Services
Security Domain Description Purpose What changed Neighbours Specifications

Description

A security domain is a grouping construct that binds together entities — originally networks, later MCX users — that share common security requirements and policies. The concept appears across multiple 3GPP security specifications, including 33.203 and 33.210 for IMS and network domain security, 33.180 for MCX security, and 23.784 for MCX architecture. Its core idea is that security policy, key management, and trust relationships are most efficiently handled at the granularity of a domain rather than per-entity. Entities inside a domain trust each other according to shared rules; entities outside the domain are treated according to inter-domain agreements.

In its original network-domain sense, a security domain is a set of networks managed by a single administrative authority. Within such a domain, a consistent level of security and a consistent set of security services is applied. This underpins Network Domain Security (NDS), where security gateways protect traffic between domains using IPsec, and where the Zb interface (between security gateways) and Za interface (within a domain) are defined. The domain boundary is where security policy translation and enforcement occur, allowing each operator to manage its own security posture independently while still interoperating.

With the introduction of Mission Critical Services (MCX), the term was adapted to a user-centric meaning. In MCX, a security domain is a group of MCX users who share common security requirements and policies for their communications. Technically, users within a security domain share a Key Management Server (KMS) and a KMS certificate. The KMS is responsible for generating and distributing key material used to protect MCX media and signalling, and the shared certificate establishes a common trust anchor. Because users may belong to more than one security domain, the model supports scenarios where, for example, a public safety officer participates in both a local agency domain and a regional mutual-aid domain.

The security domain concept enables scalable key management. Rather than establishing pairwise keys between every pair of users, the domain provides a shared key management infrastructure. Group communications within a domain can leverage domain-level keys, while cross-domain communication requires explicit inter-domain key agreements. This hierarchical approach keeps key distribution tractable even in large deployments with thousands of users.

Security domains also simplify policy enforcement and auditing. Policies such as encryption algorithms, key lifetimes, and access rules can be defined once per domain and applied uniformly. Auditors can assess compliance at the domain level. In multi-tenant and federated environments, the domain boundary clarifies responsibility: each domain operator is accountable for its own KMS and certificate lifecycle, while inter-domain trust is governed by formal agreements.

Purpose & Motivation

The security domain concept exists to make security policy and key management scalable and administrable. In early network security architectures, applying security per-interface or per-node led to combinatorial complexity: every pair of communicating entities needed its own trust relationship and key material. Grouping entities into domains reduces this to a manageable number of trust relationships between domains, with simpler internal rules.

In the network domain security context, the motivation was inter-operator security. Mobile networks operated by different authorities must exchange signalling and user traffic securely. Defining each operator network as a security domain allowed standardized security gateway interfaces (Za, Zb) and a clear separation of responsibilities. Operators could adopt their own internal security measures while relying on standardized inter-domain protection.

In the MCX context, the motivation shifted to group-based mission-critical communication. Public safety users need to communicate in talkgroups and organizations, often across agencies. A user-centric security domain tied to a shared KMS and certificate provides an efficient way to distribute group keys and enforce organizational security policies. It also supports federation: users belonging to multiple domains can participate in cross-agency operations without re-architecting key management. The evolution from a network-centric to a user-centric definition reflects this broadening of scope from infrastructure security to service-level security.

What changed in its specifications

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

TS 33.180Rel-18 → Rel-19

Rel-19 adds recording admin and replay access-token claims to TS 33.180 and removes the MC user event audit and service media collection text. It also adds Annex B recommendations on client registration, authentication request handling, public key distribution, and Issuer claim verification of the access token.

Full comparison in TS 33.180 →
TS 33.203Rel-18 → Rel-19

Rel-19 adds a TS 33.203 security clause for signing and verifying third-party user identity in IMS using STIR/SHAKEN, plus security of provisioning information. It also updates Annexes H and I with new SIP algorithm values, IPsec ESP key derivation for HMAC-SHA2-256-128, and removes hmac-md5-96.

Full comparison in TS 33.203 →

Release Timeline

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-8 Initial

Initial definition in the network domain security context: a security domain comprises networks managed by a single administrative authority, within which the same level of security and usage of security services is typical.

The definition carried over unchanged.

The definition carried over unchanged.

The definition carried over unchanged.

The definition carried over unchanged.

The definition carried over unchanged.

Wording changed: the definition was reoriented from a network-centric view (networks under a single administrative authority) to a user-centric MCX view, defining a security domain as a group of MCX users sharing security requirements and policies, a KMS, and a KMS certificate, with users allowed to belong to multiple domains.

The revised MCX-oriented definition carried over unchanged.

The definition carried over unchanged.

The definition carried over unchanged.

The definition carried over unchanged.

The definition carried over unchanged.

The definition carried over unchanged.

Defining Specifications

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

SpecificationTitleRelease
TS 23.784 vg00 Discreet Listening for Mission Critical Services Rel-16 read
TS 33.180 vk10 Security of the Mission Critical Service (MCX) Rel-20 read
TS 33.203 vk00 IMS Security Features and Mechanisms Rel-20 read
TS 33.210 vk00 Network Domain Security for IP Networks Rel-20 read
TS 33.880 vf10 Security Study for Enhanced Mission Critical Services Rel-15 read