IAM-11 CSCs Approval for Agreed Privileged Access Roles
Let cloud customers take part in approving high risk privileged access to their environment where the organisation's risk assessment says that is warranted.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
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
- The risk assessment defining which roles are high risk · Identity provider / directory
- Records of customer approvals obtained · Document repository
governing documentDocuments that govern the control
- The procedure describing customer participation in privileged access approval · Policy repository / GRC workspace
- The technical mechanism by which a customer approves or denies · 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
- Capability described but no mechanism exists for a customer to use it
- High risk roles never defined, so the process never triggers
- Customer approval sought after access was already used
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-10 Management of Privileged Access Roles · IAM-12 Safeguard Logs Integrity