What is the most common gap auditors find on PATCHOS-ISM-1703?

Driver versions not visible to the scanner and never checked

ACSC Essential Eight Maturity Model (November 2023) · Patch operating systems

`PATCHOS-ISM-1703` A vulnerability scanner is used at least fortnightly to identify missing patches or updates for…

Q: What evidence do auditors commonly ask for on PATCHOS-ISM-1703 A vulnerability scanner is used at least fortnightly to identify missing patches or updates for…?

Fortnightly scan results identifying missing driver updates; Driver inventory by device model.

A vulnerability scanner is used at least fortnightly to identify missing patches or updates for vulnerabilities in drivers. Required at Maturity Level Three of the Patch operating systems mitigation strategy (Appendix C); ISM control ISM-1703 in ASD's Essential Eight to ISM mapping (December 2023).

Source: ACSC Essential Eight Maturity Model (November 2023), PATCHOS-ISM-1703. 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 ACSC Essential Eight Maturity Model (November 2023) in the compliance library.

Each row is an ISM control the maturity model requires, with the maturity levels named in its text. Pick your target maturity level and use the rows for it.

artefacts

held by a system

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. 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

Driver inventory by device model · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Fortnightly scan results identifying missing driver updates · 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

Driver versions not visible to the scanner and never checked

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

PATCHOS-ISM-1702 A vulnerability scanner is used at least fortnightly to identify missing patches or updates for… · PATCHOS-ISM-1807 An automated method of asset discovery is used at least fortnightly to support the detection of assets for…