PA-2 Avoid standing access for user accounts and permissions
Use Privileged Identity Management (PIM) for just-in-time access elevation with approval workflows and time-bound activation.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), PA-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
- PIM configuration · Identity provider / directory
- JIT activation logs · Identity provider / directory
- Access review history · Identity provider / directory
periodic reviewEvidence produced at each review
- Approval workflow records · Identity provider / directory
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Permanent role assignments
- PIM not configured for Azure RBAC
- No approval required for sensitive roles
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-1 Separate and limit highly privileged/administrative users · PA-3 Manage lifecycle of identities and entitlements