Template library
COPRSETR WORKSHEET

CMVP certificate verification checklist

FIPS 140-3 cryptographic module validation · Step 3 · Match the validation to the actual purchase
Who prepares it
Procurement + security architecture + system owner
When to prepare it
Before accepting a product claim or deployment

Worked example

This example uses 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.

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.

Review

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

Handoff

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

Use the issuer’s current instructions and any required forms when you submit.

NIST validated module search (opens in a new tab)

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