PSS-08 Roles and Rights Concept
Give cloud users a roles and rights concept for managing access, describing the rights profiles available for each service function so that permissions can follow least privilege and need to know, and operational duties
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Published roles and rights concept listing a rights profile per service function · Policy repository / GRC workspace
- Mapping of each profile to the individual permissions it confers · Policy repository / GRC workspace
- Guidance identifying profile combinations that undermine separation of duties · Document repository
- Customer documentation explaining how profiles are assigned and revoked · Document repository
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
- Only broad administrator and read only profiles offered, forcing over privileging
- Rights profiles undocumented, so customers cannot apply least privilege
- Operational and controlling permissions bundled into a single profile
- Concept not extended when new service functions were released
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 sheetPSS-07 Confidentiality of Authentication Information · PSS-09 Authorisation Mechanisms