SEC06-BP05 Automate compute protection
Automate scanning, patching and remediation of compute resources so protection operations run without human intervention, including dependency freshness checks in the delivery pipeline.
4
artefacts
3
held by a system
0
at each review
easy
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Automated patch schedule and its execution records · Vulnerability scanner / patch tooling
- Automated remediation rules and their trigger history · Document repository
- Dependency scanning results from the CI/CD pipeline · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Mean time to patch measured by severity · Policy repository / GRC workspace
First move
Automate the pull from your Vulnerability scanner / patch tooling. Scan schedule, findings and remediation age straight from the scanner; patch compliance from the patch console.
Common gaps auditors find
- patching raised as tickets that queue behind feature work
- remediation automation built but left in report-only mode
- dependency scanning absent from the pipeline
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-BP04 Validate software integrity · SEC07-BP01 Understand your data classification scheme