AES

AES
Name	AES
Full name	Advanced Encryption Standard
Designer	Joan Daemen, Vincent Rijmen
Published	2001
Derived from	Rijndael
Key size	128, 192, 256 bits
Block size	128 bits
Structure	Substitution–permutation network
Rounds	10, 12, 14

AES is a symmetric block cipher adopted as a federal standard in 2001 that replaced older ciphers such as Data Encryption Standard. It originated from the public competition organized by National Institute of Standards and Technology and was selected for widespread use across industry, finance, and government. The algorithm derives from the cipher Rijndael designed by Joan Daemen and Vincent Rijmen and is specified for 128‑bit blocks with key lengths of 128, 192, or 256 bits.

History

AES grew out of the late 1990s effort by National Institute of Standards and Technology to find a successor to Data Encryption Standard following advances in cryptanalysis and computing exemplified by projects such as the Electronic Frontier Foundation's DES cracker. The AES competition began in 1997 with submissions from cryptographers associated with institutions like Katholieke Universiteit Leuven, Technische Universiteit Eindhoven, Université Catholique de Louvain, and companies such as Microsoft and IBM. After evaluation by panels including experts from NSA, NIST, and international researchers tied to conferences like CRYPTO and EUROCRYPT, Rijndael was announced the winner in 2000 and standardized in FIPS 197 in 2001. Subsequent adoption involved agencies such as National Security Agency and standards bodies like ISO for international harmonization.

Design and Specifications

AES is built on a substitution–permutation network influenced by earlier work including Luby–Rackoff constructions and the design principles discussed at FSE (Fast Software Encryption). The cipher operates on a 4×4 byte matrix called the state and uses operations including SubBytes, ShiftRows, MixColumns, and AddRoundKey, reflecting primitives from S-box design research and finite field arithmetic over GF(2^8). Key schedule algorithms expand user keys into round keys; variations for 128, 192, and 256‑bit keys determine rounds (10, 12, 14). The standardization document FIPS 197 specifies block layout, test vectors, and implementation considerations comparable to formats in RFC 3602 and related IPSec specifications.

Security and Cryptanalysis

AES security rests on resistance to known classes of attacks studied at venues like RSA Conference and Black Hat. While exhaustive search attacks remain impractical against full‑size AES with recommended keys, cryptanalysis research including differential and linear cryptanalysis presented at Eurocrypt and Asiacrypt has explored reduced‑round variants. Notable theoretical advances include biclique attacks reported in literature by researchers affiliated with Microsoft Research and academic groups at École Normale Supérieure and University of California, Berkeley, which marginally reduce complexity but do not threaten recommended security levels. Side‑channel analysis work from labs at University of Cambridge, Vrije Universiteit Amsterdam, and companies such as Intel and ARM Holdings has led to practical countermeasures including masking and constant‑time implementations. Standards bodies like NIST and agencies such as National Cybersecurity Center have published guidance on implementation pitfalls and mitigation strategies.

Implementations and Performance

AES has broad software and hardware implementations ranging from reference code in OpenSSL and LibreSSL to dedicated instructions in processors like those from Intel (AES-NI) and AMD. Implementations in embedded platforms are provided by vendors such as ARM Holdings with TrustZone extensions and in microcontrollers from Microchip Technology. Performance comparisons published by teams at Google and Amazon Web Services show hardware acceleration yields significant throughput improvements for modes of operation used in TLS and SSH. High-assurance implementations are produced by projects like OpenBSD and evaluated under criteria from Common Criteria and government labs including NSA's Commercial Solutions for Classified program.

Applications and Use Cases

AES is used extensively in secure communications protocols and products including Transport Layer Security, Secure Shell, IPsec, and storage encryption systems like BitLocker and FileVault. Financial systems such as those operated by SWIFT and payment standards like EMV incorporate AES in message protection and key management. Mobile ecosystems maintained by Apple Inc. and Google employ AES for device encryption, secure enclaves, and application data protection. Cloud providers including Microsoft Azure, Amazon Web Services, and Google Cloud Platform use AES for data‑at‑rest and data‑in‑transit encryption, often combined with key management services from AWS Key Management Service and Azure Key Vault.

Standards and Certification

AES is specified in federal and international standards such as FIPS 197 and ISO/IEC 18033‑3, and is referenced in protocol standards including RFC 3602, RFC 5288, and RFC 5116. Certification and compliance frameworks that mandate or recognize AES include Common Criteria, Federal Information Processing Standards, and industry standards like PCI DSS. Conformance testing is performed by laboratories accredited by bodies such as NIST's Cryptographic Module Validation Program and vendors pursue certifications from agencies like Underwriters Laboratories and national cybersecurity centers.

Category:Block ciphers