EvidenceSheet
UK Cyber Essentials · User Access Control

AC.1 User Account Approval Process

Have a documented user account creation and approval process. All accounts must be approved by an authorised individual before creation.

Source: UK Cyber Essentials, AC.1. 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.

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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

  • Approval tickets · Identity provider / directory

periodic reviewEvidence produced at each review

  • HR-IT integration evidence · Identity provider / directory

governing documentDocuments that govern the control

  • Joiner workflow · 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

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

AC.2 Authenticate Users Before Granting Access