Protocol for N32 Interconnect Security

Description

PRINS (Protocol for N32 Interconnect Security) is a standardized security mechanism specified in 3GPP for securing the N32 interface, which interconnects the security edge protection proxies (SEPPs) of two different public land mobile networks (PLMNs). The N32 interface is used for inter-PLMN signaling, primarily in roaming and interconnection scenarios, where network functions (NFs) like the AMF, SMF, or UDM in one PLMN need to communicate with counterparts in another PLMN. PRINS provides end-to-end protection for these signaling messages between the SEPPs, ensuring that sensitive data traversing untrusted network boundaries remains secure.

Architecturally, PRINS operates at the application layer, leveraging JSON Web Encryption (JWE) and JSON Web Signature (JWS) as defined in IETF RFCs, tailored for 3GPP's use cases. The protocol works by having the source SEPP encrypt and integrity-protect the HTTP/2-based N32 messages (using protocols like HTTP/2 with TLS for hop-by-hop security) before forwarding them to the destination SEPP. The destination SEPP then validates and decrypts the messages. PRINS supports two modes: the 'direct mode,' where a pre-shared key or certificate-based trust is established between SEPPs, and the 'indirect mode,' which may involve a security intermediary for key management. Key components include security policies negotiated via the N32-f interface, key derivation mechanisms, and algorithms for encryption (e.g., AES-GCM) and signing (e.g., ES256).

How it works: When an NF in the home PLMN sends a signaling message (e.g., a subscription update) to a visited PLMN, it reaches the home SEPP. The home SEPP applies PRINS by serializing the message into a JWE object for confidentiality and optionally wrapping it in a JWS for integrity. This protected payload is then transmitted over N32 to the visited PLMN's SEPP, which verifies the JWS (if used) and decrypts the JWE using keys established through prior security association. The decrypted message is forwarded to the target NF. This process ensures that even if the inter-PLMN link is compromised, the message content and its origin are safeguarded, preventing eavesdropping, tampering, or replay attacks.

Purpose & Motivation

PRINS was created in 3GPP Release 15 to address the security vulnerabilities inherent in inter-PLMN signaling, which became more critical with 5G's enhanced roaming capabilities and network exposure. Prior to 5G, inter-network signaling often relied on hop-by-hop security (e.g., IPsec or TLS between nodes), but this left messages exposed at intermediate points within foreign networks, risking data breaches and attacks like message injection. The motivation was to provide true end-to-end security between PLMNs, ensuring that only the intended SEPPs can access the signaling content.

The development of PRINS was driven by 5G's service-based architecture (SBA), which uses HTTP/2 APIs for NF communication, extending across network boundaries. Without PRINS, sensitive information such as subscriber identifiers, location data, or service parameters could be intercepted or altered, compromising privacy and network integrity. PRINS solves this by encrypting and signing messages at the application layer, independent of the underlying transport security, thus protecting data even if transport links are breached.

Historically, earlier mobile generations had less formalized inter-PLMN security, relying on bilateral agreements and basic encryption. PRINS introduces a standardized, scalable protocol that supports automated key management and policy negotiation via the N32-f interface, enabling seamless secure roaming in multi-vendor environments. It addresses regulatory requirements for data protection (e.g., GDPR) and enhances trust in 5G ecosystems, facilitating global interoperability while mitigating risks from increasingly sophisticated cyber threats.

Key Features

• End-to-end encryption and integrity protection for N32 signaling messages
• Uses JWE and JWS standards for application-layer security
• Supports both direct and indirect security modes with key management
• Integrates with SEPP for inter-PLMN boundary protection
• Provides replay protection and origin authentication
• Enables policy negotiation via the N32-f interface

Evolution Across Releases

Defining Specifications