AC.L2-3.1.6 Non-Privileged Account Use
Require staff holding privileged accounts to use a non privileged account or role when performing work that does not need elevated rights.
3
artefacts
1
held by a system
1
at each review
moderate
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
- Logs showing routine activity performed under non privileged accounts · Identity provider / directory
periodic reviewEvidence produced at each review
- Evidence that administrators hold distinct day-to-day accounts · Identity provider / directory
governing documentDocuments that govern the control
- Policy requiring separate privileged and non privileged accounts · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Administrators use privileged accounts for email and browsing
- Dual accounts issued but daily use not enforced or monitored
- No detection of privileged account use for nonsecurity tasks
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.L2-3.1.5 Least Privilege · AC.L2-3.1.7 Privileged Functions