SEC06-BP04 Validate software integrity
Cryptographically verify the integrity of software artefacts the workload consumes and sign software the organisation produces so unauthorised changes are detectable before execution.
4
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
- Record of artefacts rejected for failed verification · Document repository
governing documentDocuments that govern the control
- Signing key management procedure and key inventory · Policy repository / GRC workspace
- Signature verification enforcement in the build or admission controller · Document repository
- Certificate validation policy for vendor download sources · Vendor register / contract 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
- downloads trusted on source reputation alone
- signing keys held on build agents with broad access
- verification implemented as a warning rather than a hard fail
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 sheetSEC06-BP03 Reduce manual management and interactive access · SEC06-BP05 Automate compute protection