PV-2 Audit and enforce secure configurations
Use Azure Policy and Defender for Cloud secure score to audit and enforce configuration baselines across subscriptions.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), PV-2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
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
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