AC.4 Privileged Account Approval and Tracking
Implement an approval process and keep track of privileged (administrative) accounts. The granting of privileges must be controlled.
3
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
- Approval records · Identity provider / directory
governing documentDocuments that govern the control
- List of all admin accounts with owner · Policy repository / GRC workspace
- PAM tool inventory · 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
- unmanaged local admin
- no register of cloud admin roles
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 sheetAC.3 Remove or Disable Accounts When No Longer Required · AC.5 Separate Admin Accounts for Administrative Activities