PATCHOS-ML1 Patch Operating Systems (ML1)
An automated method of asset discovery is used at least fortnightly. A vulnerability scanner with an up-to-date vulnerability database is used. The scanner runs at least daily for operating systems of internet-facing ser
8
artefacts
5
held by a system
1
at each review
easy
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
- Asset discovery configuration and reports showing fortnightly cadence covering servers, workstations and network devices · Endpoint management (MDM / EDR)
- Authenticated OS vulnerability scan results (Nessus, Qualys, Defender for Endpoint TVM) with last-update timestamp · Vulnerability scanner / patch tooling
- Daily scan schedule and report for internet-facing servers and network devices (perimeter firewalls, load balancers, VPN concentrators) · Vulnerability scanner / patch tooling
- Fortnightly scan schedule and report for workstations and non-internet-facing infrastructure · Vulnerability scanner / patch tooling
- Network device firmware management evidence (Cisco PSIRT subscription, deployment tickets) · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Patch deployment evidence (WSUS, SCCM, Intune, Jamf, vendor portals for network devices) with CVE-to-patch timestamps · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Asset register showing no out-of-support OS (e.g. no Windows 7, no Server R2 past EOL) · Policy repository / GRC workspace
- EOL replacement plan for any in-progress migrations with compensating controls · Policy repository / GRC workspace
First move
Automate the pull from your Vulnerability scanner / patch tooling. Scan schedule, findings and remediation age straight from the scanner; patch compliance from the patch console.
Common gaps auditors find
- Network devices not in vulnerability scan scope
- Internet-facing servers patched in 48 hours but cloud-managed appliances (load balancer firmware) miss SLA
- Workstations patched via WSUS but roaming or remote machines miss the one-month window
- Non-internet-facing servers patched on quarterly cycle, breaching one-month SLA
- Out-of-support OS retained for legacy app without compensating control documented
- Asset discovery misses cloud VMs spun up outside the central inventory
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 sheetPATCHAPP-ML3 Patch Applications (ML3) · PATCHOS-ML2 Patch Operating Systems (ML2)