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.
Source: UK Cyber Essentials, AC.4. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open UK Cyber Essentials in the compliance library.
The version of the requirements is not stamped here; check the question set your certification body uses.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- List of all admin accounts with owner · Identity provider / directory
periodic reviewEvidence produced at each review
- Approval records · Identity provider / directory
governing documentDocuments that govern the control
- PAM tool inventory · Policy repository / GRC workspace
First move
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