COPRSETR WORKSHEET
CMVP certificate and change log
FIPS 140-3 cryptographic module validation · Step 4 · Maintain the configuration and review changes- Who prepares it
- Module owner + procurement + compliance
- When to prepare it
- Before upgrades and at renewal reviews
Worked example
This example uses 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.
Gather first
- Current certificate and security policy
- Deployed module inventory
- Change tickets
- Vendor correspondence
- Applicable acquisition policy
How to prepare it
- Record the certificate status, sunset, verified configurations and accountable owner. Set review dates for upcoming policy or version changes.
- Compare each proposed update with the validated version and policy. Ask the vendor or lab for documentation of coverage or a different certificate.
- Save the evidence with the approved decision, any interim measures and the next review date.
Review
A reviewer can match the approved configuration, exception or replacement decision to current evidence.
Handoff
Give the signed decision to the system owner and reflect any approved update in the inventory.
Use the issuer’s current instructions and any required forms when you submit.
NIST CMVP frequently asked questions (opens in a new tab)