PA-4 Review and reconcile user access regularly
Review privileged account entitlements on a regular cycle and confirm the access granted remains valid for control plane, management plane and workload administration.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), PA-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
none for this control
periodic reviewEvidence produced at each review
- Access review schedule and completed review records · Identity provider / directory
- Reviewer attestations per privileged role · Identity provider / directory
- Removal records for access not recertified · Identity provider / directory
governing documentDocuments that govern the control
- Exception handling for accounts retained · Policy repository / GRC workspace
First move
Common gaps auditors find
- reviews completed by bulk approval with no scrutiny
- reviews cover directory roles but not resource-level assignments
- findings recorded but removals never executed
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 sheetPA-3 Manage lifecycle of identities and entitlements · PA-5 Set up emergency access