SU.3 Critical and High Updates within 14 Days
All high or critical security updates (CVSS 7.0+ or vendor critical/high rating) must be applied within 14 days of release.
Source: UK Cyber Essentials, SU.3. 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
- Patch compliance dashboard from the patch or vulnerability management tool · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- 14-day SLA report · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Exception register · Policy repository / GRC workspace
First move
Common gaps auditors find
- patch backlog beyond 14 days
- no CVSS-based tracking
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 sheetSU.2 Automatic Updates Enabled Where Possible · SU.4 Remove Out-of-Support Software