Category: Cryptography & Encryption

FIPS 197

Also known as: FIPS 197, Advanced Encryption Standard, AES, FIPS PUB 197

Simply put

FIPS 197 is a U.S. federal standard, issued by NIST and approved by the Secretary of Commerce, that specifies the Advanced Encryption Standard (AES), an approved algorithm used to protect electronic data. It was originally approved in 2001 and is compulsory and binding on federal agencies for the purposes described in the standard. A later release updated the publication without making technical changes to the algorithm itself.

Formal definition

FIPS 197 (Advanced Encryption Standard) is a Federal Information Processing Standard maintained by NIST that specifies AES, a FIPS-approved symmetric block cipher algorithm used to protect electronic data. The Secretary of Commerce approved FIPS 197 in 2001, making it compulsory and binding on federal agencies for the purposes set out in the standard. According to the evidence, a subsequent release (dated May 9, 2023 in the cited source) updated the original 2001 publication but made no technical changes to the specified algorithm. FIPS 197 defines the AES algorithm specification itself; it is distinct from FIPS 140, which addresses cryptographic module security requirements and validation, and readers should not conflate algorithm conformance with cryptographic module validation. Practitioners should verify the current revision and any applicable approved modes against the authoritative NIST text, as details outside the algorithm specification (such as approved modes and module-level requirements) are governed by separate publications.

Why it matters

FIPS 197 defines the Advanced Encryption Standard (AES), the symmetric block cipher that has become the workhorse for protecting electronic data across federal systems and the broader private sector. Because the Secretary of Commerce approved FIPS 197 in 2001 and made it compulsory and binding on federal agencies for the purposes described in the standard, it establishes AES as an approved cryptographic algorithm that agencies can rely on when they need to protect the confidentiality of data. For compliance officers and system security managers, citing FIPS 197 is a way to point to an authoritative, government-approved algorithm specification rather than an ad hoc or proprietary encryption scheme.

A frequent and consequential mistake is to treat conformance to the FIPS 197 algorithm specification as equivalent to cryptographic module validation. FIPS 197 defines the AES algorithm itself; it does not, on its own, address the security requirements or validation of the cryptographic modules that implement AES, which are governed by the separate FIPS 140 line of publications. An organization can use AES and still fall short of module-level validation requirements that a given authorization or contract demands. Practitioners should confirm which requirement a control or clause actually imposes, because 'uses AES' and 'uses a validated cryptographic module' are not interchangeable claims.

AES has remained technically stable: the evidence indicates that a later release updated the original 2001 publication without making technical changes to the specified algorithm. That stability is useful for long-lived systems, but it should not lull practitioners into assuming the surrounding requirements are equally static. Approved modes of operation and module-level requirements are governed by separate publications and can be revised independently, so relying solely on FIPS 197 without checking the current authoritative text and any applicable modes can leave gaps.

Who it's relevant to

Compliance officers and ISSMs

Those documenting cryptographic protections for federal systems reference FIPS 197 to establish that an approved algorithm (AES) is in use. They should be careful to distinguish algorithm conformance under FIPS 197 from cryptographic module validation, which is governed by the separate FIPS 140 line, and confirm which specific requirement a control or authorization actually demands.

Government contractors and system integrators

Vendors implementing encryption in products or services delivered to federal customers rely on FIPS 197 as the authoritative specification of the AES algorithm. They should verify the current revision and any applicable approved modes against the authoritative NIST text, and not assume that using AES alone satisfies module-level validation requirements that a contract or authorization may impose.

Assessors and auditors

Evaluators verifying that systems protect electronic data with an approved algorithm should confirm both that AES is specified per FIPS 197 and, where required, that separate module validation and approved-mode requirements are met. Treating 'uses AES' as sufficient evidence, without checking the governing publications for modes and module validation, is a common gap to flag.

Authorizing officials

Officials making risk-based authorization decisions should understand that FIPS 197 addresses the AES algorithm specification and is compulsory and binding on federal agencies for the purposes described, but that it does not by itself establish cryptographic module validation or mode selection. Those aspects fall under separate publications that must be confirmed against current authoritative sources.

Inside FIPS 197

Advanced Encryption Standard (AES) Specification

FIPS 197 is the Federal Information Processing Standard issued by NIST that specifies the Advanced Encryption Standard, a symmetric block cipher approved for protecting federal information. It defines the algorithm rather than any particular product or implementation.

Block and Key Size Parameters

The standard describes AES as operating on fixed-size data blocks and supporting multiple approved key lengths. Readers should verify the exact block size and permitted key lengths against the current authoritative text of FIPS 197, as these parameters are defined precisely in the publication itself.

Algorithm Structure

FIPS 197 defines the mathematical transformations and round-based structure of the AES cipher, including the operations applied during encryption and decryption. It is a specification of the cipher's internal design, not guidance on how to deploy or configure cryptographic systems.

Relationship to Cryptographic Validation

FIPS 197 specifies the algorithm, but conformance of a specific implementation is generally assessed separately through cryptographic module and algorithm validation programs maintained by NIST. The standard itself does not confer validated status on any product.

Common questions

Answers to the questions practitioners most commonly ask about FIPS 197.

Does compliance with FIPS 197 by itself mean my system is secure or fully compliant?

No. FIPS 197 specifies the Advanced Encryption Standard (AES) algorithm, but adopting AES does not by itself make a system secure or compliant. Compliance is broader than any single algorithm and generally depends on how encryption is implemented, how keys are managed, and how the overall system meets applicable control baselines (such as those under NIST SP 800-53 or NIST SP 800-171). Selecting AES is one element of a larger cryptographic and control posture, not a substitute for it. Confirm the full set of applicable requirements against current authoritative sources.

Is choosing AES the same as having a validated cryptographic module?

No, and this is a common point of confusion. FIPS 197 defines the AES algorithm itself, while validation of a cryptographic module that implements AES is addressed under a separate framework (commonly associated with FIPS 140-series requirements and the associated validation program). Specifying AES as an algorithm is distinct from obtaining a validated module. Where validated cryptography is required, using AES without an appropriate validation may not satisfy the requirement. Verify which validation obligations apply to your environment against current official guidance.

Which publication should I cite when documenting the encryption algorithm in my system security documentation?

When the algorithm in use is AES, FIPS 197 is generally the publication that defines that algorithm and is the appropriate reference for the algorithm specification. Note that documentation for encryption typically also references related requirements governing key management and module validation, which are addressed in separate publications. Confirm the exact citation and the current revision status of the applicable standards against the official published text.

How does FIPS 197 relate to the other cryptographic requirements I need to meet for CUI or federal systems?

FIPS 197 provides the algorithm-level specification for AES, while the broader obligations for protecting information such as Controlled Unclassified Information generally come from control frameworks and requirements maintained by NIST and, for defense contexts, layered contractual and DoD requirements. In most implementations, satisfying encryption-related controls involves both selecting an approved algorithm and meeting associated module validation and key management expectations. Because scope and applicability differ across federal civilian, defense, and other environments, verify which combined requirements apply to your system.

What should an assessor look for when reviewing whether encryption meets requirements tied to AES?

An assessor generally examines more than whether AES is named. Review typically considers whether the implementation uses AES as specified, whether the cryptographic module is validated where validation is required, and whether key management practices align with applicable controls. Because assessment is distinct from authorization, findings on encryption should be evaluated within the broader assessment against the applicable baseline. Assessors should confirm the current revision of the relevant standards and any agency-specific tailoring.

Does specifying AES lock me into a particular key size or configuration?

Not inherently. FIPS 197 defines the AES algorithm and its supported key sizes, but the specific configuration appropriate for a given system generally depends on the applicable control baseline, agency tailoring, and any additional cryptographic guidance rather than on FIPS 197 alone. Because required or recommended configurations can vary and may change across revisions of the governing guidance, confirm the appropriate parameters against the current authoritative sources for your environment.

Common misconceptions

Using an AES implementation automatically means a system is FIPS-validated.

FIPS 197 specifies the AES algorithm, but simply implementing AES does not equate to formal validation. Validation of a cryptographic module or algorithm implementation is generally handled through separate NIST validation programs (such as those associated with FIPS 140), which readers should confirm against current authoritative sources. Implementing the algorithm and achieving validated status are distinct.

FIPS 197 and FIPS 140 are interchangeable or cover the same thing.

FIPS 197 defines the AES algorithm specification, whereas FIPS 140 addresses security requirements for cryptographic modules more broadly. They are separate standards issued by NIST serving different purposes, and compliance with one does not by itself satisfy the other.

Deploying AES per FIPS 197 makes a system secure.

Compliance with an algorithm standard is not the same as security. Effective protection depends on correct implementation, appropriate key management, secure configuration, and the surrounding system controls. FIPS 197 governs the cipher specification, not the operational security of a deployment.

Best practices

Confirm the exact block size, approved key lengths, and algorithm parameters against the current authoritative text of FIPS 197 rather than relying on secondary summaries.

Distinguish algorithm conformance under FIPS 197 from formal cryptographic module or algorithm validation, and verify validated status through the applicable NIST validation programs where required.

Do not treat implementation of AES as sufficient for security; pair it with sound key management, secure configuration, and the broader controls applicable to your system's categorization.

Verify how AES usage maps to the specific requirements applicable to your environment, since obligations differ across federal civilian systems under FISMA, DoD systems under the RMF, and systems handling CUI or classified information.

Check whether agency-specific tailoring or supplementary guidance imposes additional cryptographic requirements beyond the FIPS 197 algorithm specification.

Re-verify against current official NIST publications when planning or renewing implementations, as approved algorithm parameters and related validation requirements can change across revisions.