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.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), PV-4. 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
- 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
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