Join our Newsletter — 33% off our NHI Course
Home› Guides› FIPS 140-3 and Cryptographic Module Validation Guide: Buy,…
Guide Data Security

FIPS 140-3 and Cryptographic Module Validation Guide: Buy, Verify and Run Validated Crypto

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

"FIPS compliant" on a datasheet tells you almost nothing: what US and Canadian federal buyers, FedRAMP assessors and many regulated contracts actually require is a cryptographic module with a current FIPS 140-3 validation certificate, running in the configuration that certificate describes. The gap between those two statements is where audit findings, failed authorisations and last-minute product swaps come from. This guide explains how the Cryptographic Module Validation Program (CMVP) works, what changed with FIPS 140-3 and the 21 September 2026 move of FIPS 140-2 certificates to the Historical list, how to read a certificate and security policy, and how to run validated cryptography without falling behind on patches. It is for security architects, procurement and compliance teams, and engineers building products for federal or regulated customers.

Key takeaways

  • Validation applies to a module, not a product. A certificate covers a named module version on named operational environments; a product is only "validated" if it is, or embeds, that module and uses it for all its security-relevant cryptography.
  • FIPS 140-2 is now legacy for new systems. CMVP states that FIPS 140-2 certificates moved to the Historical list on 21 September 2026; agencies may keep using those modules in existing systems but should not put them in new ones.
  • Algorithm certificates come first. CAVP algorithm validation is a prerequisite of module validation, but a CAVP certificate alone does not satisfy FIPS 140.
  • Approved mode is a configuration you must prove. The security policy defines how the module enters its approved mode; vendor descriptions on the CMVP site are not verified by NIST and may not reflect approved-mode behaviour.
  • Patching and validation pull in different directions. FedRAMP's cryptographic module policy generally prefers removing known vulnerabilities over running a known-vulnerable validated version, provided the decision is risk-assessed and tracked.

What FIPS 140-3 and the CMVP are

FIPS 140-3, Security Requirements for Cryptographic Modules, was published on 22 March 2019 and took effect on 22 September 2019. Unlike FIPS 140-2, it does not restate the requirements itself: it adopts ISO/IEC 19790:2012 (with its 2015 corrections) for requirements and ISO/IEC 24759:2017 for test methods, and NIST modifies both through the SP 800-140 series. The CMVP is run jointly by NIST and the Canadian Centre for Cyber Security. NIST reports more than 1,000 active validated modules and more than 5,000 validated since the programme began.

A cryptographic module is the set of hardware, software or firmware that implements approved security functions inside a defined boundary. It can be a component embedded in a larger product or a complete product, such as a hardware security module (HSM).

The supporting documents

DocumentWhat it doesWhy practitioners care
SP 800-140FIPS 140-3 Derived Test Requirements, modifying ISO/IEC 24759Defines what the lab must test and what evidence the vendor must supply
SP 800-140ACMVP documentation requirementsVendor design evidence
SP 800-140B Rev. 1CMVP security policy requirementsFormat of the public security policy you will read when buying
SP 800-140C Rev. 2Approved security functionsWhich algorithms count as approved
SP 800-140D Rev. 2Approved sensitive parameter generation and establishment methodsApproved key generation, key agreement and key transport
SP 800-140EApproved authentication mechanismsHow operators authenticate to the module
SP 800-140FApproved non-invasive attack mitigation test metricsSide-channel testing metrics
Implementation Guidance (IG)Clarifications for FIPS 140-3 and the CMVP, first published September 2020Often decides edge cases such as entropy sources, key derivation and post-quantum algorithm acceptance

Security levels and what they mean in practice

FIPS 140-3 keeps four increasing, qualitative security levels. The descriptions below follow the FIPS 140-2 text, which describes the same ladder; the detailed FIPS 140-3 requirements are in ISO/IEC 19790 as modified by NIST, so check the security policy for the exact level achieved in each area. A module can be rated at different levels in different areas; the certificate shows an overall level.

LevelPhysical protectionOperator authenticationTypical module
1Production-grade components, no extra physical mechanismsNot required at this levelSoftware libraries (OpenSSL-based providers, OS crypto libraries)
2Tamper evidence: coatings, seals or pick-resistant locksRole-basedAppliances, some smart cards and tokens
3Tamper detection and response that zeroises plaintext keys and critical security parameters when covers are openedIdentity-basedNetwork HSMs, cloud HSM services
4Complete protective envelope detecting penetration from any direction, plus protection against environmental failure (temperature and voltage)Identity-basedModules for physically unprotected environments

Decision guidance: Level 1 is normal for software cryptography on general-purpose servers and is usually sufficient where a requirement simply asks for validated cryptography without naming a level. Choose Level 3 for root and issuing CA keys, payment keys, code-signing keys and any key whose theft would be catastrophic, because the protection is in the hardware rather than in server hardening. Large organisations usually run both: Level 1 libraries for bulk TLS and storage encryption, and Level 3 HSMs for a small number of high-value keys. Smaller organisations can usually meet the Level 3 need through a cloud HSM service rather than owning hardware. See the HSM Deployment and Operations Guide.

How validation works

  1. Algorithm testing (CAVP): the vendor's algorithm implementations are tested through NIST's Automated Cryptographic Validation Test System (ACVTS). Testing is black-box: CAVP generates test vectors, the vendor runs them, and ACVTS checks the outputs. The production server is used only by accredited labs.
  2. Module testing: an accredited Cryptographic and Security Testing Laboratory (CSTL), accredited under NVLAP, tests the module against FIPS 140-3 and the SP 800-140 series and writes the report.
  3. Submission and queue: the module appears on the Modules In Process (MIP) list with statuses such as Pending Review, Review, Comment Resolution and Cost Recovery. CMVP notes that a module moves from Pending Review to Review only after the lab pays the cost recovery fee. A MIP entry means the CMVP is working on it; it is not a certificate.
  4. Certificate: on validation the module goes on the Active list for five years. Interim validations, introduced on 6 June 2024 for modules submitted before 1 January 2024, are listed for two years.
  5. End of life: modules move to the Historical list when certificates age out or after programmatic transitions. Historical modules should not go into new federal systems but can be procured for legacy ones. A revoked certificate can no longer be cited at all.

The FIPS 140-2 to 140-3 transition

DateEvent (as stated by CMVP)
22 September 2019FIPS 140-3 effective
22 September 2020CMVP begins accepting FIPS 140-3 submissions
22 September 2021No new FIPS 140-2 submissions for new certificates
1 April 2022Only FIPS 140-2 reports that do not change the sunset date accepted
6 June 2024Two-year interim validations begin
21 September 2026FIPS 140-2 certificates move to the Historical list; existing systems only

Reading a certificate and security policy

Every certificate entry on the CMVP validated modules search links to the security policy and to the CAVP algorithm certificates it relies on. Read them together and check:

  • Module name and version: must match exactly what is deployed. CMVP says that if the vendor's letter does not match the entry's version, part number, release and operational environment, the vendor is not offering a validated solution.
  • Tested operational environments: software modules are tested on specific operating systems and processors. Running on a different platform is a judgement call your assessor will question; the security policy and IG define what porting is allowed.
  • Approved mode: the security policy states how the module enters approved mode (for example a configuration flag, a provider setting or a self-test sequence) and which services are approved. On Linux this usually means enabling the distribution's FIPS mode and crypto policy; see the Linux System-Wide Crypto Policies and FIPS Mode Guide.
  • Approved versus other algorithms: CMVP states that algorithms listed under "other algorithms" are not validated. An application that calls them is using unvalidated cryptography even inside a validated module.
  • Overall and per-area levels: confirm the level the requirement actually asks for, especially physical security for HSMs.
  • Status and dates: Active, Historical or Revoked, and the date it will leave the Active list.

For a product that embeds a module, CMVP advises asking the vendor for a signed letter stating that the product is or incorporates a validated module, that the module provides all the cryptographic services in the solution, and the certificate number.

FedRAMP, CMMC and contract requirements

NIST SP 800-53 Rev. 5 control SC-13 Cryptographic Protection is where most programmes anchor the requirement, with SC-8(1) for data in transit and SC-28(1) for data at rest. The FedRAMP Policy for Cryptographic Module Selection and Use (version 1.1, approved 16 January 2025) is the most practical statement of how this works in a modern cloud service:

  • Update streams versus validated module streams: a cloud service provider must state its default position in its SI-2 response: take the latest patches regardless of validation status, or only take versions that carry validation.
  • Known vulnerabilities: the policy generally prefers removing a known vulnerability over keeping a known-vulnerable validated version, after a risk assessment that considers the FIPS 199 impact level and mission impact.
  • Unvalidated modules: permitted where validation is not needed, for example an outer encryption layer over a validated inner layer; otherwise documented in a POA&M with a transition plan.
  • Inventory: modules, versions and use cases go in SSP Appendix Q; required customer settings such as FIPS mode go in the Customer Responsibility Matrix; continuous monitoring data must show complete module and version visibility.
  • Language: providers must describe FIPS status with NIST terms and avoid ambiguous phrases such as "FIPS compliant".
  • Resubmission: providers keep evidence that updated major versions were submitted to the CMVP within six months of release.

Defence contractors meet the same question through NIST SP 800-171 requirement 03.13.11 Cryptographic Protection, where Revision 3 lets the organisation define the types of cryptography; contract clauses and the CMMC assessment approach decide whether validated modules are expected. See the FedRAMP Guide and the CMMC 2.0 Level 2 Assessment Guide.

Implementing validated cryptography

  1. Inventory first: list every place cryptography protects federal or regulated data: TLS termination, storage encryption, key management, VPNs, SSH, code signing, token signing, database encryption. A cryptographic bill of materials makes this repeatable. See the Cryptographic Inventory and CBOM Guide.
  2. Map each use to a module: record the module name, version, certificate number, status and level. Treat FIPS 140-2 certificates as legacy and plan replacements.
  3. Enable approved mode in a test ring: turn on FIPS mode on a pilot set of hosts or containers and run functional and integration tests. Expect failures where software uses MD5, non-approved key sizes or unvalidated libraries bundled inside language runtimes.
  4. Fix the strays: applications that ship their own crypto library bypass the platform module. Rebuild them against the validated module or document them in the POA&M.
  5. Roll out by ring, with rollback: extend FIPS mode in stages and keep a tested way to revert a host image, since enabling it can break legacy clients that only offer non-approved cipher suites.
  6. Decide your stream policy: write down whether security patches outrank validation status, who signs off the risk, and how exceptions are tracked.
  7. Plan for post-quantum algorithms: ML-KEM (FIPS 203) and the post-quantum signatures will reach you through module updates and new certificates, so ask suppliers for their validation roadmap. See the ML-KEM Guide.

Where identity fits

Much of the cryptography in scope belongs to non-human identities: TLS private keys for workloads, mTLS client certificates, SSH host and user keys, OAuth and OIDC token-signing keys, and code-signing keys used by pipelines. Two points follow. First, the validated module must perform the signing or decryption for these keys, so a token service that signs JWTs with a language-runtime library outside the module is a gap even when the host runs in FIPS mode. Second, the highest-value machine keys, such as identity provider signing keys and certificate authority keys, are the strongest case for Level 3 hardware, with access to the HSM partition itself treated as privileged. See the mTLS Guide and the SSH Key Management Guide.

Detection and measurement

  • Coverage: percentage of in-scope cryptographic uses served by a module with an Active FIPS 140-3 certificate.
  • Legacy exposure: number of systems still relying on Historical (former FIPS 140-2) modules, trending to zero for new builds.
  • Approved mode drift: hosts in scope where FIPS mode is off, checked by configuration scanning (CM-6 Configuration Settings).
  • Non-approved algorithm use: TLS handshakes or API calls negotiating non-approved suites, taken from load balancer and application logs.
  • Patch latency versus validation: days between a cryptographic library security fix and deployment, alongside open POA&M items for unvalidated versions.

Framework mapping

FrameworkReferenceRelevance
NIST SP 800-53 Rev. 5SC-13 Cryptographic ProtectionPrimary control for using the required type of cryptography
NIST SP 800-53 Rev. 5SC-8(1), SC-28(1) Cryptographic ProtectionData in transit and at rest
NIST SP 800-53 Rev. 5SI-2 Flaw RemediationUpdate stream versus validated stream decision
NIST SP 800-53 Rev. 5CM-6 Configuration SettingsEnforcing approved mode
NIST SP 800-171 Rev. 303.13.11 Cryptographic ProtectionControlled unclassified information in contractor systems
NIST CSF 2.0PR.DS-01, PR.DS-02Protection of data at rest and in transit
ISO/IEC 27001:2022A.8.24 Use of cryptographyCryptography rules including approved algorithms and modules

Common failure patterns

  • Buying on the word "compliant": the product uses validated algorithms or an older library, not the certified module. FedRAMP now tells providers to avoid the phrase entirely.
  • Citing a MIP listing as a certificate: a module in the queue is not validated, and queue times are long. Plan delivery dates around Active certificates.
  • Validated module, unvalidated call path: the application bundles its own crypto, or uses "other algorithms" from the module, so the validated code never protects the data.
  • FIPS mode enabled once, then lost: rebuilt images, new container base images or a configuration change switch it off and nobody notices.
  • Freezing patches for the certificate: teams leave a known-vulnerable library in place to keep a certificate number, without the risk assessment and POA&M that FedRAMP expects.
  • Ignoring the September 2026 transition: new systems are designed around FIPS 140-2 certificates that are now Historical, forcing late redesign.

Practitioner checklist

  • Build an inventory of every in-scope cryptographic use with module name, version and certificate number.
  • Check each certificate's status on the CMVP search and flag every Historical or Revoked entry.
  • Read the security policy for each module and record how approved mode is enabled.
  • Obtain signed vendor letters for products that embed validated modules and match them to the CMVP entry.
  • Enable FIPS mode through a pilot ring with a documented rollback.
  • Scan continuously for FIPS mode drift and non-approved algorithm negotiation.
  • Write and approve an update stream versus validated stream policy with a POA&M process.
  • Ask suppliers for their FIPS 140-3 and post-quantum validation roadmap at each renewal.

Standards and references

Related NHI Mgmt Group resources: Encryption Buyer's Guide · Cryptographic Key Management Guide · HSM Deployment and Operations Guide · Crypto-Agility Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.