Start hereDefine the boundary and agree the validation route
~56 days leftOpen step
Guide library
Certification North America

FIPS 140-3 cryptographic module validation

FIPS 140-3 CMVP validation and cryptographic certificate verification

Prepare the module, boundary and evidence for an accredited lab. Verify the exact validated module and its operating conditions before purchasing or deploying it.

Issuing authority
NIST and the Canadian Centre for Cyber Security
Timing
Agree test, submission and review timing with the accredited lab. Determine when a hardware, firmware or software change requires a different validation submission or replacement.
Reviewed
Inside this guide
4 steps · 4 templates

Who it applies to

Vendors seeking cryptographic module validation and buyers or integrators comparing module validations against a policy, contract or purchasing requirement.

What you’ll produce

A validation certificate and public security policy when approved, plus a deployment or procurement record that matches their conditions.

Compare the certificate number, version, operational environment, mode and caveats. An algorithm validation is separate from a module validation. Check the current status and sunset before relying on a certificate.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What do we need the certification to cover?
Confirm the applicable edition, sites, products or service boundary and the certification route. Budget for assessment, changes needed to pass, and maintaining certification.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

FIPS 140-3 cryptographic module validation kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Define the boundary and agree the validation route · Product security + module engineering + accredited CST lab [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • What is inside the module boundary, and which operating environments and versions will the evaluation cover?
  • How does the purchase or deployment record prove that the configuration matches the currently validated module?

Worked scenario

A procurement team evaluating an HSM asks for the certificate number and public security policy. Engineering maps the proposed hardware and firmware to the validated versions and checks caveats before approving that configuration.

What to read next

FROM THE SOURCE

Cases and numbers

CMVP active list transition · September 2026

Look up the module again when you renew

NIST’s transition schedule moved remaining FIPS 140-2 validations to the historical list on 22 September 2026. CMVP guidance addresses treatment for existing systems and leaves acquisition decisions to agencies.

What to check Save the active or historical status with the project’s purchasing rules and record the exact certificate on file.

NIST FIPS 140-3 transition schedule (opens in a new tab)

NIST fee schedule · 2026

USD 16,000–19,000NIST base report review fee for a full submission, depending on level

Ask the lab to itemise testing and review fees

NIST’s 2026 full-submission schedule ranges from USD 16,000 at Level 1 to USD 19,000 at Level 4. Extended review fees may apply. The accredited lab’s testing is a separate cost.

What to check Ask the lab which fee scenario the planned submission uses and which evidence gaps could change the quote.

NIST 2026 cost recovery fee schedule (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • Before purchase or deployment

    Verify the live certificate and security policy

    Match the exact configuration and applicable caveats to the planned environment.

    Official reference (opens in a new tab)
  • 22 September 2026

    FIPS 140-2 active-list transition

    CMVP scheduled remaining FIPS 140-2 validations to move to the historical list. Confirm policy for existing systems and the actual certificate status.

    Official reference (opens in a new tab)
  • At change or approaching sunset

    Recheck the status and change coverage

    Keep the certificate, procurement requirement and approved version together.

    Official reference (opens in a new tab)
The whole journeyabout 56 days across 4 steps
  1. 01Define the boundary and agree the validation route, Product security + module engineering + accredited CST lab, about 14 days
  2. 02Prepare the evidence and track lab review, Module engineering + Quality + lab, about 28 days
  3. 03Match the validation to the actual purchase, Procurement + security architecture + system owner, about 7 days
  4. 04Maintain the configuration and review changes, Module owner + procurement + compliance, about 7 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 4 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Define the boundary and agree the validation routeProduct security + module engineering + accredited CST labBefore test engagementSet a start dateCMVP module scope and lab briefOpen
Prepare the evidence and track lab reviewModule engineering + Quality + labBefore and during testingSet a start dateCMVP lab evidence registerOpen
Match the validation to the actual purchaseProcurement + security architecture + system ownerBefore accepting a product claim or deploymentSet a start dateCMVP certificate verification checklistOpen
Maintain the configuration and review changesModule owner + procurement + complianceBefore upgrades and at renewal reviewsSet a start dateCMVP certificate and change logOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Define the boundary and agree the validation route

    Who Product security + module engineering + accredited CST lab When Before test engagement

    Record module type, boundary, versions, intended operational environments and candidate security level. Have the lab confirm the submission approach, applicable requirements and evidence it expects.

    What to produce

    CMVP module scope and lab briefMemo

    Gather first

    • Architecture
    • Module and product versions
    • Intended environments
    • Applicable procurement requirements
    • Current CMVP manual

    How to prepare it

    1. Describe the module boundary, its interfaces, module type, versions and target environments.
    2. Review the intended level and submission approach with an accredited CST lab. Record assumptions, evidence needs, fees and expected activities.
    3. Have Product and Engineering sign the boundary and resolve any difference between what will be evaluated and what customers will receive.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional boundary
    Mylark Crypto Module is a library with an identified binary boundary. The product team records the host applications and supported deployment environments separately.
    Lab handoff
    Engineering gives the lab the release identifiers, architecture, intended environments and candidate submission route.

    Check before handing it over

    The scope is specific enough to identify what is covered and who will provide each item.

    Give the approved brief to the lab and the engineering owners of the evidence.

  2. 02

    Prepare the evidence and track lab review

    Who Module engineering + Quality + lab When Before and during testing

    Version the module and its artifacts. Give the lab the module description, relevant security evidence, build details and security policy draft. Track test findings, evidence revisions and the configuration submitted for validation.

    What to produce

    CMVP lab evidence registerSpreadsheet

    Gather first

    • Agreed lab plan
    • Versioned artifacts
    • Security policy draft
    • Design, build and test evidence
    • Review correspondence

    How to prepare it

    1. Index every evidence item with requirement, version, source file, owner and review status.
    2. Link evidence and lab feedback to the tested configuration. Track changes and their impact before replacing an artifact.
    3. Reconcile the final policy and submission identifiers with the release candidate and preserve the lab’s closeout evidence.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional evidence row
    The release artifact is identified by version and digest. Engineering supplies the build record and records the lab’s evidence request against that artifact.
    Scope question
    A second platform is planned after submission. The owner asks the lab how and when to handle that change.

    Check before handing it over

    The lab can reproduce the version history and confirm which artifacts the evidence supports.

    Give Quality and release owners the exact configuration submitted and any open constraints.

  3. 03

    Match the validation to the actual purchase

    Who Procurement + security architecture + system owner When Before accepting a product claim or deployment

    Look up the exact certificate. Read the public security policy and confirm module version, boundaries, supported environments, approved mode and caveats. Save a dated verification tied to the intended configuration.

    What to produce

    CMVP certificate verification checklistChecklist

    Gather first

    • Exact certificate number
    • Public security policy
    • Quoted model or software version
    • Deployment configuration
    • Purchasing requirements

    How to prepare it

    1. Look up the certificate and save current status, sunset, vendor and title. Retrieve the public security policy.
    2. Compare the proposed model, software or firmware version, environment and operating mode to the published validation and caveats.
    3. Ask for dated evidence of any claimed coverage or upgrade. Obtain a signed procurement or deployment decision tied to the exact configuration.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional quote check
    A supplier references an HSM validation. The purchasing lead asks for the hardware and firmware versions and matches them against the public policy before acceptance.
    Decision record
    Security links the certificate, policy version and configuration evidence. Procurement records the verified date.

    Check before handing it over

    The approval identifies the module actually being used and the relevant certificate conditions.

    Give the deployment team the verified versions, conditions and recheck triggers.

  4. 04

    Maintain the configuration and review changes

    Who Module owner + procurement + compliance When Before upgrades and at renewal reviews

    Track current certificate status, sunset and approved versions. Compare proposed changes with the validated configuration and ask the vendor or lab for documented change coverage. Recheck policy on historical or revoked listings.

    What to produce

    CMVP certificate and change logSpreadsheet

    Gather first

    • Current certificate and security policy
    • Deployed module inventory
    • Change tickets
    • Vendor correspondence
    • Applicable acquisition policy

    How to prepare it

    1. Record the certificate status, sunset, verified configurations and accountable owner. Set review dates for upcoming policy or version changes.
    2. Compare each proposed update with the validated version and policy. Ask the vendor or lab for documentation of coverage or a different certificate.
    3. Save the evidence with the approved decision, any interim measures and the next review date.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional change
    An upgrade changes the cryptographic library package. The owner records the old and proposed versions and checks with Procurement and the vendor before implementation.
    Review trigger
    A date alert prompts a live certificate lookup and checks which deployed systems rely on the module.

    Check before handing it over

    A reviewer can match the approved configuration, exception or replacement decision to current evidence.

    Give the signed decision to the system owner and reflect any approved update in the inventory.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes