MITRE ATT&CK T1562.001: Understanding the Detection Gap
Detection stack
- AIDR
- Alert
- ETL
- Query
Summary
Attackers use defense evasion techniques to disable or modify security tools and reduce defensive visibility. This can include terminating EDR processes, changing registry keys to suppress logging, or abusing vulnerable drivers to obtain kernel-level access. By impairing security controls early in an intrusion, adversaries gain more time to perform follow-on malicious activity.
Investigation
The report explains how an attacker with local administrator privileges can systematically weaken defenses by killing processes and modifying registry values. One case study highlights the RansomHub EDRKillShifter tool, which abuses a vulnerable driver to gain kernel-level access. Investigation should focus on the process chain responsible for initiating these tampering attempts.
Mitigation
Organizations should implement strong tamper protection to prevent unauthorized modification, deletion, or shutdown of security agent processes and registry settings. Local administrator privileges should be tightly controlled, and changes to security tools should require authenticated authorization. Monitoring for abuse of signed but vulnerable drivers is also critical.
Response
When a tamper alert is detected, treat it as a high-priority event even if the attempt was unsuccessful. Immediately investigate the process chain to identify the initiating process and its parent. Confirm that kernel-level protections remain active and review the surrounding timeframe for additional defense evasion activity.
Attack Flow
Detections
Windows Defender Realtime Protection Process Was Terminated (via sysmon)
Possible BYOVD – Bring Your Own Vulnerable Driver Attack (via file_event)
Suspicious Driver Install (via system)
Possible BYOVD – Bring Your Own Vulnerable Driver Attack (via audit)
Malicious Process Termination Attempt Against Security Tools [Windows Process Creation]
Detection of Security Tool Tampering via Registry Key Deletion or Modification [Windows Registry Event]
Detect Modification of Sysmon’s Registry Values [Windows Sysmon]
Simulation Execution
-
Attack Narrative & Commands: An adversary has gained local administrator privileges and seeks to perform lateral movement or credential dumping. To avoid detection by the EDR/Sysmon, they decide to “silence” the telemetry. Instead of killing the
Sysmon.exeprocess (which would trigger a “Process Terminated” alert), they will perform a stealthy modification to the registry. They will target theStartvalue of the Sysmon service, changing it to4(Disabled), which ensures that upon the next reboot, the service will not start, or they will target theEnableparameter to stop logging immediately. -
Regression Test Script:
# Simulation script to disable Sysmon logging via Registry modification # Note: Must be run as Administrator $registryPath = "HKLM:SYSTEMCurrentControlSetServicesSysmon" $targetValue = "Start" Write-Host "[!] Attempting to modify Sysmon registry value to disable service..." -ForegroundColor Yellow try { # Changing Start value to 4 (Disabled) Set-ItemProperty -Path $registryPath -Name $targetValue -Value 4 -ErrorAction Stop Write-Host "[+] Success: Registry value modified. Detection should trigger." -ForegroundColor Green } catch { Write-Host "[-] Failed to modify registry. Ensure you are running as Administrator." -ForegroundColor Red } -
Cleanup Commands:
# Restore Sysmon Start value to 2 (Automatic) to ensure system stability $registryPath = "HKLM:SYSTEMCurrentControlSetServicesSysmon" Set-ItemProperty -Path $registryPath -Name "Start" -Value 2 Write-Host "[+] System restored. Sysmon service set to Automatic." -ForegroundColor Green