PV-4 Audit and enforce secure configurations for compute resources
Continuously monitor compute resources for deviation from the defined configuration baseline, alert on drift and enforce the desired configuration by denying or remediating non-compliant configuration.
4
artefacts
2
held by a system
1
at each review
easy
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 compliance dashboard for compute resources · Cloud console / configuration management
- Alert rules for baseline deviation · SIEM / log platform
periodic reviewEvidence produced at each review
- Remediation records with time to correct · Document repository
governing documentDocuments that govern the control
- Deny or remediate policy assignments and their effect history · Policy repository / GRC workspace
First move
Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.
Common gaps auditors find
- compliance measured but enforcement left in audit mode
- drift alerts routed to a mailbox nobody reads
- remediation manual and therefore inconsistent
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-3 Define and establish secure configurations for compute resources · PV-5 Perform vulnerability assessments