Category: NIST Standards & Publications

NIST SP 800-140 series

Also known as: SP 800-140x series, NIST SP 800-140x series

Simply put

The NIST SP 800-140 series is a set of Special Publications issued by the National Institute of Standards and Technology (NIST) that supports FIPS 140-3, the federal standard for security requirements of cryptographic modules. These documents spell out the detailed testing requirements and supplemental information used to check whether a cryptographic module meets the standard. They are the reference material that testing laboratories and validators rely on when evaluating cryptographic products.

Formal definition

The NIST SP 800-140 series is a family of NIST Special Publications that supports Federal Information Processing Standard (FIPS) Publication 140-3, Security Requirements for Cryptographic Modules. The base document, SP 800-140, specifies modifications to the Derived Test Requirements (DTR) for FIPS 140-3, while the lettered members of the series (for example, SP 800-140Br1 and SP 800-140D Rev. 2) provide supplemental and periodically updated requirements within the Cryptographic Module Validation Program (CMVP), such as CMVP-approved sensitive security parameter generation and establishment methods and guidance on transitioning cryptographic algorithms and key lengths. Practitioners should note that specific documents in the series are revised over time and are administered in connection with the CMVP; the current authoritative text and applicable revision for any given member of the series should be verified against official NIST/CSRC sources.

Why it matters

Federal agencies and many defense contractors are generally required to use cryptographic modules that have been validated under FIPS 140-3, and the SP 800-140 series is the practical mechanism that makes that validation possible. Without documented, consistent testing requirements, laboratories evaluating cryptographic products would have no common baseline, and agencies would have limited assurance that a module labeled as compliant actually meets the federal standard. The series translates the high-level security requirements of FIPS 140-3 into the detailed criteria that the Cryptographic Module Validation Program (CMVP) uses in practice.

Because the members of the series are revised on their own schedules, they also serve as the vehicle for keeping validation aligned with evolving cryptographic guidance. For example, certain documents in the series address transitioning the use of cryptographic algorithms and key lengths, and others define CMVP-approved sensitive security parameter generation and establishment methods. This matters to practitioners because a module validated against one revision may need to be reassessed as the underlying supplemental requirements change; validation is tied to the applicable revision at the time of testing rather than being a permanent status.

Who it's relevant to

Cryptographic testing laboratories and validators

Accredited laboratories rely on the SP 800-140 series as the reference material for evaluating whether a cryptographic module meets FIPS 140-3. The Derived Test Requirements and supplemental documents define the criteria testers apply, so laboratories must track which revision of each document is current when conducting an evaluation.

Cryptographic product vendors and developers

Vendors seeking CMVP validation for their modules need to understand the testing requirements and supplemental guidance in the series, including CMVP-approved methods for sensitive security parameter generation and establishment and guidance on transitioning algorithms and key lengths. Because documents are periodically updated, vendors should confirm the applicable revision against official NIST/CSRC sources rather than assuming a prior validation baseline still applies.

Compliance officers and ISSMs procuring cryptographic modules

Those responsible for selecting or approving cryptographic products need to recognize that FIPS 140-3 validation depends on the underlying SP 800-140 series requirements. A validation is tied to the applicable revision at the time of testing, so compliance personnel should not treat it as a permanent or self-updating status and should verify that a module's validation reflects current guidance for their use case.

Authorizing officials and auditors

Authorizing officials and auditors reviewing whether systems use validated cryptography benefit from understanding how the series supports FIPS 140-3 through the CMVP. This entry describes the role of the documents in the validation process; it does not cover the contractual, agency-specific, or implementation details that a reader must confirm against current official sources.

Inside NIST SP 800-140 series

Purpose and Relationship to FIPS 140-3

The NIST SP 800-140 series supports the cryptographic module validation process by specifying and modifying the requirements referenced in FIPS 140-3, the standard maintained by NIST for security requirements for cryptographic modules. The series generally works in conjunction with ISO/IEC standards that FIPS 140-3 incorporates by reference, allowing NIST to update certain requirements without revising the FIPS publication itself. Readers should verify the current revision and scope against the official NIST text.

Modular Sub-Publication Structure

The series is organized into multiple related documents (commonly identified by letter suffixes) that each address a distinct aspect of cryptographic module validation, such as security policy documentation, derived test requirements, and vendor-supplied information. Each sub-publication modifies or supplements specific annexes or clauses referenced by FIPS 140-3. The precise number, titles, and content of the sub-publications may change across revisions and should be confirmed in current official sources.

Role in the Cryptographic Module Validation Program (CMVP)

The series generally provides the detailed technical basis used within the Cryptographic Module Validation Program, which NIST operates jointly with the Canadian Centre for Cyber Security. It informs how accredited testing laboratories assess modules and how requirements are documented, but validation itself is administered through the CMVP process rather than by the SP 800-140 documents alone.

Scope Boundaries

The series addresses requirements for the validation of cryptographic modules and does not by itself constitute an authorization to operate, a system-level accreditation, or a procurement mandate. Its applicability to federal civilian, defense, or national security systems flows from other authorities (such as FISMA-related requirements or DoD policy) that call for validated cryptography; readers must confirm the governing requirement for their environment.

Common questions

Answers to the questions practitioners most commonly ask about NIST SP 800-140 series.

Does achieving FIPS 140 validation through the SP 800-140 series mean my cryptographic module is automatically approved for use on any federal or DoD system?

No. The SP 800-140 series supports the validation of cryptographic modules against the requirements of FIPS 140 (as of the applicable version), but validation is not the same as authorization to operate. A validated module addresses whether the module itself meets the specified security requirements; it does not by itself satisfy the broader system-level requirements found in frameworks such as FISMA, FedRAMP, or the DoD RMF. Additionally, a module being validated does not guarantee it is appropriate for every impact level, data type, or agency-specific tailoring. Readers should confirm applicability against current authoritative sources and any agency-specific guidance.

Is the SP 800-140 series a replacement for FIPS 140, or does it change the underlying cryptographic requirements?

The SP 800-140 series does not replace FIPS 140 and is generally understood to complement it. In most implementations, the series modifies or specifies certain annexes and supporting requirements referenced by FIPS 140 rather than establishing a new standalone standard. It should not be treated as a substitute for the governing FIPS publication maintained by NIST. Because the relationship between FIPS 140 and the 800-140 series can evolve across revisions, readers should verify the current authoritative text and version before relying on any specific mapping.

How does the SP 800-140 series fit into a validation effort for a cryptographic module?

The series is generally used as part of the validation process that references FIPS 140, providing the specifications and annex content that support how modules are tested and assessed. Organizations pursuing validation typically work within the applicable validation program processes maintained by NIST and its testing partners. Because procedures and referenced documents change across revisions, teams should confirm which version of FIPS 140 and which SP 800-140 sub-publications apply to their effort against current official sources before beginning work.

Where should I look to determine which SP 800-140 sub-publications apply to my module?

The SP 800-140 series is organized into multiple sub-publications, each addressing distinct aspects of the validation requirements referenced by FIPS 140. The applicable sub-publications depend on the nature of the module and the requirements being addressed. Because the number, scope, and revision status of these sub-publications can change, this entry does not enumerate them; readers should consult the current NIST publications directly to identify which sub-documents are relevant and in effect for their situation.

Does relying on a module validated under the SP 800-140 series mean my system is secure?

No. Using a validated cryptographic module addresses a specific set of requirements for that module, but compliance with a validation standard is not the same as overall system security. A validated module is one element within a broader security and risk-management context that includes proper implementation, configuration, key management, and continuous monitoring under the applicable framework. Readers should treat validation as a component of, not a substitute for, a complete security posture.

How should I account for revisions when documenting reliance on the SP 800-140 series?

Because the SP 800-140 series and the FIPS 140 standard it supports are subject to revision, documentation should identify the specific versions and sub-publications relied upon and note the date of reference. Requirements, referenced annexes, and validation procedures may differ across revisions, so assessment and authorization artifacts generally benefit from explicitly recording the applicable version rather than referencing the series generically. Verify the current authoritative text before finalizing any documentation.

Common misconceptions

The SP 800-140 series replaces FIPS 140-3 as the governing standard for cryptographic modules.

The SP 800-140 series does not replace FIPS 140-3; it supports and modifies specific requirements referenced by FIPS 140-3. FIPS 140-3 remains the applicable standard, and the SP 800-140 documents exist to let certain requirements be updated without reissuing the FIPS publication. The two should be read together, against their current revisions.

A module described against the SP 800-140 series is automatically validated and approved for use.

The series provides technical requirements and documentation guidance, but it is not the same as validation. A module is validated through the Cryptographic Module Validation Program via an accredited laboratory and the associated CMVP process. Meeting the documentary requirements described in the series does not by itself confer a validation certificate.

Using a module covered by this series satisfies all compliance and authorization obligations for a system.

Validated cryptography is one element of a broader compliance posture. It does not equate to overall system security, nor does it substitute for an Authority to Operate, continuous monitoring, or framework-specific obligations under FISMA, DoD RMF, or contractual requirements. Those obligations are governed by separate authorities that practitioners must confirm independently.

Best practices

Read the applicable SP 800-140 sub-publications together with the current revision of FIPS 140-3, since the series modifies requirements referenced by that standard rather than standing alone.

Verify the specific sub-publication titles, suffixes, and content against current official NIST sources before relying on them, because the series structure and requirements can change across revisions.

Confirm module validation status through the Cryptographic Module Validation Program rather than assuming that alignment with the series documentation implies a completed validation.

Trace the requirement to use validated cryptography back to the governing authority for your environment (for example FISMA-related requirements or DoD policy) to determine what actually applies to CUI, defense, or civilian systems.

Do not treat cryptographic module validation as equivalent to system security or as a substitute for an ATO, continuous monitoring, or other framework obligations.

Coordinate with accredited testing laboratories and the CMVP process early when validation is required, and document requirements consistent with the current series guidance rather than superseded versions.