Attack surface reduction (ASR) rules are Microsoft Defender settings that block risky software behavior on Windows, such as Office apps spawning child processes, obfuscated scripts and code injection. The safe way to deploy them is to turn on Microsoft's standard protection rules in Block mode, run the rest in Audit mode on a small pilot group, add narrow exclusions, and then move rules to Block one at a time. This guide shows you how, using Intune, Group Policy or PowerShell.
TL;DR
- ASR rules target behaviors attackers commonly abuse, not specific malware files, so they work on threats your antivirus has never seen.
- Microsoft recommends the standard protection rules in Block mode without extensive testing. Run the other rules in Audit mode first.
- Intune endpoint security policy is the recommended way to manage ASR rules. Group Policy and PowerShell work for local or unmanaged setups.
- Use per-rule exclusions and Warn mode to handle false positives. Do not switch a rule off to make one app work.
- Watch Event IDs 1121, 1122, 1129 and 5007 in Event Viewer to see what the rules are doing.
Table of Contents
- What ASR rules actually do
- The rules worth knowing first
- Understand the four modes before you touch a policy
- A deployment plan that avoids a help-desk flood
- How to configure ASR rules
- Handle exclusions without gutting the rule
- Monitor events and troubleshoot
- Where ASR rules fit in your wider security baseline
- Get a second pair of eyes on your rollout
- FAQ
- Sources
What ASR rules actually do
ASR rules in Microsoft Defender Antivirus target risky software behavior on Windows devices that attackers commonly exploit through malware. The examples Microsoft lists include launching executables and scripts that try to download or run files, running obfuscated or otherwise untrusted scripts, creating child processes from potentially vulnerable applications, and injecting code into other processes.
That framing matters for a small business. Patching and antivirus signatures deal with known problems. ASR rules deal with the way attacks run. A Word document that launches PowerShell, for instance, is rarely something your accounting team needs. Blocking that behavior removes an opportunity for the attacker, which is the idea behind attack surface reduction in Defender for Endpoint: eliminate risky or unnecessary behaviors on devices rather than only reacting to them.
What you need before you start
The rules are available on any Windows edition that includes Microsoft Defender Antivirus. You can set them locally with PowerShell or Group Policy. For central management you can use Microsoft Intune, Microsoft Configuration Manager or the Microsoft Defender portal. Microsoft's overview notes that endpoint security policies in Intune are the recommended method.
For most smaller companies already running Microsoft 365, that means Intune. If you do not yet have a device inventory, build one first. You cannot pilot a rule on a ring of devices you cannot name.
The rules worth knowing first
Microsoft's rules reference lists every rule with its GUID, category and a detailed description with examples of what it blocks. Each rule is controlled by its GUID, which is what you will see in Group Policy and PowerShell. A few from Microsoft's documentation:
| Rule | GUID | What it addresses |
|---|---|---|
| Block abuse of exploited vulnerable signed drivers (Device) | 56a863a9-875e-4185-98a7-b882c64b5ce5 | Standard protection rule |
| Block credential stealing from the Windows local security authority subsystem | 9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2 | Standard protection rule |
| Block execution of potentially obfuscated scripts | 5beb7efe-fd9a-4556-801d-275e5ffc04cc | Other ASR rule |
| Block JavaScript or VBScript from launching downloaded executable content | d3e037e1-3eb8-44c8-a917-57927947596d | Other ASR rule |
| Use advanced protection against ransomware | c1db55ab-c21a-4637-bb3f-a12568109d35 | Other ASR rule |
These come from Microsoft's overview and reference pages. The full list is longer, and it changes as Microsoft adds rules, so copy GUIDs from the reference page rather than from a blog post or an old script.
Understand the four modes before you touch a policy
Every rule has a state. In Group Policy you set the state by pairing the rule GUID with a mode value:
- 0: Off
- 1: Block
- 2: Audit
- 5: Not configured
- 6: Warn
Audit mode is your safety net. Per Microsoft's test guidance, it does not affect users but generates logged events you can evaluate. Warn mode blocks the action but lets the user override it. Block is the finished state.
A deployment plan that avoids a help-desk flood
Step 1: Block the standard protection rules
Microsoft recommends enabling the standard protection rules in Block mode without the need for extensive testing, because they typically have minimal or no noticeable effect on users. There are documented exceptions, including WMI event subscription persistence when you use Configuration Manager, so read the rule notes before you apply them to a fleet that uses it.
This gives you a quick win. Two of the five rules in the table above are standard protection rules, and getting them live in a day is better than waiting weeks for a perfect plan.
Step 2: Put the remaining rules in Audit mode on a pilot ring
Microsoft typically recommends enabling all ASR rules in Audit mode at the same time, starting with ring 1 champions or devices. Choose a pilot group that mixes roles: someone in finance, someone who lives in Excel macros, an IT person, a salesperson who uses a line-of-business app. A pilot of only IT staff tells you very little.
Let it run long enough to cover a full business cycle. Month-end close, payroll runs and any quarterly reporting scripts are the things that surface late.
Step 3: Review the audit events
Review triggered events with the reporting methods available to you, including Event ID 1122 in Windows Event Viewer. For each event, ask three questions:
- Is this a legitimate business process?
- Is the file or folder specific enough to exclude narrowly?
- Could the process be changed so it no longer needs the risky behavior?
Often the answer to the third question is yes. An old macro that launches a script from a temp folder can usually be rewritten. That is a better outcome than an exclusion, because the behavior is gone rather than permitted.
Step 4: Move rules to Block or Warn, one at a time
After audit testing, Microsoft's implementation guide directs you to move some rules to Block or Warn for ring 1 once you have determined the exclusions you need. Start with the rule that has the fewest triggered events, and refine exclusions from activity and your champions' feedback. Then widen to the next ring.
Going one rule at a time costs a little speed and buys you a clean cause when something breaks. If three rules flip on the same morning and an app fails, you are guessing.
How to configure ASR rules
Pick one management path and stick with it. Mixing Intune and Group Policy on the same device invites conflicts you will spend hours untangling.
Intune (recommended)
In Intune, create an endpoint security Attack surface reduction policy, choose Platform: Windows, and select Profile: Attack Surface Reduction Rules. Set each rule to Audit, Block or Warn, assign the policy to a pilot device group, and widen the assignment as you gain confidence. Microsoft's Intune settings reference ties each rule control to its GUID, which helps when you need to match a portal setting to an event or script.

Assign to device groups you can grow in rings, not to "All devices" on day one.
Group Policy
In Group Policy, the settings live under Computer configuration, Administrative templates, Windows components, Microsoft Defender Antivirus, Microsoft Defender Exploit Guard, Attack Surface Reduction. The documented settings include:
- Configure Attack Surface Reduction rules
- Exclude files and paths from Attack surface reduction rules
- Apply a list of exclusions to specific attack surface reduction (ASR) rules
In the first setting you enter each rule's GUID and the mode value from the list above.
PowerShell
In an elevated session, use Add-MpPreference, Set-MpPreference or Remove-MpPreference with the -AttackSurfaceReductionRules_Ids and -AttackSurfaceReductionRules_Actions parameters, as Microsoft documents. PowerShell is handy for a single test machine or a quick lab. Be careful with Set-MpPreference: Microsoft's cmdlet set replaces what is configured, while Add-MpPreference appends, so check which one you are running before you press Enter.
Handle exclusions without gutting the rule
Exclusions are where good ASR deployments go wrong. Microsoft explains that per-rule exclusions apply only to the selected rule, while ASR-only exclusions apply across all ASR rules. A broad exclusion therefore removes protection from every rule, not just the one that annoyed a user.
After you set a rule to Audit, Block or Warn, an "ASR only per rule exclusions" section appears so you can specify exclusions for that rule only. Use it by default.
Here are working habits that keep exclusions small:
- Exclude a specific file or a specific folder, never a drive or a user profile.
- Write down who requested the exclusion, which rule, and why. Review the list quarterly.
- Prefer exclusions to the alternatives. Microsoft says rule exclusions are better than turning rules off or switching them back to Audit, and suggests Warn mode where available to limit disruption without disabling the rule.
If your team also tracks alert noise from other tools, the same discipline applies: tune precisely rather than silence broadly. Guidance on reducing false positive alerts covers that general principle for operations teams.
Monitor events and troubleshoot
When a user reports that something stopped working, resist the urge to turn the rule off. Microsoft's troubleshooting guidance says to switch a misbehaving rule to Audit mode for testing. Audit does not block files or processes, but it records what the rule would have done in Block or Warn.
The same page lists the Event Viewer IDs to check:
| Event ID | Meaning |
|---|---|
| 1121 | A rule blocked something (Block mode) |
| 1122 | A rule would have blocked something (Audit mode) |
| 1129 | A user overrode a Warn-mode prompt |
| 5007 | A configuration change |
Event 5007 is the one people forget. If a rule "stopped working" overnight, a configuration change is a good first suspect: another policy, a script or a person altered the setting. Event 1129 tells you which Warn-mode prompts users click through, which is useful for deciding whether a rule is ready for Block.
Where ASR rules fit in your wider security baseline

ASR rules are one layer. They harden Windows endpoints, but they do not replace identity controls, patching, backups or application control. If you want to decide what to do alongside them, our SMB security hardening checklist picks the first three controls to start with. For a stricter step on which software may run at all, see our practical guide to Windows Defender Application Control.
A reasonable order for a smaller company: identity protection first, standard ASR rules next, then the audited rules, then application control once you know your software estate.
Our perspective
We see the same pattern in small and midsize companies. ASR rules are free to turn on and valuable, yet they sit unused because nobody owns the audit-review step. The technology is not the hard part. Ownership is.
Our advice is to treat ASR as a small project with a named owner, a pilot ring and a review date, not a checkbox in a policy. Start with the standard protection rules, since Microsoft says they rarely affect users, and bank that protection right away. Then spend your effort on the audit events, because that is where you learn how your business really runs.
That is also how we approach security work generally: assess what you have, produce a prioritized plan in plain language that you own, and then build it with monitoring and a way to roll back. A control you can explain to your operations lead is a control that survives staff changes.
jaras
Get a second pair of eyes on your rollout
If you want help sequencing ASR rules with the rest of your Windows and Microsoft 365 hardening, Mindpod Technologies offers security assessment and hardening as part of its advisory work, and engagements start with a free technology assessment that results in a plain-language plan you own. You can book a 30-minute call to talk through your environment.

Bring your device count, your management tool (Intune, Configuration Manager or Group Policy) and the line-of-business apps you worry about. That is enough to outline a pilot ring and an audit period.
FAQ
Do I need Defender for Endpoint to use ASR rules?
Not to configure them. Microsoft states that the rules are available on any Windows edition that includes Microsoft Defender Antivirus, and you can manage them locally with PowerShell or Group Policy. Centralized options include Intune, Configuration Manager and the Microsoft Defender portal.
Should I enable all ASR rules in Block mode right away?
Only the standard protection rules, which Microsoft says typically have minimal or no noticeable effect on users. Put the other rules in Audit mode on a pilot ring first, review the events, add exclusions, and then move them to Block or Warn one at a time.
How do I know if an ASR rule is blocking something?
Check Windows Event Viewer. Event ID 1121 records blocks, 1122 records audit hits, 1129 records a user overriding a Warn prompt, and 5007 records configuration changes. Reviewing these before and after each change shows you the effect of a rule.
What should I do about a false positive?
Add an exclusion for the specific file or folder, scoped to that single rule. Microsoft says exclusions are better than turning the rule off or returning it to Audit. If you need to investigate, switch the rule to Audit temporarily so it logs what it would have done.
Sources
- ASR rules overview, Microsoft Defender for Endpoint
- Attack surface reduction in Microsoft Defender for Endpoint
- ASR rules reference, Microsoft Defender for Endpoint
- Configure ASR rules and exclusions
- Test your ASR rules deployment
- Enable your ASR rules deployment
- Troubleshoot ASR rules
- Intune endpoint security Attack surface reduction settings
