PV-5 Perform vulnerability assessments
Use Defender Vulnerability Management or equivalent to identify vulnerabilities in VMs, containers, and databases on a continuous basis.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), PV-5. 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
- Patch management evidence · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Vulnerability assessment coverage report · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Critical/high vulnerability ageing · Policy repository / GRC workspace
First move
Common gaps auditors find
- VAs not scheduled regularly
- Coverage gaps for containers
- Critical findings exceed SLA
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-4 Audit and enforce secure configurations for compute resources · PV-6 Rapidly and automatically remediate vulnerabilities