CM-14 Signed Components
Requires and verifies cryptographic signatures on delivered software, firmware and updates before installation.
3
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Records of verification for sampled updates · Document repository
governing documentDocuments that govern the control
- Signature verification configuration or procedure · Policy repository / GRC workspace
- Handling of components that cannot be verified · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- signatures present but never checked
- unsigned firmware installed because verification is inconvenient
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet