IAM-09 Segregation of Privileged Access Roles
Separate privileged roles so that administration of data, of encryption and key management, and of logging are held by distinct roles rather than one super-administrator.
4
artefacts
0
held by a system
2
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
- Assignment records proving no individual holds conflicting roles · Identity provider / directory
- Evaluation evidence such as a conflict report · Identity provider / directory
governing documentDocuments that govern the control
- The privileged role definitions showing the separation · Policy repository / GRC workspace
- Technical enforcement of the separation · 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
- A platform administrator role that implicitly carries key and log administration
- Separation defined and then defeated by an emergency access role
- No conflict reporting, so accumulation is unnoticed
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 sheetIAM-08 User Access Review · IAM-10 Management of Privileged Access Roles