How to Configure Exploit Protection System Mitigations in Windows 11 Using PowerShell

Modern memory corruption exploits—such as buffer overflows, return-oriented programming (ROP) chains, and heap spray attacks—seek to compromise operating system integrity by hijacking running processes. Windows 11 incorporates Exploit Protection (the successor to the Enhanced Mitigation Experience Toolkit, or EMET) directly into the Windows Security subsystem. While basic protections are enabled by default, system administrators can configure and enforce advanced system-wide and per-application mitigations using PowerShell to dramatically harden endpoints.

Key Exploit Protection Mitigations in Windows 11

Windows Exploit Protection enforces critical runtime memory mitigations:

  • Control Flow Guard (CFG): Restricts where an application can execute code from, preventing indirect call hijacking and ROP gadget execution.
  • Data Execution Prevention (DEP): Prevents code execution from non-executable memory segments (such as the default heap and stack).
  • Mandatory ASLR (Address Space Layout Randomisation): Forcefully randomises memory locations of DLLs and executables, preventing attackers from predicting target function offsets.
  • High-Entropy ASLR: Expands the virtual address randomization space on 64-bit processes to 1 terabyte, rendering brute-force guessing ineffective.
  • Bottom-Up ASLR: Randomises base allocation addresses for virtual memory mappings.

Inspecting Current Mitigations via PowerShell

To check the current system-wide mitigation posture:

  1. Right-click the Start button on Windows 11 and select Terminal (Admin) or PowerShell (Admin).
  2. Execute the Get-ProcessMitigation cmdlet to inspect active system settings:
    Get-ProcessMitigation -System
  3. Review the output properties, noting whether DEP, ASLR, Payload, and ControlFlowGuard indicate ON, OFF, or NOTSET.

Enforcing Advanced Mitigations Using Set-ProcessMitigation

To reinforce system-wide defenses and enforce Mandatory ASLR and High-Entropy ASLR globally:

# Enable system-wide Data Execution Prevention:
Set-ProcessMitigation -System -Enable DEP

# Enforce Bottom-Up ASLR and High-Entropy ASLR across all running binaries:
Set-ProcessMitigation -System -Enable BottomUp, HighEntropy

To apply targeted mitigations to high-risk applications (such as web browsers, PDF readers, or office applications):

# Enforce strict CFG, DEP, and Child Process Blocking on Microsoft Edge:
Set-ProcessMitigation -Name msedge.exe -Enable DEP, CFG, HighEntropy -Disable AllowChildProcessCreation

Exporting and Deploying Configuration Profiles via XML

For fleet-wide standardization across enterprise workstations, export your tested configuration:

  1. Export the active settings to an XML file:
    Get-ProcessMitigation -RegistryConfigFilePath "C:\Security\ExploitProtectionConfig.xml"
  2. Deploy the XML profile to other workstations or enforce it via Group Policy or Intune:
    Set-ProcessMitigation -PolicyFilePath "C:\Security\ExploitProtectionConfig.xml"

Hardening Windows 11 with PowerShell Exploit Protection mitigations neutralises exploitation vectors at the hardware and kernel boundaries, ensuring resilient defense against advanced persistent threats.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.