Windows Defender Application Control example base policies
- Windows 10
- Windows 11
- Windows Server 2016 and above
Some capabilities of Windows Defender Application Control are only available on specific Windows versions. For more information, see Windows Defender Application Control feature availability.
When you create policies for use with Windows Defender Application Control (WDAC), start from an existing base policy and then add or remove rules to build your own custom policy. Windows includes several example policies that you can use.
|Example Base Policy||Description||Where it can be found|
|DefaultWindows_*.xml||This example policy is available in both audit and enforced mode. It includes rules to allow Windows, third-party hardware and software kernel drivers, and Windows Store apps. Used as the basis for the Microsoft Intune product family policies.||%OSDrive%\Windows\schemas\CodeIntegrity\ExamplePolicies\DefaultWindows_*.xml
|AllowMicrosoft.xml||This example policy includes the rules from DefaultWindows and adds rules to trust apps signed by the Microsoft product root certificate.||%OSDrive%\Windows\schemas\CodeIntegrity\ExamplePolicies\AllowMicrosoft.xml
|AllowAll.xml||This example policy is useful when creating a blocklist. All block policies should include rules allowing all other code to run and then add the DENY rules for your organization's needs.||%OSDrive%\Windows\schemas\CodeIntegrity\ExamplePolicies\AllowAll.xml|
|AllowAll_EnableHVCI.xml||This example policy can be used to enable memory integrity (also known as hypervisor-protected code integrity) using WDAC.||%OSDrive%\Windows\schemas\CodeIntegrity\ExamplePolicies\AllowAll_EnableHVCI.xml|
|DenyAllAudit.xml||Warning: May cause long boot time on Windows Server 2019. Only deploy this example policy in audit mode to track all binaries running on critical systems or to meet regulatory requirements.||%OSDrive%\Windows\schemas\CodeIntegrity\ExamplePolicies\DenyAllAudit.xml|
|Microsoft Configuration Manager||Customers who use Configuration Manager can deploy a policy with Configuration Manager's built-in WDAC integration, and then use the generated policy XML as an example base policy.||%OSDrive%\Windows\CCM\DeviceGuard on a managed endpoint|
|SmartAppControl.xml||This example policy includes rules based on Smart App Control that are well-suited for lightly managed systems. This policy includes a rule that is unsupported for enterprise WDAC policies and must be removed. For more information about using this example policy, see Create a custom base policy using an example base policy.||%OSDrive%\Windows\schemas\CodeIntegrity\ExamplePolicies\SmartAppControl.xml
|Example supplemental policy||This example policy shows how to use supplemental policy to expand the DefaultWindows_Audit.xml allow a single Microsoft-signed file.||%OSDrive%\Windows\schemas\CodeIntegrity\ExamplePolicies\DefaultWindows_Supplemental.xml|
|Microsoft Recommended Block List||This policy includes a list of Windows and Microsoft-signed code that Microsoft recommends blocking when using WDAC, if possible.||Microsoft recommended block rules
|Microsoft recommended driver blocklist||This policy includes rules to block known vulnerable or malicious kernel drivers.||Microsoft recommended driver block rules
|Windows S mode||This policy includes the rules used to enforce Windows S mode.||%ProgramFiles%\WindowsApps\Microsoft.WDAC.WDACWizard*\WinSiPolicy.xml.xml|
|Windows 11 SE||This policy includes the rules used to enforce Windows 11 SE, a version of Windows built for use in schools.||%ProgramFiles%\WindowsApps\Microsoft.WDAC.WDACWizard*\WinSEPolicy.xml.xml|
Not all policies shown available at %OSDrive%\Windows\schemas\CodeIntegrity\ExamplePolicies can be found on all versions of Windows.
Submit and view feedback for