FIPS-validated vs FIPS-compliant: what FedRAMP and CMMC accept
FIPS-compliant is not a status in NIST’s validation program. FIPS-validated means a cryptographic module holds that program’s certificate and runs in its approved mode.
Short notes from our engineers on what is changing in federal compliance.
FIPS-compliant is not a status in NIST’s validation program. FIPS-validated means a cryptographic module holds that program’s certificate and runs in its approved mode.
FedRAMP’s 2026 rules become mandatory for Rev5 on January 1, 2027. Existing certifications must follow each set of rules by its own date, and every grace period ends by February 1, 2028.
NIST lists the algorithms a FIPS 140-3 module may use in its approved mode on two web pages. Some are now limited to legacy use, and NIST plans to retire SHA-1 by 2030.
Every FIPS 140-2 certificate is now on NIST’s Historical List. Existing systems can keep their FIPS 140-2 modules if their agency accepts the risk, but FedRAMP’s 2026 rules call for active validations.
FedRAMP’s 2026 rules set a deadline for each vulnerability by class, impact, reachability and exploitability, from 12 hours to 192 days.
After the July 13, 2026 suspension, Level 1 and Level 2 contractors still owe their self-assessments and annual affirmations while a DoW task force reviews CMMC.