Course contentsShow
← Security
Lesson 1594 of 3,05232. Operating System Security - Endpoint ProtectionFree lesson

Windows Defender Application Control (WDAC)

Deploying WDAC for kernel and user-mode code integrity policies, managed and supplemental policies, and driver signing requirements.

Windows Defender Application Control (WDAC)

What you'll learn: How WDAC enforces code integrity through kernel and user-mode policies, managed configurations, and driver signing requirements.

The Core Idea

Windows Defender Application Control (WDAC) is Microsoft's enterprise-grade code integrity solution that goes deeper than AppLocker. While AppLocker focuses on what applications users can run, WDAC enforces trust at the code level—verifying that both user-mode applications and kernel-mode drivers meet your organization's integrity standards before they execute.

Think of it like airport security: AppLocker checks your boarding pass (application identity), but WDAC inspects the actual luggage contents (code signatures and integrity) for both passengers (user apps) and crew (kernel drivers).

How WDAC Works

Code Integrity Policies define what code can run based on cryptographic signatures, file hashes, or publisher certificates. WDAC enforces these policies in:

  • User mode: Applications, scripts, and libraries
  • Kernel mode: Drivers and system-level code

Managed vs. Supplemental Policies:

  • Managed (base) policies: Primary policies controlling overall system behavior
  • Supplemental policies: Add exceptions or expand rules without replacing the base policy—useful for departmental variations

Driver Signing Requirements:

WDAC can enforce strict driver signing, requiring that all kernel-mode drivers be signed by trusted publishers. This blocks unsigned or maliciously signed drivers—a critical defense against rootkits and kernel-level malware.

Deployment Considerations

WDAC policies are XML files converted to binary format and deployed via Group Policy, MDM, or local configuration. Policies can run in:

  • Audit mode: Logs violations without blocking (testing phase)
  • Enforced mode: Actively blocks non-compliant code

Multiple policies can coexist, with supplemental policies layering additional rules atop base policies.

Key Takeaway:
WDAC provides deep code integrity enforcement across both user and kernel modes through managed and supplemental policies, with robust driver signing controls that defend against sophisticated threats at the OS foundation.