T1562

Impair Defenses

Defense Evasion Last updated:

Adversaries may maliciously modify components of a victim environment in order to hinder or disable defensive mechanisms. This not only involves impairing preventative defenses, such as firewalls and anti-virus, but also detection capabilities that defenders can use to audit activity and identify malicious behavior. This may span both native defenses as well as supplemental capabilities installed by users and administrators. Adversaries may also impair routine operations that contribute to defensive hygiene, such as blocking users from logging out, preventing a system from shutting down, or disabling or modifying the update process.

What is T1562 Impair Defenses?

Impair Defenses (T1562) maps to the Defense Evasion tactic — the adversary is trying to avoid being detected in MITRE ATT&CK.

This page provides production-ready detection logic for Impair Defenses, covering the data sources and telemetry it touches: Process: Process Creation, Command: Command Execution, Windows Registry: Windows Registry Key Modification, Microsoft Defender for Endpoint. The queries below are rated high severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Defense Evasion
Technique
T1562 Impair Defenses
Canonical reference
https://attack.mitre.org/techniques/T1562/
Microsoft Sentinel / Defender
kusto
let SecurityServiceNames = dynamic(["WinDefend", "MsMpSvc", "Sense", "WdNisSvc", "WdNisDrv", "WdFilter", "WdBoot", "SecurityHealthService", "wscsvc", "EventLog", "MpsSvc"]);
let SuspiciousCommands = dynamic(["sc stop", "sc config", "net stop", "taskkill", "Set-MpPreference", "DisableRealtimeMonitoring", "DisableBehaviorMonitoring", "Remove-MpPreference", "auditpol /clear", "auditpol /set", "wevtutil cl", "bcdedit /set", "netsh advfirewall set"]);
union DeviceProcessEvents, DeviceRegistryEvents
| where Timestamp > ago(24h)
| extend CommandLine = coalesce(ProcessCommandLine, "")
| where CommandLine has_any (SuspiciousCommands)
   or (ActionType == "RegistryValueSet" and RegistryKey has_any ("WinDefend", "EventLog", "SecurityHealth", "MpsSvc"))
| extend StoppedService = extract(@"(?:sc\s+(?:stop|config)|net\s+stop)\s+([\w]+)", 1, CommandLine)
| extend IsSecurityService = StoppedService in (SecurityServiceNames)
| project Timestamp, DeviceName, AccountName, ActionType, CommandLine, RegistryKey, RegistryValueName, RegistryValueData, StoppedService, IsSecurityService
| sort by Timestamp desc

Broad detection for defense impairment activities across Windows endpoints. Monitors for security service stopping, firewall modifications, event log clearing, audit policy changes, safe mode boot changes, and Defender preference modifications. Combines process creation and registry events for comprehensive coverage.

high severity medium confidence

Data Sources

Process: Process Creation Command: Command Execution Windows Registry: Windows Registry Key Modification Microsoft Defender for Endpoint

Required Tables

DeviceProcessEvents DeviceRegistryEvents

False Positives

  • IT administrators performing legitimate maintenance or reconfiguration of security tools during planned change windows
  • Endpoint management tools (SCCM, Intune, GPO) updating Defender exclusions or policies
  • Security tool upgrades that temporarily stop and restart services

Sigma rule & cross-platform mapping

The detection logic for Impair Defenses (T1562) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  category: process_creation
  product: windows

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Stop Windows Defender Service

    Expected signal: Sysmon Event ID 1: Process Create with CommandLine 'sc stop WinDefend'. System Event ID 7036: Windows Defender Antivirus Service entered the stopped state. Security Event ID 4688 if command line auditing enabled.

  2. Test 2Clear Security Event Log

    Expected signal: Security Event ID 1102: The audit log was cleared. Sysmon Event ID 1: Process Create with CommandLine 'wevtutil cl Security'.

  3. Test 3Disable Audit Policy

    Expected signal: Security Event ID 4719: System audit policy was changed. Sysmon Event ID 1: Process Create with CommandLine 'auditpol /clear /y'.


Response Playbook

Triage

  1. Identify which defensive component was targeted — was it AV/EDR, event logging, firewall, or audit policy?
  2. Check the user context — is this a privileged admin account with a corresponding change ticket, or an unexpected user?
  3. Determine if the impairment was successful — did the service actually stop, was the registry key changed, was the log cleared?
  4. Look for temporal correlation — did other suspicious activity occur immediately before or after the defensive impairment?
  5. Check for lateral movement indicators — was the same impairment command executed across multiple hosts?

Containment

  1. If EDR/AV was disabled: immediately isolate the endpoint via network segmentation or EDR isolation capability
  2. If event logging was cleared or disabled: preserve remaining logs from SIEM, begin forensic imaging of the endpoint
  3. If firewall was disabled: re-enable firewall rules and block any newly opened ports at the network perimeter
  4. If audit policy was modified: restore audit policy from GPO baseline and force a gpupdate
  5. If multiple hosts affected: consider domain-wide credential reset and hunting for persistence mechanisms

Evidence Collection

  1. Windows Security Event Log — Event ID 1102 (log cleared), 4719 (audit policy changed), 4688 (process creation)
  2. System Event Log — Event ID 7036 (service state change), 7040 (service start type changed), 7045 (new service installed)
  3. Sysmon Event ID 1 (process creation), Event ID 12/13 (registry modifications)
  4. PowerShell ScriptBlock Logging — Event ID 4104 for Set-MpPreference or other Defender modification commands
  5. Registry hives — HKLM\SYSTEM\CurrentControlSet\Services for service configuration changes
  6. Memory forensics — volatile data may reveal in-memory hooks or patches to security tool DLLs

Escalation Criteria

  • ! Multiple defense impairment techniques observed on the same host within a short time window (kill chain progression)
  • ! Defense impairment followed by data exfiltration, lateral movement, or encryption activity
  • ! Impairment detected on domain controllers, critical servers, or privileged access workstations
  • ! Unknown or compromised account performing the impairment
  • ! Evidence of BYOVD (Bring Your Own Vulnerable Driver) used to disable security tools at kernel level

Investigation Guide

Forensic Artifacts

  • > Registry: HKLM\SYSTEM\CurrentControlSet\Services\<ServiceName>\Start — service start type values
  • > Registry: HKLM\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-* — event log autologger configuration
  • > Registry: HKLM\SOFTWARE\Microsoft\Windows Defender — Defender configuration and exclusions
  • > File System: C:\Windows\System32\winevt\Logs\ — event log files (.evtx) for timeline analysis
  • > Event Log: Security Event ID 1102 — provides the account that cleared the log
  • > WMI: Win32_Service for current service states and start types

Tuning Guidance

This parent detection is intentionally broad. Start by correlating alerts with your change management system — legitimate maintenance should have corresponding tickets. Build an allowlist for known admin accounts and their typical maintenance patterns. Consider splitting this into sub-detections per impairment category (service stopping, log clearing, firewall modification) for more granular tuning. Exclude known endpoint management tool service accounts (SCCM, Intune agent accounts) but only by exact account name match, never by command pattern.


Hunting Queries

Hunt for accounts or processes that have attempted to stop or reconfigure security services across the environment. High counts or multiple affected devices indicate coordinated defense impairment.

Hunting — KQL
kql
DeviceProcessEvents
| where Timestamp > ago(7d)
| where ProcessCommandLine has_any ("sc stop", "sc config", "net stop", "taskkill")
| where ProcessCommandLine has_any ("WinDefend", "Sense", "MsMpSvc", "SecurityHealth", "EventLog", "CrowdStrike", "Carbon", "Tanium", "Sentinel")
| summarize Count=count(), Devices=dcount(DeviceName) by AccountName, ProcessCommandLine
| sort by Count desc
Hunting — SPL
spl
index=wineventlog sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 (CommandLine="*sc stop*" OR CommandLine="*sc config*" OR CommandLine="*net stop*" OR CommandLine="*taskkill*") (CommandLine="*WinDefend*" OR CommandLine="*Sense*" OR CommandLine="*MsMpSvc*" OR CommandLine="*SecurityHealth*" OR CommandLine="*EventLog*" OR CommandLine="*CrowdStrike*")
| stats count as Count, dc(host) as Devices by User, CommandLine
| sort - Count

Hunt for registry modifications targeting Windows Defender settings or event log autologger configuration. These modifications can silently disable security monitoring without stopping services.

Hunting — KQL
kql
DeviceRegistryEvents
| where Timestamp > ago(7d)
| where RegistryKey has "Windows Defender" or RegistryKey has "WMI\\Autologger\\EventLog"
| where ActionType == "RegistryValueSet"
| where RegistryValueName in ("DisableRealtimeMonitoring", "DisableBehaviorMonitoring", "Start", "Enabled", "DisableAntiSpyware")
| project Timestamp, DeviceName, AccountName, RegistryKey, RegistryValueName, RegistryValueData
| sort by Timestamp desc
Hunting — SPL
spl
index=wineventlog sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" (EventCode=13 OR EventCode=14) (TargetObject="*Windows Defender*" OR TargetObject="*Autologger*EventLog*") (TargetObject="*DisableRealtimeMonitoring*" OR TargetObject="*DisableBehaviorMonitoring*" OR TargetObject="*DisableAntiSpyware*" OR TargetObject="*Start*" OR TargetObject="*Enabled*")
| table _time, host, User, EventCode, TargetObject, Details
| sort - _time

Atomic Red Team Tests

Test 1 Stop Windows Defender Service
windows

Attempts to stop the Windows Defender service using sc.exe. This simulates ransomware and malware that disable AV before deploying payloads. Requires elevated privileges.

Command

powershell
sc stop WinDefend

Cleanup

powershell
sc start WinDefend

Expected Telemetry

Sysmon Event ID 1: Process Create with CommandLine 'sc stop WinDefend'. System Event ID 7036: Windows Defender Antivirus Service entered the stopped state. Security Event ID 4688 if command line auditing enabled.

Expected Detection

Alert fires on 'sc stop' + 'WinDefend' pattern. KQL: StoppedService='WinDefend', IsSecurityService=true. SPL: action='service_tampering'.

Test 2 Clear Security Event Log
windows

Clears the Windows Security event log using wevtutil. This is a common post-exploitation technique to cover tracks. Generates Security Event ID 1102.

Command

powershell
wevtutil cl Security

Expected Telemetry

Security Event ID 1102: The audit log was cleared. Sysmon Event ID 1: Process Create with CommandLine 'wevtutil cl Security'.

Expected Detection

Alert fires on 'wevtutil cl' pattern and Event ID 1102. SPL: action='log_cleared' or action='log_tampering'.

Test 3 Disable Audit Policy
windows

Uses auditpol to clear all audit policies, preventing Windows from logging security events. This technique was used by Magic Hound (APT35) to evade detection.

Command

powershell
auditpol /clear /y

Cleanup

powershell
auditpol /set /category:* /success:enable /failure:enable

Expected Telemetry

Security Event ID 4719: System audit policy was changed. Sysmon Event ID 1: Process Create with CommandLine 'auditpol /clear /y'.

Expected Detection

Alert fires on 'auditpol /clear' pattern and Event ID 4719. SPL: action='audit_policy_changed' or action='log_tampering'.

Related Detections