CM-14 Signed Components. Prevent the installation of [organization-defined] without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization
Signed Components. Prevent the installation of [organization-defined] without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization.
5
artefacts
2
held by a system
1
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 enforcing signature verification at install time, with the failure behaviour on an unsigned component · Cloud console / configuration management
- Installation or change records showing verification occurred, and evidence of a rejected unsigned component · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Definition of the software and firmware components required to be signed · Cloud console / configuration management
governing documentDocuments that govern the control
- List of certificates recognised and approved by the organisation for verifying signatures · Policy repository / GRC workspace
- Process for approving a new signing certificate and revoking one no longer trusted · Policy repository / GRC workspace
First move
Start with the 2 of 5 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
- Verification enforced on the operating system while application packages, drivers and container images install unverified
- Trust store accumulates certificates with no approval or revocation process behind it
- Enforcement set to warn rather than block, so an unsigned component still installs
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-13 Data Action Mapping. Develop and document a map of system data actions · CP-1 Policy and procedures for contingency planning