# CMVP certificate verification checklist

FIPS 140-3 cryptographic module validation | Worked example with fictional data

Step: Match the validation to the actual purchase
Owner: Procurement + security architecture + system owner
When: Before accepting a product claim or deployment

## 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.

## Example

### 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.

## 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.

Official reference: NIST validated module search
https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules/search

Use the current rules and any prescribed forms for your engagement.
