Vendors describe products as “FIPS-compliant” or “FIPS-capable”. Neither is a status in NIST’s Cryptographic Module Validation Program (CMVP). A cryptographic module holds a CMVP certificate or it does not, and NIST says the parts are not enough on their own: “a product or implementation does not meet the FIPS 140-2 or FIPS 140-3 requirements by simply implementing an approved security function and acquiring algorithm validation certificates.”
Where federal rules ask for cryptography, they ask for validated modules. In the CMVP’s words, “Non-validated cryptography is viewed as providing no protection to the information or data.”
What FIPS-validated means
Cryptography is FIPS-validated when all four of these hold:
- The module has a CMVP certificate on the Active list, where NIST keeps it for five years from validation, or two years for an interim validation.
- The version you run matches the one on the certificate, and for software and firmware so does the operational environment.
- The module runs in its approved mode, configured as its security policy describes, as our introduction to FIPS 140 explains.
- The algorithms you use are ones the certificate approves. NIST says the functions a certificate lists as “other algorithms” have “not been validated or tested through the CMVP.”
NIST issues certificates for modules. A product such as a VPN or a smart card can be a validated module itself, or it can contain one that does all of its cryptography, and NIST notes that many more products use validated modules than appear on its list.
What does not count
- An approved algorithm in a library with no module certificate. Correct AES or SHA-256, even with algorithm certificates, does not make the library a validated module.
- A “FIPS mode” the vendor cannot tie to a certificate. A setting that limits a product to approved algorithms is not a validation.
- A module in process. NIST lists modules being tested and modules under review, and says “Posting on the list does not imply guarantee of final validation.” A module counts once its certificate is issued.
- A historical certificate in a new system. NIST says federal agencies “should not include these in new systems but can be procured for legacy systems”, and every FIPS 140-2 certificate moved to the Historical List in September 2026.
- A revoked certificate. NIST says its validation “is no longer valid”.
What CMMC and FedRAMP accept
Requirement 3.13.11 of NIST SP 800-171 Rev. 2 reads: “Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.” Under the CMMC scoring rule it is worth 5 points when not implemented, and 3 when encryption is in place but not FIPS-validated. That case is the only requirement worth more than 1 point that a Conditional Level 2 status lets you carry on a POA&M, to be closed within 180 days. Our CMMC Level 2 self-check scores it both ways.
FedRAMP’s Consolidated Rules for 2026 tie the requirement to the certification class. Providers at Class B may, at Class C should, and at Class D must “use cryptographic modules or update streams of cryptographic modules with active validations under the NIST Cryptographic Module Validation Program when using cryptographic services to protect federal customer data.” An algorithm that an update stream adds, and that was never validated, falls outside the rule. Every provider must document the modules each service uses and whether each is validated, and should configure agency tenants by default to use validated modules where they are available.
FedRAMP also says FIPS 140 encryption “is only expected to protect sensitive data” and that it “no longer assumes all federal customer data and metadata is sensitive”. Providers document where they use it, so agencies can judge it against their own use of the service. For Rev5 certifications these rules apply from January 1, 2027, with a grace period to June 1, 2027, among the other Rev5 deadlines for 2027.
How to check a module or product
- Search NIST’s validated modules list by vendor or module name and open the certificate. Check that it is active and whether it was validated to FIPS 140-3 or FIPS 140-2.
- Match the version and, for software, the operational environment to what you run.
- Read the security policy: how to put the module in its approved mode, and which algorithms it approves. Check that yours are among them.
- For a product with an embedded module, ask the vendor for what NIST suggests: “a signed letter stating their application, product or module is a validated module or incorporates a validated module, the module provides all the cryptographic services in the solution, and reference the modules validation certificate number.” NIST adds: “If they do not agree, the vendor is not offering a validated solution.”
- Record each module, its certificate number and where it runs. FedRAMP asks providers for this list, and it shows where 3.13.11 is met.
How we can help
Our cryptographic inventory finds where your systems encrypt, establish keys and sign, and the libraries underneath them, and our AFIPS model maps each one to the validated module doing the work. For the algorithms a FIPS 140-3 module may use, read FIPS 140-3 approved algorithms.
Sources
- NIST, CMVP Validated Modules (opens in a new tab), read November 11, 2026: approved functions and algorithm certificates are not enough, “other algorithms”, version and environment, historical and revoked certificates, and the vendor letter.
- NIST, Cryptographic Module Validation Program (opens in a new tab): the Active list’s five and two years, and non-validated cryptography.
- NIST, CMVP Modules In Process (opens in a new tab): the lists of modules in testing and review.
- NIST, SP 800-171 Rev. 2 (opens in a new tab): requirement 3.13.11.
- 32 CFR Part 170 (opens in a new tab), sections 170.21 and 170.24: the points for 3.13.11 and the POA&M rule.
- FedRAMP, Consolidated Rules for 2026 (opens in a new tab), version 2026.11.02.01: rules CMU-CSO-UVM, CMU-CSO-CMD and CMU-CSO-CAT and their Rev5 dates.
- FedRAMP, What’s Changing in 2026 (opens in a new tab): FIPS 140 encryption for sensitive data.