EvidenceSheet

8.2 Privileged access rights

Requires the allocation and use of privileged access rights to be restricted and actively managed.

5
artefacts
0
held by a system
4
at each review
hard
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

none for this control

periodic reviewEvidence produced at each review

  • Authorisation records for each privileged allocation, showing the business justification and the approver · Identity provider / directory
  • Evidence of restriction, such as separate administrative accounts, multi factor authentication, session recording, vaulting or time bound elevation · Identity provider / directory
  • Logs of privileged activity and evidence of their review · Identity provider / directory
  • Records of periodic review of privileged rights, and of revocation where the need has ended · Identity provider / directory

governing documentDocuments that govern the control

  • The definition of what counts as privileged in each system, and the register of privileged accounts and their holders · 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

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 sheet

8.1 User endpoint devices · 8.3 Information access restriction