PV-1 Define and establish secure configurations
Define secure configuration baselines for each resource type in the cloud, or establish them automatically through configuration management before or during deployment so environments are compliant by default.
4
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
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
none for this control
governing documentDocuments that govern the control
- Baseline definition per resource type · Policy repository / GRC workspace
- Policy or template implementing the baseline at deployment · Policy repository / GRC workspace
- Exception register with owner and expiry · Policy repository / GRC workspace
- Coverage report showing resource types with and without a baseline · Policy repository / GRC workspace
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
- baselines documented in prose but not encoded in policy
- baseline exists for virtual machines only
- new resource types deployed with no baseline defined
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 sheetPA-8 Determine access process for cloud provider support · PV-2 Audit and enforce secure configurations