Defender exclusions: close security gaps without disrupting applications
28 October 2026
Review Defender exclusions, restrict who can change them, and set approval and monitoring controls without disrupting legitimate business applications.
Huntress has highlighted how attackers abuse Microsoft Defender Antivirus exclusions to reduce the chance of malware being scanned. Its analysis of exclusion abuse references threats including GootKit and WhisperGate. For Australian businesses using Windows endpoints and servers, the practical issue is broader than any malware family: who can create Defender exclusions, which exceptions remain necessary, and whether unexpected changes trigger investigation.
Removing every exception immediately is not the answer. Some applications need carefully scoped exclusions. The goal is to distinguish documented requirements from inherited workarounds and unauthorised changes, then reduce exposure without interrupting business operations.
Why Defender exclusions deserve a security review
An antivirus exclusion changes what the scanner inspects. Depending on its type, it can exclude particular files, folders, file extensions or files opened by specified processes. These categories have different effects and should not be treated as interchangeable.
For example, a process exclusion generally affects files opened by that process; it does not simply mean the executable itself is excluded from every scan. Microsoft documents these distinctions in its guidance on Microsoft Defender Antivirus exclusions.
A business application may have a genuine compatibility requirement. However, an excluded folder that ordinary users can write to creates a potential hiding place. Excluding an entire drive or a common file extension can create a much wider gap than intended.
Exclusions do not necessarily disable every endpoint protection capability. Antivirus scanning, endpoint detection and response, and other controls have different behaviours. Equally, another security tool being installed is not evidence that an overly broad exception is safe.
Build an inventory of configured and effective exclusions
Start with a read-only assessment, not a bulk configuration change. Cover workstations, servers, shared devices and specialist application hosts. Record which devices are actively protected by Defender Antivirus and which use another antivirus product or operate in passive mode.
On an authorised test device, IT administrators can inspect configured exclusion fields using PowerShell:
```powershell Get-MpPreference | Select-Object ExclusionPath, ExclusionExtension, ExclusionProcess ```
Treat this as one source of evidence, not a complete audit. Visibility can be restricted, automatic server-role exclusions may not appear in these fields, and centrally managed settings need to be checked separately.
Compare endpoint information with Intune, Group Policy, Configuration Manager or whichever platform manages your environment. Include deployment scripts and remote management tooling. Check effective behaviour on representative devices rather than assuming the management console tells the whole story.
For each exception, record:
- Device group and application affected.
- Exclusion type and exact scope.
- Policy or tool that supplies it.
- Business owner and technical owner.
- Supporting vendor documentation or troubleshooting evidence.
- Approval reference, review date and removal criteria.
An exclusion with no identifiable owner is a review priority, not proof of compromise.
Identify everyone who can change Defender exclusions
The authority to change antivirus settings may sit in several places. Local administrators are only one part of the picture. Central policy administrators, remote support operators, deployment services and automation accounts may also influence endpoint configuration.
Map the full change path:
- Local access: identify users and support accounts with administrative rights.
- Policy access: review roles that can edit, assign or deploy endpoint security policies.
- Remote execution: check who can run scripts through remote monitoring and management tools.
- Service identities: inspect unattended accounts and their credential controls.
- Emergency access: confirm how exceptional access is approved, logged and withdrawn.
Check whether local settings can merge with centrally managed exclusions. Where supported and appropriate, prevent unapproved local additions from expanding the approved baseline. Test the result because policy behaviour depends on the management approach and device configuration.
Verify tamper protection too, but do not assume enabling it makes every exclusion change impossible. Exclusion protection has specific prerequisites and management conditions. Validate the applicable Microsoft guidance and test your actual configuration.
Our remote management access checklist covers a related issue: a trusted support platform can become a route for unauthorised security changes if its accounts are compromised.
Prioritise broad and unexplained exceptions
Review Defender exclusions according to their potential impact. A narrowly scoped application requirement is different from a blanket exception added during troubleshooting and never removed.
Start with:
- Whole-drive exclusions or large directory trees.
- Download, temporary and other user-writable locations.
- Broad file-extension exclusions.
- Process exclusions involving general-purpose script engines or interpreters.
- Exceptions applied to every device when only one application server needs them.
- Recent changes without a matching support ticket or deployment record.
For each entry, ask whether an attacker or ordinary user could place content within its scope. Review folder permissions alongside the exclusion itself.
Then verify the application requirement. Vendor advice should match the installed version and workload. A historical recommendation is not automatically appropriate for a current release. Where performance is the stated reason, collect diagnostic evidence before accepting a permanent scanning exception.
Establish approval without creating an operational bottleneck
Use a short, consistent change process for Defender exclusions. Every request should explain the application problem, the proposed scope, the affected devices and why a narrower alternative is unsuitable.
Require a technical reviewer and an accountable approver. In a small business, this might mean the IT provider assesses the configuration while the application owner approves the operational risk. Avoid letting the requester silently approve their own change.
Temporary troubleshooting exclusions need an expiry or a scheduled removal task with a named owner. Permanent exceptions still need periodic review and reassessment after application upgrades.
Keep emergency changes possible, but record the reason, operator and affected devices. Follow them with prompt review. The objective is a traceable decision, not paperwork that encourages staff to bypass the process.
Monitor configuration changes and investigate context
Approval controls need evidence that deployed settings still match the approved baseline. Forward relevant Defender operational logs and management-platform audit logs to your monitoring system where available.
Microsoft Defender Antivirus Event ID 5007 can indicate a configuration change. It is not, by itself, proof of malicious activity or a complete attribution record. Correlate it with policy deployments, administrator sign-ins, remote management activity and endpoint process telemetry where available.
Create alerts for unexpected additions, broader exclusion scope and changes outside approved windows. Assign an owner to investigate them; collecting logs without a response process is not enough.
If a change looks suspicious, preserve evidence and determine whether it came from a legitimate policy deployment, an administrator session or compromised tooling. Investigate activity involving the excluded location. Simply deleting the exception does not establish that the device is clean.
Where there are signs of active compromise, follow your incident process, including isolation where appropriate. Our ransomware response checklist outlines wider containment and recovery considerations.
Test removal before broad deployment
Reduce Defender exclusions in stages. Select representative devices, establish application performance baselines and agree on rollback criteria with the application owner.
Remove or narrow one exception at a time where practical. Test real workflows such as opening shared files, processing transactions, running scheduled jobs and completing backups. Monitor application errors and resource use, not just whether the application launches.
If problems emerge, investigate with the vendor rather than immediately restoring an unnecessarily broad exclusion. Document the final configuration and expand deployment gradually.
Tech Engine can help review your cyber security, including Defender configuration, administrative access and change monitoring. Call 1300 088 324 or email sales@techengine.au to plan a review that accounts for both security exposure and application continuity.
Want this applied to your business?
Request an AI Blueprint and we will map the processes worth automating first.
Request an AI Blueprint