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.
3
artefacts
1
held by a system
0
at each review
moderate
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Patch compliance dashboard (Defender/Tenable/Qualys) · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- 14-day SLA report · Policy repository / GRC workspace
- Exception register · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Vulnerability scanner / patch tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.
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