PV-2 Audit and enforce secure configurations
Use Azure Policy and Defender for Cloud secure score to audit and enforce configuration baselines across subscriptions.
3
artefacts
2
held by a system
0
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
- Policy compliance dashboard · Cloud console / configuration management
- Drift remediation log · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Secure Score trend · 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
- Secure Score declining
- Policies in audit mode never enforced
- Non-compliant resources unremediated
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-1 Define and establish secure configurations · PV-3 Define and establish secure configurations for compute resources