Windows Defender Application Control (WDAC) lets you decide which software, drivers and scripts may run on your Windows devices, and blocks everything else. Microsoft now calls the feature App Control for Business, but the older name is still everywhere in documentation, policy files and admin conversations. For a small or midsize business, the safe way in is simple: start with a policy in audit mode, read what it would have blocked, fix your rules, and only then enforce.
This guide explains what the feature does, what a policy contains, how to roll one out without stopping your team's work, and what upkeep to expect afterward.
TL;DR
- WDAC flips the default on Windows: code runs only if your policy allows it, instead of running unless antivirus flags it.
- A policy is a set of rules (publisher, file path, hash and others) plus options such as audit mode and managed installer.
- Always deploy in audit mode first, in small rings, and enforce only when the remaining audit events match what you expect.
- Publisher-based rules and a managed installer cut maintenance. Hash rules break whenever an app updates.
- Treat policies like code: keep them in version control and plan for regular changes.
Table of Contents
- What Windows Defender Application Control actually does
- How WDAC policies work
- Is your business ready for it?
- A rollout plan that does not lock your team out
- Checking that a policy is active
- The upkeep you should plan for
- Where WDAC fits in the rest of your security program
- Where Mindpod can help
- FAQ
- Sources
What Windows Defender Application Control actually does
Most endpoints work on a "run unless it looks bad" model. Antivirus watches for known or predicted threats, and everything else executes. Application control reverses that. According to Microsoft's overview of application control for Windows, it moves Windows to a model where code runs only if your policy says so, and it can restrict code running in the kernel as well as in user mode. It works alongside antivirus rather than replacing it.
Why that matters for a smaller company: ransomware, rogue installers and a lot of commodity malware depend on running something nobody approved. If an unapproved executable, script or driver cannot start, a large share of that risk never materializes. The Australian Signals Directorate's endpoint blueprint describes WDAC policies as able to enforce Constrained Language mode for Windows PowerShell, require drivers signed through Windows Hardware Quality Labs, and block unsigned and unapproved scripts, MSIs, Store apps and .NET applications.

WDAC, App Control for Business and Smart App Control
Three names cause most of the confusion:
- WDAC is the original name, still used in many tools and articles.
- App Control for Business is the current Microsoft name for the same technology, aimed at managed business devices.
- Smart App Control is a simpler, consumer-oriented feature. Per Microsoft, starting with Windows 11 version 22H2 it brings application control to consumers and to some small businesses with simpler app portfolios. It allows signed code or code predicted to be safe by Microsoft's cloud security service.
If you run a mixed fleet with line-of-business software, custom tools or a handful of older applications, you will almost certainly want the managed, policy-driven version rather than Smart App Control.
How WDAC policies work
A WDAC policy is a statement of trust. Microsoft's guidance says the first design step is to define a "circle of trust": a natural-language description of the business intent of the policy that then guides the actual rules in the policy XML. Write that sentence before you open any tool. For example: "Run Windows, Microsoft 365, our line-of-business apps deployed by Intune, and signed drivers. Nothing else."
Microsoft also ships example policies. The DefaultWindows example, found under the Windows schemas folder for Code Integrity, sets a circle of trust that allows Windows, third-party hardware and software kernel drivers, and applications from the Microsoft Store. That is a reasonable starting point to learn from, though most businesses need to add their own software.
Policy rule options
Policy rule options change how the whole policy behaves. The ones most SMBs meet first, as documented by Microsoft, are:
| Option | What it does | Why you would care |
|---|---|---|
| Enabled:UMCI | Restricts user-mode binaries as well as kernel-mode | Without it, only drivers and kernel code are controlled |
| Required:WHQL | Requires every driver to be WHQL signed | Blocks unvetted drivers |
| Enabled:Audit Mode | Logs what would be blocked without blocking it | Your safe testing mode |
| Disabled:Script Enforcement | Turns off script enforcement for PowerShell, wscript, cscript, mshta and MSXML | Usually something to avoid unless you have a specific reason |
| Enabled:Managed Installer | Automatically allows apps installed by a designated managed installer | Cuts rule maintenance for centrally deployed software |
| Enabled:Intelligent Security Graph Authorization | Automatically allows apps with a known-good reputation | Reduces rules for common software |
File rule levels
Rules identify what is trusted. The same Microsoft page lists the file rule levels: hash, file name, file path, publisher and certificate-based rules. They trade precision against upkeep:
- Hash rules are exact but fragile. Every update changes the hash.
- Publisher or certificate rules trust software signed by a given vendor. Microsoft notes that rules based on the publisher's code-signing certificates give the most resiliency against app changes, while hash or file-attribute rules often need updating when the app changes.
- Path rules are convenient but only as safe as the folder permissions behind them.
A sensible SMB policy leans on publisher rules and a managed installer, with a small number of explicit exceptions for unsigned legacy tools.
Is your business ready for it?
Application control rewards organizations that already know what runs on their machines. Microsoft's design guidance says organizations that centrally manage all their apps are the best fit, because options like managed installer make it easy to authorize whatever your distribution tool deploys. Where users can freely download and install apps, the same guidance suggests deploying in audit mode to learn what is running without hurting productivity.
Before you write a policy, work through this short readiness list:
- Inventory. List the applications actually in use, including the quiet ones: accounting add-ins, scanner utilities, vendor remote-support tools, scripts someone wrote years ago. If you suspect more is out there than you know about, our guide to shadow IT discovery is a good first step.
- Deployment path. Decide how software reaches devices: Intune, Configuration Manager, or hand installs. The fewer paths, the simpler the policy.
- Management plane. Confirm devices are enrolled and you can push a policy to a pilot group. If your Intune setup is still maturing, our Intune app protection guide for SMBs covers related groundwork.
- Owner. Name one person who approves exceptions. Without one, every blocked app becomes a ticket that sits.
- Rollback plan. Know how you will remove or relax a policy on a device that cannot launch something critical.
The Australian Cyber Security Centre's small business guidance gives the same advice in plain terms: put application control in audit mode first and track events in Event Viewer. If business-critical applications would be blocked once enforced, it suggests using the WDAC wizard to create explicit allow rules.
A rollout plan that does not lock your team out
Microsoft's deployment guidance is consistent: convert policies to binary before deployment, identify devices and split them into deployment rings, define success criteria, and deploy in audit mode before enforcement, monitoring events before you widen the rollout. Policies can be delivered through an MDM such as Intune, through Configuration Manager, by script or through group policy.
Microsoft's own lifecycle for policy management translates into these steps for a smaller business.
Step 1: Define the circle of trust and build an audit policy
Start from a Microsoft example policy or the wizard, add the options you need (UMCI, managed installer, audit mode) and write down the business intent in one paragraph.
Step 2: Deploy to a pilot ring
Pick a handful of devices that represent your real work: one from finance, one from operations, one IT machine, one that is used by someone who installs odd tools. Do not pilot only on IT's laptops, because they are the least typical.
Step 3: Read the audit events
Audit mode logs what would have been blocked. Review those entries in the Code Integrity operational log in Event Viewer. Sort them into three buckets: software you want (add a rule), software you did not know about (investigate), and software you do not want (leave it to be blocked later). Reviewing logs on a schedule is also a habit auditors expect from mature security programs, as in these logging and monitoring expectations.

Step 4: Iterate until the noise matches expectations
Microsoft's lifecycle says to keep adjusting until the remaining audit events match what you expect. Expect several cycles. A single week of data usually misses month-end tools and quarterly utilities, so let the pilot run through at least one full business cycle.
Step 5: Generate the enforced policy and stage it
Switch audit mode off in a new version of the policy and deploy it by rings again, starting with the pilot group. Keep the audit-mode version handy so you can fall back.
Step 6: Repeat when trust changes
New software, a new vendor or a new line-of-business app means a policy change. Build that into your change process rather than treating the first enforcement as the finish line.
Deploying with Configuration Manager
If you still run Configuration Manager, it offers two modes: enforcement enabled, where only trusted executables run, and audit only, which allows everything to run but logs untrusted executables in the local client event log. Microsoft lists what typically runs under such a policy, including Windows components, WHQL-signed drivers, Store apps, the Configuration Manager client and software deployed through it.
Checking that a policy is active
After deployment, confirm each pilot device actually loaded the policy rather than assuming it did. Open the Code Integrity operational log in Event Viewer and look for the policy-loaded entry and then for block or would-block entries. Microsoft's deployment guidance ties success to defined criteria and monitored events, so write down what "working" means before the pilot starts: for example, no unexpected block events for two weeks and no help-desk tickets about blocked tools.
One behavior worth knowing so it does not alarm you: when Smart App Control is on, or when you enable App Control with the Intelligent Security Graph, Microsoft Defender Antivirus is placed in passive or hybrid mode on systems that use a non-Microsoft antivirus for real-time protection. Microsoft states this is expected behavior, not a bug or a misconfiguration.
The upkeep you should plan for
Application control is not a set-and-forget feature, and a small team should budget for that honestly. The recurring work looks like this:
- Rule updates when software changes. Publisher rules absorb most updates. Hash and file-attribute rules do not.
- Version control. Microsoft recommends storing policies in a version-controlled repository accessible to every administrator who manages them. Even a private Git repository beats a shared folder of files named "final_v3".
- A managed installer. Microsoft notes that using a managed installer to deploy all apps and their updates minimizes the need to update policies. One practical wrinkle: applications installed before you turned the managed installer on will not be recognized automatically, so expect events for your existing estate during the first cycles.
- Exception handling. Decide in advance how long a request for a new app should take and who signs off.
- Change discipline. Policy changes should be tracked and reversible. The same mindset behind reversible Windows changes applies: know what changed, when, and how to undo it.
Where the effort concentrates
The heaviest lift comes at the start, because application control forces you to be explicit about what you trust. Teams that begin with hash rules for everything discover the burden quickly; teams that move toward publisher rules and a managed installer see it fall. If you have custom software built in-house, signing your builds consistently makes your own tools much easier to allow.
Where WDAC fits in the rest of your security program
Application control is one layer. It does not replace patching, identity controls or backups, and it will not fix a weak admin account. Pair it with identity hardening (see our Entra security best practices) and a baseline for your cloud tenant (our Microsoft 365 security baseline guide). Think of those controls as covering different failure modes: identity stops the wrong person getting in, application control stops the wrong code running once someone is.
Our perspective
We see the same pattern at smaller companies: someone reads that application control would have stopped a past incident, switches on enforcement for everyone, and spends the next week fielding calls about blocked tools. The feature is not the problem. The sequence is.
Our approach to any control that can interrupt work is the one we use for AI agents too: ship it with monitoring, a rollback path and a human checkpoint from day one. For application control, that means audit mode, a pilot ring that includes a few ordinary users, a named person who approves exceptions, and a plain-language record of what you chose to trust and why.
We also believe the policy and the plan should belong to you, not to a consultant. The documents should be readable by the next person who inherits them, and the roadmap should rank work by risk and effort so a small team can actually finish it.
jaras
Where Mindpod can help
If you want a second set of eyes before you enforce anything, we start every engagement with a free technology assessment. It produces a prioritized, plain-language plan that you own, covering where application control sits among your other security and resilience work. We can then deliver and run the work with you. Our security assessment and hardening work and our fractional CTO engagements are built for companies that want enterprise-grade practices without a large internal team.

You can start with a free assessment at Mindpod Technologies and tell us what you run today.
FAQ
Is Windows Defender Application Control the same as Microsoft Defender Antivirus?
No. Antivirus detects and blocks threats it recognizes or predicts, while application control enforces an allow list of what may run at all. Microsoft describes the two as working alongside each other, with application control restricting code even in the kernel.
What is the difference between WDAC and App Control for Business?
They are the same technology under two names. Microsoft's current documentation uses App Control for Business, while many tools, policy files and older articles still say WDAC.
Can I try WDAC without blocking my users?
Yes. Audit mode logs what would have been blocked while letting everything run. Microsoft and the Australian Cyber Security Centre both recommend starting there and reviewing events in Event Viewer before you switch to enforcement.
How do I deploy a WDAC policy?
Convert the policy to binary, then push it through an MDM such as Intune, through Configuration Manager, by script or through group policy. Roll it out in rings, starting with a pilot group, and define success criteria beforehand.
Why do apps get blocked even though Intune installed them?
If an app was installed before you enabled a managed installer, the policy does not automatically trust it, even when the same tool deployed it. Add rules for existing software, preferably publisher-based, and let the managed installer handle new installs.
Sources
- Application Control for Windows, Microsoft Learn
- Understand App Control for Business policy rules and file rules, Microsoft Learn
- Understand Windows Defender Application Control policy design decisions, Microsoft Learn
- Deploying App Control for Business policies, Microsoft Learn
- Plan for App Control policy management, Microsoft Learn
- Manage Windows Defender Application Control with Configuration Manager, Microsoft Learn
- Technical example: Application control, Cyber.gov.au
- Windows Defender application control, ASD's Blueprint for Secure Cloud
