PA-7 Follow just enough administration (least privilege) principle
Apply just enough administration by managing permissions at fine granularity, using role-based access control to grant only the access a role needs.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Evidence of custom roles replacing broad built-in roles · Identity provider / directory
governing documentDocuments that govern the control
- Role definitions in use with their permission scope · Policy repository / GRC workspace
- Assignment inventory showing scope of each assignment · Policy repository / GRC workspace
- Report on unused permissions identified and removed · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- owner or contributor granted at subscription scope as a default
- custom roles never created so broad built-ins are the only option
- permission usage never analysed so grants only ever grow
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-6 Use privileged access workstations · PA-8 Determine access process for cloud provider support