CM-14 Signed Components
Requires and verifies cryptographic signatures on delivered software, firmware and updates before installation.
Source: NIST SP 800-161 Rev 1 (supply chain), CM-14. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-161 Rev 1 (supply chain) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
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
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