NIA

New radio Integrity Algorithm

Security →
Introduced in Rel-15

NIA is the standardized suite of cryptographic algorithms that provides integrity protection for 5G signaling and user data, ensuring it is not tampered with during transmission.

Category
Security
Introduced
Rel-15
Where
Security
Specifications
1 specs
NIA Description Purpose Related Classification Detected Changes Specifications

Description

The New radio Integrity Algorithm (NIA) is a core component of the 5G security architecture, defined in 3GPP specification 33.501. It provides integrity protection for both the control plane (signaling) and user plane (data) traffic over the air interface between the User Equipment (UE) and the gNodeB (gNB). Integrity protection is a fundamental security service that guarantees the received data has not been altered, deleted, replayed, or inserted by an unauthorized party during transmission. The NIA suite is designed to work in conjunction with the New radio Encryption Algorithm (NEA) for confidentiality, forming a comprehensive cryptographic protection layer for 5G NR.

NIA operates within the Packet Data Convergence Protocol (PDCP) layer in the radio protocol stack. For each data packet, the transmitting entity (UE or gNB) calculates a Message Authentication Code (MAC-I) using the integrity algorithm, the integrity key (K~RRCint~ for signaling or K~UPint~ for user data), a count value (PDCP COUNT), the bearer identity, and the direction of transmission (uplink/downlink). This MAC-I is appended to the PDCP Protocol Data Unit (PDU) before transmission. The receiving entity independently recalculates the MAC-I using the same inputs and the received data. It then compares the calculated value (XMAC-I) with the received MAC-I. If they match, the data's integrity is verified; if not, the packet is discarded, and a security failure procedure may be initiated.

The NIA suite is not a single algorithm but a family, allowing for algorithm agility. The initial set in Release 15 included NIA0, NIA1, and NIA2. NIA0 is the 'null' integrity algorithm, providing no protection and used only in specific, predefined exceptional cases. NIA1 is based on the SNOW 3G stream cipher, a carry-over from 3G and 4G security for backward compatibility and migration. NIA2 is based on the AES-CTR mode using a 128-bit key, offering strong, modern cryptographic protection. The selection of which specific NIA algorithm to use for a connection is negotiated during the security mode command procedure between the UE and the Access and Mobility Management Function (AMF) in the core network, based on the security capabilities advertised by the UE and the network's security policy.

This integrity mechanism is crucial for preventing attacks such as message forgery, replay attacks, and man-in-the-middle manipulations. It protects critical signaling procedures like attachment, handover, and session management, ensuring the network's control over the UE is secure. For user data, it guarantees that the application data received is exactly what was sent, which is vital for services requiring high data assurance. The separation of integrity keys for control and user planes (K~RRCint~ and K~UPint~) provides additional security isolation. The integrity protection is applied end-to-end between the UE and the gNB on the radio link, which is the most vulnerable segment of the connection.

Purpose & Motivation

The primary purpose of NIA is to provide a standardized, robust, and future-proof mechanism for data integrity protection in the 5G system. As mobile networks evolved to 5G, supporting a vast array of new services like massive IoT, ultra-reliable low-latency communications (URLLC), and enhanced mobile broadband (eMBB), the threat landscape expanded significantly. Previous generations had integrity protection (e.g., EIA in LTE), but 5G required algorithms that could meet higher performance demands for latency and throughput while resisting more sophisticated cryptographic attacks. The creation of a new suite of algorithms under the 'NIA' umbrella was motivated by the need for algorithm agility—the ability to introduce new, stronger algorithms over time without overhauling the entire security architecture, thereby responding to advances in cryptanalysis and computational power.

Another key motivation was to address specific vulnerabilities identified in previous systems. For instance, in LTE, integrity protection was mandatory for signaling but optional for user plane data. This left user data vulnerable to certain over-the-air attacks in many deployments. 3GPP made a conscious decision in 5G to mandate integrity protection for the user plane by default, although it can be disabled by the network operator for specific Data Radio Bearers (DRBs) if needed for performance reasons (using NIA0). This shift significantly enhances the baseline security posture. The design also explicitly separates the cryptographic chains for integrity and confidentiality, preventing potential weaknesses in one algorithm from compromising the other service.

Furthermore, the development of NIA was part of a holistic 5G security redesign that included home control and enhanced key hierarchy. The integrity keys are derived from a root key in the home network, ensuring that even in roaming scenarios, the integrity of the connection is anchored to the subscriber's home operator. This addresses concerns about visited network security. By standardizing a clear set of algorithms (NIA1, NIA2) and a clear null algorithm (NIA0), 3GPP ensures global interoperability while giving operators the tools to deploy security appropriate to their risk assessment and the requirements of different network slices.

Classification

Part ofMAC-I
Related approachesNEA

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (18 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 11 changes

In Release 15, the NIA (New radio Integrity Algorithm) function introduced mandatory support for user plane integrity protection between the UE and gNB, using the defined algorithms NIA0, 128-NIA1, and 128-NIA2. This release also specified that integrity protection for RRC and NAS signalling is mandatory, with NIA0 being implemented but generally not used except for specific cases like unauthenticated emergency calls. Furthermore, it established that the activation of user plane integrity protection is based on an explicit indication from the gNB.

  • CR for Clause Security algorithm selection, key establishment and security mode command procedure TS 33.501CR0053
  • Clarifications to Annex D.3 Integrity algorithms TS 33.501CR0217
  • Clause 6.7.3.2 - Modification on algorithm selection during N2 handover TS 33.501CR0239
  • Deletion of Editor Note in Annex D.2.1 Ciphering algorithm TS 33.501CR0260
  • Algorithm Negotiation for Unauthenticated UEs in LSM TS 33.501CR0270
  • Correction to Clause 5.11.2 Requirements for algorithm selection TS 33.501CR0336

+ 5 more changes

Rel-16 3 changes

In Release 16, the new radio integrity algorithm (NIA) function was enhanced to mandate UE support for user plane integrity protection with the gNB and to specify its activation based on network indication. It also introduced the requirement for integrity protection enforcement specifically for gPTP messages within the user plane. Furthermore, clarifications were provided for the integrity protection mechanism used for the Steering of Roaming (SoR) procedure.

  • Update to User Plane Integrity Protection TS 33.501CR0852
  • Clarifications to SoR integrity protection mechanism TS 33.501CR0944
  • UP integrity enforcement for gPTP messages TS 33.501CR0771
Rel-17 2 changes

In Release 17, the enhancements for the New Radio Integrity Algorithm (NIA) function specifically introduced procedures for User Plane Integrity Protection Policy Handling during interworking handovers from EPS to 5GS. Furthermore, the release defined mechanisms for performing an integrity check during a specific context transfer scenario, ensuring security continuity. These additions built upon the existing mandatory integrity protection for RRC and NAS signalling and the optional integrity protection for user plane data.

  • User Plane Integrity Protection Policy Handling in IW handover from EPS to 5GS TS 33.501CR1253
  • Integrity check during context transfer scenario 1 TS 33.501CR1210
Rel-19 2 changes

In Release 19, the NIA function was enhanced to ensure the Access and Mobility Management Function (AMF) selects a New Radio integrity algorithm that is actually supported by the User Equipment (UE). Additionally, clarifications were made to the text governing the Access Stratum (AS) algorithm selection process for integrity protection.

  • Ensuring the AMF selects an algorithm supported by the UE TS 33.501CR2172
  • Clarifications for the AS algorithm selection text TS 33.501CR2173

Explore further

Broader topics and technologies where NIA plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 33.501 vk00 5G Security Architecture and Procedures Rel-20