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.
4
artefacts
2
held by a system
2
at each review
easy
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- PIM configuration · Identity provider / directory
- JIT activation logs · Identity provider / directory
periodic reviewEvidence produced at each review
- Approval workflow records · Identity provider / directory
- Access review history · Identity provider / directory
governing documentDocuments that govern the control
none for this control
First move
Automate the pull from your Identity provider / directory. Scheduled export of users, roles and MFA state from the directory; access-review completion pulled from the IdP, not a spreadsheet.
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