Skip to content
System management
ASD ISMISM-1697

ASD ISM 1697 Patch drivers within one month if non-critical with no working exploit

What it says

Patches, updates or other vendor mitigations for vulnerabilities in drivers are applied within one month of release when vulnerabilities are assessed as non-critical by vendors and no working exploits exist.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Driver fixes for flaws the vendor rates non-critical, with no working exploit, must be installed within one month of the vendor releasing them.

Vendor patches, updates or other mitigations for vulnerabilities in drivers must be applied within one month of release when the vendor rates the vulnerability non-critical and no working exploit exists. Both conditions must hold. A driver is software that lets an operating system use hardware such as a network adapter, graphics card or printer, and drivers on every type of device are covered. If the vendor raises the rating to critical or a working exploit appears, ISM-1879 requires the fix within 48 hours of release instead.

Why it matters

Driver fixes are easy to miss because many come from hardware makers, not the operating system's update service. Left in place, even lower-rated flaws in this highly privileged code can let malicious actors take control of a device; one month limits that.

How to implement

  1. Know which drivers run on your devices.

    Pull driver names, versions and makers from the endpoint management tool into the software register (ISM-1643 requires driver versions and patch histories), covering servers as well as workstations.

  2. Track driver releases from every maker.

    Subscribe to the security notices of each hardware and component maker, not only the operating system vendor, and record each fix's release date, the vendor's rating and any working exploit.

  3. Roll non-critical driver fixes into a scheduled release inside the month.

    Package them in the central patch tool, test on one device of each affected hardware model, then deploy with a deadline that leaves time to retry failures before the month ends.

  4. Find and fix devices that missed the update.

    Use the driver vulnerability scanning ISM-1703 requires to find devices still running old versions, and follow up failed installs and devices that have been offline.

Keep it running

Recheck a pending driver fix if the vendor raises its rating or a working exploit is reported, since ISM-1879's 48 hours then apply. Add each new hardware model's drivers and maker to the watch list when the model is introduced.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    Driver fixes the vendors rated non-critical over a recent period, taken from hardware and operating system makers' notices, with install records for a sample of affected devices.

    Look at

    The time from each release to its installation on each sampled device.

    Good evidence

    Each sampled driver fix was applied on every sampled affected device within one month of release; a device left on an exception or accepted risk counts as a failure.

  2. Check 2 of 3What an auditor asks for

    Ask for

    The driver entries in the software register compared with drivers found installed on sampled devices.

    Look at

    Whether drivers from all makers are recorded and their releases watched.

    Good evidence

    Every driver found on the sampled devices is in the register with its maker and version, and that maker's security notices are watched.

  3. Check 3 of 3What an auditor asks for

    Ask for

    The rating and exploit status recorded for driver fixes handled on the one-month timeframe, checked against vendor notices and ASD alerts.

    Look at

    Whether any was rated critical by the vendor, or had a working exploit, before it was installed.

    Good evidence

    Every driver fix handled on the one-month timeframe stayed non-critical with no working exploit until installed, or was moved to the 48-hour process as soon as that changed.

Mappings

Closest match in ASD Essential Eight: E8-PO-ML3.6, Apply non-critical driver patches within one month if no exploits exist, which asks for the same thing.

ISO 27001

ISO/IEC 27001: 1 mapping

Essential Eight

ASD Essential Eight: 10 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.