Essential Eight AC-ML3.3 Microsoft's vulnerable driver blocklist is implemented
What it says
Microsoft's vulnerable driver blocklist is implemented.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Implement Microsoft's vulnerable driver blocklist so Windows workstations and servers refuse to load drivers Microsoft lists as vulnerable, malicious or able to bypass Windows security.
At Maturity Level Three, Microsoft's vulnerable driver blocklist must be implemented. The blocklist is Microsoft's list of drivers that have known security flaws, behave maliciously or get around Windows security, and implemented means Windows workstations and servers refuse to load them. Many listed drivers are validly signed, so the blocklist must apply even where a signing rule or the approved set of drivers (E8-AC-ML3.2) would otherwise allow them.
Free. Save your status, tasks and notes.
Why it matters
Attackers at this level can load an old, validly signed driver with a known flaw, then use the flaw to switch off security tools or take full control. The blocklist keeps listed drivers from loading, even where a signature-based rule would allow them.
How to implement
Check where the blocklist is enforced today.
On a sample of Windows workstations and servers, check the device security setting for the vulnerable driver blocklist and whether memory integrity is on, because on supported Windows versions other than Windows Server 2016, memory integrity also enforces the blocklist.
Find and fix devices that load a listed driver before enforcing.
Where you deploy Microsoft's published driver block rules through application control, run them in audit mode first to find these devices, then update or replace the driver or the hardware. An exception for a listed driver is a known gap until it is closed, not compliance.
Enforce it on every device through central management.
Turning on memory integrity, which E8-RA-ML3.4 requires anyway, enforces the blocklist on supported versions other than Windows Server 2016, as does the blocklist setting where available. Where neither does, as on Windows Server 2016, or for the newest list, add Microsoft's published driver block rules to your application control driver rules (E8-AC-ML3.2).
Keep it running
Keep the blocklist current through Windows updates and, if you use the published rules, by loading each new release. Check new devices and server builds have it on, and fix any driver it blocks rather than excepting it.
Evidence and audit
- Check 1 of 2What an auditor asks for
Ask for
Blocklist status for a sample of workstations and servers drawn from an independent device list.
Look at
Whether the blocklist is enforced on each, through the device setting, memory integrity (which does not enforce it on Windows Server 2016) or application control rules.
Good evidence
The blocklist is enforced on every sampled workstation and server, with none switched off, left in audit mode or covered by an exception.
- Check 2 of 2What an auditor asks for
Ask for
A test on isolated test devices, one built from each standard workstation and server image, of loading a driver that is on the blocklist.
Look at
Whether the driver is refused on each device and the refusal is logged.
Good evidence
The listed driver fails to load on every test device and each refusal is recorded in that device's logs.
Mappings
Closest match in ASD Information Security Manual: ISM-1659, Implement Microsoft's vulnerable driver blocklist, which asks for the same thing.
ISO/IEC 27001: 2 mappings
This control partially meets A.8.8.
E8-AC-ML3.3 requires a specific measure: enabling Microsoft's vulnerable driver blocklist to reduce exposure to driver vulnerabilities. ISO/IEC 27001:2022 Annex A 8.8 requires obtaining information about technical vulnerabilities, evaluating exposure, and applying appropriate measures across information systems generally. E8-AC-ML3.3 is a concrete technical implementation that can be selected as one 'appropriate measure' under Annex A 8.8, but Annex A 8.8 is much broader in scope and method.
This control partially meets A.8.19.
E8-AC-ML3.3 requires implementing Microsoft's vulnerable driver blocklist to stop vulnerable drivers from running on Windows systems. ISO/IEC 27001:2022 Annex A 8.19 supports this by requiring secure software installation procedures, which can include controls to restrict or validate driver installation and reduce exposure to malicious or vulnerable drivers. Annex A 8.19 is procedural and technology-agnostic, while E8-AC-ML3.3 is a specific Microsoft platform enforcement mechanism.
ASD Information Security Manual: 5 mappings
This control is equivalent to ISM-1659.
E8-AC-ML3.3 requires organisations to implement Microsoft's vulnerable driver blocklist to prevent known vulnerable drivers from loading on Windows systems. ISM-1659 states the same requirement to implement Microsoft's vulnerable driver blocklist. Both controls have the same technical intent and implementation focus (blocking vulnerable kernel drivers) with no material difference in scope.
This control partially overlaps ISM-0298.
E8-AC-ML3.3 requires implementing Microsoft's vulnerable driver blocklist to prevent execution of known vulnerable drivers. ISM-0298 requires a centralised, managed approach to patch or update applications, operating systems, drivers and firmware and to verify successful application. They overlap in managing driver-related risk, but E8-AC-ML3.3 is an execution-prevention control while ISM-0298 is a lifecycle maintenance/patching control that does not necessarily enforce runtime blocking.
This control partially overlaps ISM-1492.
E8-AC-ML3.3 requires implementing Microsoft's vulnerable driver blocklist to prevent exploitation via known vulnerable kernel drivers. ISM-1492 relates by requiring operating system exploit protection to be enabled, which can mitigate exploitation techniques (including some privilege escalation paths) even if a vulnerable driver is present. The blocklist prevents specific drivers from loading, whereas exploit protection is a broader OS hardening measure and may not stop a vulnerable driver from being installed or started.
This control partially overlaps ISM-1703.
E8-AC-ML3.3 requires organisations to implement Microsoft's vulnerable driver blocklist to stop known vulnerable drivers from running. ISM-1703 relates by requiring regular vulnerability scanning to identify missing patches or updates for driver vulnerabilities, which helps discover and remediate the same class of driver risk that the blocklist mitigates at runtime. The blocklist is an execution prevention control, whereas ISM-1703 is a detection/assessment control and does not by itself prevent a vulnerable driver from loading.
This control depends on ISM-1697.
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.
ASD Essentials for enterprise IT: 1 mapping
- IT.PRO-07.1Restrict execution to supported, verified and authorised software with time-bound exceptionsPartially overlaps
This control partially overlaps IT.PRO-07.1.
IT.PRO-07.1 requires that only supported, verified and organisation-authorised software can execute; E8-AC-ML3.3 requires Microsoft's vulnerable driver blocklist to be implemented, a narrower measure that blocks the vulnerable drivers on that list.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




