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

Glossary term · Security

KASUMI

KASUMI block cipher

Security →

KASUMI is the 3GPP 64-bit block cipher used in UMTS security to provide confidentiality and integrity for radio access, core signalling, and user-plane protection.

Introduced
R99
Where
Security
Specifications
1 specs
KASUMI Description Purpose Family Detected Changes Specifications

Description

KASUMI is a 64-bit block cipher with a 128-bit key, standardized by 3GPP in TS 35.202 for use in the security architecture of UMTS and related 3GPP systems. It was designed as a lightweight cipher for mobile terminals, base stations, and network elements that had to provide confidentiality and integrity protection over radio interfaces while remaining efficient in hardware and constrained software environments. In 3GPP terminology, KASUMI is not normally used as a raw block cipher by applications; instead it is the cryptographic core of algorithms such as f8 for ciphering and f9 for integrity, which combine the cipher with keys, sequence counters, and padding or MAC construction to protect signalling and user data.

Internally, KASUMI is an eight-round block cipher with a Feistel-like structure. The input block is divided into two halves, and each round applies a nonlinear round function to one half before combining it with the other half using XOR operations. The round function is built from three main components: FL, FL inverse, and FI. The FI function is the principal nonlinear element and uses small substitution boxes, commonly referred to as S7 and S9, together with subkey XOR, bit rotations, and internal feedback. The FL and FL inverse functions provide additional key-dependent mixing and help resist linear and differential analysis. The cipher also uses a key schedule that expands the 128-bit master key into round keys and subkeys for the FL and FI functions, ensuring that each round depends on different portions of the key.

During encryption, KASUMI processes the plaintext block in a fixed sequence of rounds, producing a 64-bit ciphertext block. Decryption is performed by reversing the round sequence and using the corresponding subkeys in reverse order. Because KASUMI is a block cipher, any data longer than 64 bits must be protected through a mode of operation or through the higher-level 3GPP algorithm definitions. In the UMTS context, the f8 and f9 algorithms define how KASUMI is applied to confidentiality and integrity inputs, including the use of a 128-bit key, a 32-bit count value, and data blocks that are formatted, padded, or combined to produce the final output. This abstraction allowed 3GPP to reuse a single cipher for multiple security services while keeping the implementation footprint manageable.

KASUMI was important because it gave 3GPP a common cryptographic primitive for 3G security. It supported the need to protect radio transmission from eavesdropping and tampering, and it helped move beyond older GSM ciphering approaches that were increasingly considered weak. Its design emphasized low gate count, small code size, and predictable latency, which were valuable for handsets and network equipment. At the same time, its 64-bit block size and the security analysis of its construction later motivated the adoption of stronger or more modern primitives for newer radio technologies. Nevertheless, KASUMI remains a historically significant part of 3GPP security and is still relevant when studying legacy UMTS systems and the evolution of mobile cryptography.

From an implementation perspective, KASUMI is attractive because its operations are based on fixed-size 16-bit words, XOR, rotations, and small S-boxes, which map well to ASICs, DSPs, and embedded processors. The eight-round structure gives a balance between security and performance. In UMTS, the cipher is used in conjunction with key derivation functions and sequence numbers to provide freshness, preventing replay attacks. The count value changes with each radio frame or packet, so the same plaintext produces different ciphertext and MACs. This is essential on an unreliable radio interface where retransmissions and mobility events are common. KASUMI also illustrates the 3GPP approach to security: a carefully specified primitive, a limited set of algorithms, and a key hierarchy that separates ciphering and integrity keys.

Purpose & Motivation

KASUMI was created to satisfy 3GPP security requirements for UMTS, where mobile networks needed to protect both voice and packet data over radio links. Earlier GSM systems relied on ciphering mechanisms that were increasingly vulnerable to known attacks and were not designed for the broader security goals of 3G. UMTS required confidentiality, integrity, and replay protection for signalling and user data, while still working on devices with limited processing power, memory, and battery capacity. A general-purpose high-performance cipher was not always practical for every handset or network element, so 3GPP selected a lightweight block cipher that could be implemented efficiently in hardware and software.

The motivation was also architectural. 3GPP wanted a single cryptographic primitive that could support different security functions through well-defined algorithms. KASUMI could be used for ciphering and integrity, and it could be combined with counters and keys to provide freshness and authentication of messages. This reduced the need for multiple independent cryptographic engines in devices. At the same time, KASUMI addressed limitations of older approaches by offering a 128-bit key and a structure intended to resist linear and differential cryptanalysis better than legacy GSM ciphers. Although later generations moved to stronger primitives, KASUMI solved the immediate problem of securing 3G radio access in a practical and standardizable way.

Technology family

Ciphering and integrity algorithms · Security

  1. Phase 1 A5/1, A5/2, A8
  2. R97 GEA
  3. R98 B1, B2
  4. R99 A5/3, GEA3, KASUMI, UEA1, UIA1
  5. Rel-7 SNOW 3G, UEA2, UIA2
  6. Rel-8 128-EEA1, 128-EEA2, 128-EIA1, 128-EIA2, EEA0, EIA0
  7. Rel-9 A5/4, GEA4
  8. Rel-11 128-EEA3, 128-EIA3, ZUC
  9. Rel-13 GEA5, GIA4, GIA5
  10. Rel-15 128-NEA1, 128-NEA2, 128-NEA3, 128-NIA1, 128-NIA2, 128-NIA3, NEA0, NIA0
  • KASUMI extended by GIA4
    “GIA4 is based on Kasumi 128, and is specified in TS 55.241 [26].” TS 43.020
  • KASUMI extended by A5/4
    “Each of these algorithms is based on the KASUMI algorithm that is specified in TS 35.202 [5].” TS 55.226
  • KASUMI extended by UEA1 (not stated verbatim in the specifications)

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 1 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

R99 introduced

TS 35.202 first specifies the KASUMI 64-bit block cipher with a 128-bit key, a Feistel structure with FL, FO and FI subfunctions, and its use as the basis of f8 and f9.

  • “KASUMI is a block cipher that produces a 64-bit output from a 64-bit input under the control of a 128-bit key.” TS 35.202 v3.1.2
  • “This part of the document contains the normative specification of the KASUMI algorithm.” TS 35.202 v3.1.2
  • “KASUMI is a block cipher that forms the heart of the 3GPP confidentiality algorithm f8, and the 3GPP integrity algorithm f9.” TS 35.202 v3.1.2

Defining Specifications

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

SpecificationTitleRelease
TS 35.202 vj00 KASUMI Algorithm Specification Rel-19 read