Skip to content
Application control
Essential EightE8-AC-ML3.3

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.

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

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

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

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

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

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

ISO/IEC 27001: 2 mappings

ASD ISM

ASD Information Security Manual: 5 mappings

ASD Essentials

ASD Essentials for enterprise IT: 1 mapping

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