top of page

FIPS 140-3 Gap Analysis: What Your Lab Submission Decides Before the First Test Runs

Writer: Brian Couzens
Brian Couzens
1 day ago
5 min read
Abstract depiction of a cryptographic module undergoing structured gap analysis before laboratory submission

Cryptographic module vendors invest months of engineering effort before approaching a Cryptographic and Security Testing Laboratory for FIPS 140-3 validation. The assumption is that if the cryptography works, the validation will follow. That assumption is wrong. The gap between a module that functions correctly and a module that satisfies the Cryptographic Module Validation Program (CMVP) is a gap in documentation, boundary definition, and evidentiary rigour, not a gap in code.

A FIPS 140-3 gap analysis conducted before lab engagement identifies exactly where that evidentiary trail breaks down. The question is not whether the module encrypts. The question is whether the Security Policy, the Finite State Model, the entropy source documentation, and the cryptographic boundary specification meet the standard to which an accredited laboratory will test.

What FIPS 140-3 Actually Requires

FIPS 140-3, approved by the Secretary of Commerce in March 2019 and effective from 22 September 2019, is the current joint U.S. and Canadian standard for the validation of cryptographic modules. It superseded FIPS 140-2 in its entirety. FIPS 140-3 itself does not contain the technical module requirements; it references ISO/IEC 19790:2012 (with the 2015 Technical Corrigendum) for the security requirements and ISO/IEC 24759:2017 for the test requirements. NIST's SP 800-140 series documents the modifications, additions, and deletions that the CMVP applies to those ISO standards.

ISO/IEC 19790 specifies four security levels across eleven requirement areas: Cryptographic Module Specification, Cryptographic Module Interfaces, Roles Services and Authentication, Software/Firmware Security, Operational Environment, Physical Security, Non-Invasive Security, Security Parameter Management, Self-Tests, Life-Cycle Assurance, and Mitigation of Other Attacks. Each area is assessed independently at one of four levels, and the overall security level of the module reflects the lowest level achieved across the eleven areas.

The CMVP is administered jointly by NIST and the Canadian Centre for Cyber Security, a branch of the Communications Security Establishment. Independent testing is performed by Cryptographic and Security Testing Laboratories accredited under the National Voluntary Laboratory Accreditation Program (NVLAP). The laboratory tests; the CMVP validates. No self-attestation of compliance is accepted.

The September 2026 Deadline and Its Commercial Consequences

FIPS 140-2 certificates that remain on the CMVP Active Validation List will move to the Historical List on 21 September 2026. Modules on the Historical List may continue to operate in existing deployments, but federal agencies should not include Historical List modules in new procurements. For vendors selling hardware or software security products into the U.S. federal sector, the Canadian federal sector, or any regulated supply chain that mandates FIPS-validated cryptography, the absence of a FIPS 140-3 certificate after that date constitutes a procurement barrier.

The CMVP stopped accepting new FIPS 140-2 submissions after March 2022. Since April 2022, the programme has accepted FIPS 140-2 reports only where they did not alter the validation sunset date. The transition window is not approaching. It has arrived. Any module without a FIPS 140-3 submission already in the validation queue faces a timeline measured in months of lab engagement, review cycles, and CMVP processing, against a deadline that does not move.

Where Submissions Stall: The Three Structural Failures a FIPS 140-3 Gap Analysis Exposes

The Cryptographic Boundary Is Undefined or Misstated

ISO/IEC 19790 requires the cryptographic boundary to be specified in full, encompassing all hardware, software, and firmware components within the module. The boundary determines what is in scope for testing and what falls outside. A boundary drawn too narrowly excludes components the lab will assess. A boundary drawn too broadly exposes the module to requirements that do not apply to its intended validation level. Either error generates findings that halt the review. A gap analysis audits the boundary definition against the architectural specifications and the Security Policy to confirm they are consistent, complete, and defensible before the lab sees them.

The Security Policy and Finite State Model Are Incomplete

SP 800-140B Rev. 1 (November 2023) standardises the contents and ordering of the non-proprietary Security Policy. The Security Policy must document every approved security function, every mode of operation (normal and degraded), every role, every service, and the indicators that confirm approved operation. The Finite State Model must represent every operational state, every error state, and every transition. Where these documents are incomplete, ambiguous, or inconsistent with the module's actual behaviour, the testing laboratory will return them for correction. Each correction cycle adds weeks to the engagement. A gap analysis conducted against ISO/IEC 19790 and ISO/IEC 24759 surfaces these deficiencies before the laboratory clock starts.

Entropy Source Documentation Does Not Satisfy SP 800-90B

SP 800-90B, published in January 2018, specifies the design principles and requirements for entropy sources used by random bit generators. FIPS 140-3 modules that generate cryptographic keys must demonstrate that their entropy sources are validated through the Entropy Source Validation process. This includes documentation of the noise source, the conditioning function (if present), the health tests, and the min-entropy estimate. The August 2026 Implementation Guidance (IG D.K, Resolution 23) strengthened this requirement: from 1 January 2027 onwards, evaluation of physical noise sources at multiple operating conditions becomes mandatory, rather than a recommendation. Vendors whose entropy documentation has not been prepared to this standard face rejection at the evidence-ingestion stage. Mapping declared algorithms against the NIST approved and allowed lists, and verifying the SP 800-90B entropy source documentation, is a core deliverable of a FIPS 140-3 gap analysis.

The Post-Quantum Dimension

The August 2026 Implementation Guidance added guidance on Key Encapsulation Mechanisms (KEMs) aligned with SP 800-227, including a hybrid KEM scenario. The August 2024 IG added self-test requirements for FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA), and the September 2025 IG refined key generation checking for those algorithms. Modules that incorporate post-quantum algorithms face an expanded set of documentation and testing obligations. The CMVP validation queue now processes these submissions alongside classical algorithm validations. For organisations planning PQC readiness alongside FIPS 140-3 compliance, the gap analysis must account for these additional requirements from the outset.

Gap Analysis as a Structural Discipline

A FIPS 140-3 gap analysis is not a checklist exercise. It is a structured audit that examines three distinct artefact sets: first, the Security Policy, Finite State Model, and architectural specifications against ISO/IEC 19790:2012 and ISO/IEC 24759:2017; second, the cryptographic inventory and entropy readiness, mapping declared algorithms against the NIST approved lists and reviewing SP 800-90B documentation; and third, the gap between current documentation and what the laboratory requires for ingestion, producing a written deficiency report and a prioritised roadmap for submission to an accredited testing laboratory.

The output is not an opinion. It is a structured finding, referenced to specific clauses of the standard, that tells the engineering team specifically what must be corrected before engaging the lab. The difference between conducting this review before lab engagement and discovering these deficiencies during lab engagement is the difference between a controlled remediation and an expensive re-engagement cycle. For organisations subject to the September 2026 deadline, that difference is now measured in months, not quarters.

SITG-Consulting delivers an independent FIPS 140-3 gap analysis as a readiness review of your cryptographic module's boundary, architecture, and documentation, before you submit to an accredited testing laboratory. For organisations addressing broader cryptographic compliance requirements, SITG-Consulting also provides Quantum Trust and PQC Assurance Services, Cryptographic Agility Services, and Thematic Reviews that examine how standards intersect with operational readiness.

Comments


Need an independent assessment of your cryptographic exposure?

bottom of page