CM-14 Signed Components
Prevent the installation of FedRAMP-defined software and firmware components without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization.
3
artefacts
1
held by a system
0
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration showing signature enforcement at install time · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Code-signing policy naming the approved certificate authorities · Policy repository / GRC workspace
- Exception register for unsigned components with compensating controls · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Signature checking enforced on servers but not on build agents or container images
- Approved certificate list not maintained, so revoked signers still pass
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 sheetCM-12(1) Information Location | Automated Tools to Support Information Location. Use automated tools to identify [Assignment: organization-defined information by information type] on [Assignment: organization-defined system components] to ensure controls are in place to protect organizational · CP-1 Policy and Procedures