Windows Defender Disabled via Registry Modification
editWindows Defender Disabled via Registry Modification
editIdentifies modifications to the Windows Defender registry settings to disable the service or set the service to be started manually.
Rule type: eql
Rule indices:
- winlogbeat-*
- logs-endpoint.events.*
- logs-windows.*
Severity: low
Risk score: 21
Runs every: 5 minutes
Searches indices from: now-9m (Date Math format, see also Additional look-back time)
Maximum alerts per execution: 100
References:
Tags:
- Elastic
- Host
- Windows
- Threat Detection
- Defense Evasion
Version: 2 (version history)
Added (Elastic Stack release): 7.12.0
Last modified (Elastic Stack release): 7.13.0
Rule authors: Elastic
Rule license: Elastic License v2
Investigation guide
editTriage and analysis
Detections should be investigated to identify if the hosts and users are authorized to use this tool. As this rule detects post-exploitation process activity, investigations into this should be prioritized
Rule query
editregistry where event.type in ("creation", "change") and
((registry.path:"HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows
Defender\\DisableAntiSpyware" and registry.data.strings:"1") or
(registry.path:"HKLM\\System\\ControlSet*\\Services\\WinDefend\\Start"
and registry.data.strings in ("3", "4")))
Threat mapping
editFramework: MITRE ATT&CKTM
-
Tactic:
- Name: Defense Evasion
- ID: TA0005
- Reference URL: https://attack.mitre.org/tactics/TA0005/
-
Technique:
- Name: Impair Defenses
- ID: T1562
- Reference URL: https://attack.mitre.org/techniques/T1562/
Rule version history
edit- Version 2 (7.13.0 release)
-
- Formatting only