Windows Registry: Windows Defender Exclusions Key Modified via ObjectName Match

Alerts on registry value changes under the Windows Defender Exclusions key in Windows Security event 4657.

FreeReviewedSigma · Medium · v2

Product: windows
Service: security
Author: @BarryShooshooga (SigmaHQ), DRL 1.1
Published: 2019-10-26
Updated: 2026-07-31

ATT&CK techniques

Recon
Resource Dev
Initial Access
Execution
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
Impact

What it detects

This rule flags Security event 4657 where a registry value modification targets a path under \Microsoft\Windows Defender\Exclusions\, indicating changes to Windows Defender’s configured exclusions. Attackers may use exclusions to reduce scanning and hinder detection of malicious files or locations. It relies on Windows Security auditing for registry value modifications (EventID 4657) and the presence of the Defender exclusions registry path in the event’s ObjectName field.

Reporting behind it

Related detections9 linkedT1685 — drag to rearrange

Suspicious Windows Defender Exclusion via Add-MpPreference (via process_creation)

Malicious Windows Defender Service Tampering via PowerShell (via process_creation)

Windows Defender Disabled via DisableAntiSpyware Registry Key

Suspicious Vulnerable Intel Ethernet Driver Load for BYOVD via SCATTERED SPIDER (via driver_load)

Malicious Defender Disable And Executable Exclusion Via Registry

Malicious UAC Disable via EnableLUA Registry Modification (via registry_set)

Malicious AMSI and ETW Patching via PowerShell Script

Malicious PowMix AMSI Bypass via amsiInitFailed

Suspicious ThrottleStop Driver Abuse for Defense Evasion in Ransomware Attacks

Windows Registry: Windows Defender Exclusions Key Modified via ObjectName Match

Pivot detection · T1685 · 9 related

Changelog

v2
Candidate ingested via manual entry.2026-07-31
v1
No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.

windows-security-log-windows-defender-exclusions-registry-key-value-modified-46a68649

title: "Windows Registry: Windows Defender Exclusions Key Modified via ObjectName Match"
id: e0cfc5d6-4b2c-4dcc-87c4-07a368d74043
related:
  - id: e9c8808f-4cfb-4ba9-97d4-e5f3beaa244d
    type: derived
  - id: a33f8808-2812-4373-ae95-8cfb82134978
    type: derived
  - id: 46a68649-f218-4f86-aea1-16a759d81820
    type: derived
status: test
description: This rule flags Security event 4657 where a registry value modification targets a path under \Microsoft\Windows Defender\Exclusions\, indicating changes to Windows Defender’s configured exclusions. Attackers may use exclusions to reduce scanning and hinder detection of malicious files or locations. It relies on Windows Security auditing for registry value modifications (EventID 4657) and the presence of the Defender exclusions registry path in the event’s ObjectName field.
references:
  - https://www.bleepingcomputer.com/news/security/gootkit-malware-bypasses-windows-defender-by-setting-path-exclusions/
  - https://github.com/SigmaHQ/sigma/blob/master/rules/windows/builtin/security/win_security_windows_defender_exclusions_registry_modified.yml
author: "@BarryShooshooga, Huntrule Team"
date: 2019-10-26
modified: 2023-11-11
tags:
  - attack.defense-impairment
  - attack.t1685
logsource:
  product: windows
  service: security
  definition: "Requirements: Audit Policy : Security Settings/Local Policies/Audit Policy, Registry System Access Control (SACL): Auditing/User"
detection:
  selection:
    EventID: 4657
    ObjectName|contains: \Microsoft\Windows Defender\Exclusions\
  condition: selection
falsepositives:
  - Intended exclusions by administrators
level: medium
license: DRL-1.1

Convert

This rule as a query you can run. Uses no unlock credit.

SplunkSPL