What it is
FIPS 197 is the NIST standard for the Advanced Encryption Standard. AES is a symmetric block cipher: one secret key encrypts and decrypts, and every operation uses a 128-bit block. Three key lengths are allowed: 128, 192, and 256 bits, known as AES-128, AES-192, and AES-256. AES is a fixed profile of Rijndael; other Rijndael block and key sizes are outside this standard. FIPS 197 specifies the round operations (SubBytes, ShiftRows, MixColumns, AddRoundKey), key expansion, decryption, and the round counts: 10, 12, and 14 for the three key lengths. Modes of operation, message authentication, and key management sit in companion documents. For an E/E engineer, this is the definition that a library, an HSM, or a test vector must match when it claims to implement AES.
Who it applies to
The standard applies to U.S. federal systems that use approved symmetric encryption. Vehicle type approval does not list FIPS 197 as its own compliance target. Automotive programs still use it as the normative definition of AES whenever an OEM cybersecurity specification, a chip security manual, or an AUTOSAR crypto configuration names AES-128 or AES-256. Cybersecurity engineers select it, software and BSW engineers invoke it, and hardware engineers integrate an accelerator or HSM that implements it. Suppliers show conformance with known-answer tests. The same text is the usual AES specification worldwide, in parallel with ISO/IEC 18033-3, which also specifies the algorithm.
What it covers
The document specifies the block cipher only.
| Topic | In FIPS 197 |
|---|---|
| 128-bit block | Yes |
| Keys of 128, 192, and 256 bits | Yes |
| Round function, key expansion, encrypt, decrypt | Yes |
| Modes (CBC, CTR, GCM, CCM, XTS) | No |
| CMAC and GMAC | No |
| Key generation, storage, and lifetime | No |
| Which key length a vehicle must use | No |
AES maps one 128-bit block to another under the secret key. Longer messages, integrity, and authenticated encryption depend on a mode and on rules for nonces, IVs, and tags. A requirement that says only “AES” still needs those choices written down.
How it fits with other documents
NIST SP 800-38A specifies CBC, CFB, OFB, and CTR. CMAC is in SP 800-38B, CCM in SP 800-38C, GCM and GMAC in SP 800-38D, XTS-AES in SP 800-38E, and key wrap in SP 800-38F. Key-management guidance is in the SP 800-57 series. ISO/IEC 18033-3 is the paid international specification of the same block cipher; cite it, and keep its text out of project files.
In the vehicle, AUTOSAR exposes AES through the Crypto Service Manager and a crypto driver, often on an HSM. SecOC authenticates PDUs with a MAC, commonly AES-CMAC. Secure boot, diagnostic authentication, MACsec, and TLS or IPsec on automotive Ethernet each bind AES to a mode and a key hierarchy defined outside FIPS 197. UN Regulation No. 155 and ISO/SAE 21434 require cybersecurity risk management and leave the cipher choice to the risk treatment and the OEM specification.
In practice
Fix the key length and the mode in the cybersecurity concept before implementation starts. AES-128 is the usual in-vehicle choice for SecOC and for many HSM accelerators. AES-256 is used where an OEM or a back-end profile requires it, such as TLS to off-board systems or encryption of stored software. AES-192 is specified and rarely selected. Use a maintained library or the hardware crypto engine, and run known-answer tests. Lab failures are typically a repeated nonce under GCM or CTR, a predictable CBC IV, a key stored in plain flash, an over-truncated MAC, or a receiver that decrypts without checking the authentication tag. The mode specification, the key-management plan, and the test report are what catch those errors.