Template library
COPRSETR WORKSHEET

CMVP lab evidence register

FIPS 140-3 cryptographic module validation · Step 2 · Prepare the evidence and track lab review
Who prepares it
Module engineering + Quality + lab
When to prepare it
Before and during testing

Worked example

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

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.

Review

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

Handoff

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

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

Current CMVP Management Manual (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