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.
Free. Save your status, tasks and notes.
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
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.
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.
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.
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
- 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.
- 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.
- 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/IEC 27001: 1 mapping
This control partially meets A.8.8.
ISM-1697 requires applying vendor-provided mitigations for non-critical driver vulnerabilities within one month where no working exploits exist. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, assess exposure, and take appropriate measures across information systems generally. ISM-1697 is a specific, time-bound patching requirement within the broader vulnerability management expectations of Annex A 8.8.
ASD Essential Eight: 10 mappings
This control is equivalent to E8-PO-ML3.6.
ISM-1697 requires organisations to apply patches, updates or other vendor mitigations for non-critical driver vulnerabilities within one month where no working exploits exist. E8-PO-ML3.6 states the same patching requirement with the same scope (drivers), timing (one month), and conditions (non-critical, no working exploits). Implementing E8-PO-ML3.6 would therefore largely satisfy ISM-1697.
- E8-PA-ML1.6Apply non-critical online service patches within two weeks if no exploits existPartially overlaps
This control partially overlaps E8-PA-ML1.6.
ISM-1697 requires organisations to patch non-critical driver vulnerabilities within one month where no working exploits exist. E8-PA-ML1.6 similarly requires patching of non-critical vulnerabilities with no working exploits, but for online services and within two weeks. They overlap on vulnerability-driven patching, but have different technology scope and mandated timeframes.
- E8-PO-ML3.4Non-critical non-internet-facing OS patches within one month if no exploitsPartially overlaps
This control partially overlaps E8-PO-ML3.4.
ISM-1697 requires applying non-critical patches for driver vulnerabilities within one month when no working exploits exist. E8-PO-ML3.4 sets the same one-month/non-critical/no-exploit requirement, but for operating systems on workstations and non-internet-facing servers/devices rather than drivers. They overlap on patch timeliness for non-critical vulnerabilities, but differ in the asset category being patched.
This control partially overlaps E8-PO-ML3.5.
ISM-1697 requires organisations to apply vendor mitigations for driver vulnerabilities within one month when they are assessed as non-critical and no working exploits exist. E8-PO-ML3.5 addresses the same technology scope (drivers) but applies to critical vulnerabilities or those with working exploits and requires patching within 48 hours. The controls overlap on driver patching governance, but they target different risk conditions and impose different timeframes.
This control partially overlaps E8-PO-ML3.7.
ISM-1697 requires applying non-critical driver patches within one month when no working exploits exist. E8-PO-ML3.7 requires patching firmware vulnerabilities within 48 hours when they are critical or when working exploits exist. The overlap is limited to the general patch/mitigation concept, with key differences in both asset type (firmware vs drivers) and urgency/risk trigger (critical/exploited vs non-critical/non-exploited).
- E8-PO-ML3.8Firmware vulnerabilities patched within one month if non-critical and no exploitsPartially overlaps
This control partially overlaps E8-PO-ML3.8.
ISM-1697 requires organisations to apply non-critical patches for driver vulnerabilities within one month when no working exploits exist. E8-PO-ML3.8 applies the same timing and exploit/criticality conditions, but for firmware rather than drivers. They overlap on the general patch-timeliness principle, but differ materially in asset class and technical scope.
This control supports E8-AC-ML3.3.
ISM-1697 requires patching non-critical driver vulnerabilities within one month when no working exploits exist. E8-AC-ML3.3 supports ISM-1697 by reducing exposure to known vulnerable drivers through Microsoft's vulnerable driver blocklist, acting as an additional vendor mitigation when patching is pending or unavailable. The blocklist is a different control mechanism than patching and does not replace the one-month remediation requirement in ISM-1697.
This control supports E8-PO-ML1.1.
ISM-1697 requires applying non-critical driver patches within one month when no working exploits exist. E8-PO-ML1.1 supports ISM-1697 by requiring automated asset discovery to feed vulnerability scanning, helping ensure devices with vulnerable drivers are in scope for patch tracking and remediation. The candidate control is foundational for coverage, but it does not itself require patch deployment within a defined window.
This control depends on E8-PO-ML1.2.
ISM-1697 requires organisations to apply non-critical driver patches within one month where no working exploits exist. E8-PO-ML1.2 supports ISM-1697 by requiring vulnerability scanning with an up-to-date database, which helps identify missing patches/updates and validate remediation status for components such as drivers. The scanning requirement is complementary but does not define the driver patching timeframe or conditions itself.
This control depends on E8-PO-ML3.1.
ISM-1697 requires organisations to apply non-critical driver patches within one month where no working exploits exist. E8-PO-ML3.1 supports ISM-1697 by requiring fortnightly vulnerability scanning to identify missing driver patches, which helps detect non-compliance with the one-month patch window. Scanning improves visibility and assurance, but it does not itself mandate the patch application timeframe or decision conditions.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




