SC.8 Process for Compromised Passwords
Have a process to change passwords promptly when the user knows or suspects the password or account has been compromised.
Source: UK Cyber Essentials, SC.8. 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
none for this control
periodic reviewEvidence produced at each review
- Service desk ticket sample · Ticketing / ITSM
governing documentDocuments that govern the control
- Password reset procedure · Policy repository / GRC workspace
- Incident playbook section · Document repository
First move
Common gaps auditors find
- no documented reset workflow
- users unaware how to report
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 sheetSC.7 Educate Users on Strong Passwords · SC.9 Device Unlocking Credentials and Brute-Force Protection