FIPS 140-3 — Security Requirements for Cryptographic Modules

Why does it matter?

FIPS 140 validation is the test behind every federal encryption requirement: NIST SP 800-53 control SC-13 and FedRAMP's cryptographic module rules ask for FIPS-validated modules, and CMVP's rule is that if cryptography is required it must be validated. With FIPS 140-2 certificates now historical, the module inventory of any supplier to government needs an active FIPS 140-3 certificate for new procurements.

Key benefits include:

• Four graded levels

Level 1 to Level 4 raise the requirements for physical security, authentication and tamper response so a module can match the data and environment it protects (standard, section 3 and Applications).

• One international basis

Adopting ISO/IEC 19790:2012 and 24759:2017 aligns U.S. and Canadian validation with the standard other schemes test against, limiting FIPS-specific differences to the SP 800-140 annexes.

• A public register

The CMVP Validated Modules list records each certificate, its level, approved algorithms and security policy, and the Historical and Revoked statuses that govern use.

• Fixed transition dates

CMVP stopped accepting FIPS 140-2 submissions for new certificates on April 1, 2022 and moved all FIPS 140-2 certificates to the Historical List on September 21, 2026.

• Approved functions only

Conforming modules use only Approved security functions: those in a FIPS, SP 800-140C (approved security functions) or SP 800-140D (sensitive security parameter establishment methods).

How does it work?

The standard itself is short. Section 1 explains that FIPS 140-3 supersedes FIPS 140-2 and aligns with ISO/IEC 19790:2012, with the main technical change being non-invasive physical security requirements. Section 2 names the two ISO/IEC documents as the basis, and section 3 lists the NIST Special Publications that modify them: SP 800-140 (derived test requirements, modifying ISO/IEC 24759 sections 6.1 to 6.12) and SP 800-140A to F, which modify ISO/IEC 19790 Annexes A to F on documentation, security policy, approved security functions, sensitive security parameter methods, authentication mechanisms and non-invasive attack test metrics.

The eleven requirement areas come from ISO/IEC 19790: cryptographic module specification; interfaces; roles, services and authentication; software and firmware security; operating environment; physical security; non-invasive security; sensitive security parameter management; self-tests; life-cycle assurance; and mitigation of other attacks. A module is validated at the lowest level it meets across the areas, so a vendor chooses the level the intended environment needs and documents it in the security policy that SP 800-140B requires.

Validation runs through CMVP. The vendor contracts an NVLAP-accredited CST laboratory, which tests the module and submits a report; CMVP reviews and issues the certificate, with the module listed on the Implementation Under Test and Modules In Process lists meanwhile. From June 6, 2024 CMVP offers two-year interim validations for modules submitted before January 1, 2024, and SP 800-140B Rev. 1 formatted security policies are processed automatically. Agencies choose modules from the Active list; Historical modules may remain in existing systems only, and a revoked module may not be used.

Key Elements

• Security Levels 1 to 4

Four increasing, qualitative levels covering a wide range of applications and environments; the level chosen must match the security required by the application and environment.

• Eleven requirement areas

Module specification, interfaces, roles and authentication, software/firmware security, operating environment, physical security, non-invasive security, SSP management, self-tests, life-cycle assurance and mitigation of other attacks.

• ISO/IEC 19790:2012 and 24759:2017

The security requirements and test requirements the standard adopts; the latest edition including amendments applies (section 3.1).

• SP 800-140 series

SP 800-140 derived test requirements plus 800-140A (documentation), B (security policy), C (approved security functions), D (SSP generation and establishment), E (authentication) and F (non-invasive attack mitigation metrics).

• CMVP and CST laboratories

A joint NIST and Canadian program using independent NVLAP-accredited laboratories; validated modules are accepted by federal agencies of both countries.

• Certificate life and status

Active for five years (two for interim), then Historical; FIPS 140-2 certificates all became Historical on September 21, 2026; a revoked module may not be used.

What does it cover?

FIPS 140-3 applies to all U.S. federal agencies that use cryptography-based security systems to protect sensitive information in computer and telecommunication systems, including voice systems, and to modules that departments and agencies operate or have operated for them under contract. Modules approved for classified use may be used instead. Private and commercial organizations may adopt it voluntarily, and FedRAMP requires FIPS-validated modules by reference wherever cryptography protects federal data.

What are its objectives?

FIPS 140-3 ensures that cryptography protecting federal information is implemented in modules whose security has been independently tested.

Specify the security requirements a cryptographic module must satisfy at each of four levels.

Align U.S. and Canadian validation with ISO/IEC 19790 and 24759 while keeping CMVP control of the annexes.

Validate modules through accredited laboratories and publish the results for procurement.

Require Approved security functions and documented approved modes of operation.

Retire FIPS 140-2 on a fixed schedule so new systems use FIPS 140-3 modules.

Framework in Context

FIPS 140-3 is issued under the Federal Information Security Modernization Act and 15 U.S.C. 278g-3, and NIST SP 800-53 control SC-13 requires FIPS-validated cryptography for federal systems, which FedRAMP carries into its Cryptographic Module Use rules and SSP Appendix Q. It succeeds FIPS 140-1 (1994) and FIPS 140-2 (2001, approved 2002), and the standard is reviewed at least every five years. Algorithm testing runs separately under the Cryptographic Algorithm Validation Program.

Common Framework Mappings

FIPS 140-3 mappings help organizations align cryptographic module validation, algorithm/key management, and assurance requirements with broader security controls and industry compliance regimes for procurement, audits, and regulatory acceptance.

Mapped frameworks include:

Common Criteria (ISO/IEC 15408)

Cryptographic Module Validation Program (CMVP)

ISO/IEC 19790

ISO 27001:2022

NIST 800-53 Rev.5

NIST SP 800-57

PCI DSS 4.0.1

SOC 2