EvidenceSheet

A.8.18 Use of privileged utility programs

Restrict and tightly control utilities that can override system and application controls.

12
artefacts
3
held by a system
4
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

  • System logs showing execution of privileged utilities · Identity provider / directory
  • Centralized logging configuration for utility usage · SIEM / log platform
  • Audit trail of changes to utility configurations · SIEM / log platform

periodic reviewEvidence produced at each review

  • Risk assessment for each utility · Identity provider / directory
  • Management approval email records · Identity provider / directory
  • Periodic privileged utility usage review report · Identity provider / directory
  • Exception handling records for unauthorized usage · Cloud console / configuration management

governing documentDocuments that govern the control

  • Privileged utility program inventory register · Policy repository / GRC workspace
  • Tool version and patch status report · Policy repository / GRC workspace
  • Log retention policy document · Policy repository / GRC workspace
  • Approved request forms for privileged utility access · Policy repository / GRC workspace
  • Access control matrix for utility accounts · Policy repository / GRC workspace

First move

Start with the 3 of 12 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.

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

A.8.17 Clock synchronization · A.8.19 Installation of software on operational systems