PV-3 Define and establish secure configurations for compute resources
Define secure configuration baselines specifically for compute resources such as virtual machines and containers, established automatically at or before deployment.
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Source control / CI pipeline
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Hardened image build pipeline and its output catalogue · Source control / CI pipeline
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Compute hardening standard referencing a recognised benchmark · Policy repository / GRC workspace
- Container base image standard and admission policy · Policy repository / GRC workspace
- Baseline coverage across virtual machine and container estates · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Source control / CI pipeline); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- hardening applied post-deployment by script that sometimes fails
- container workloads exempt from the compute baseline
- hardened images built once and never refreshed
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 sheetPV-2 Audit and enforce secure configurations · PV-4 Audit and enforce secure configurations for compute resources