T1562.006
Indicator Blocking
Adversaries may attempt to block indicators or events typically captured by sensors from being gathered and analyzed. This includes tampering with Event Tracing for Windows (ETW), disabling crash dumps, modifying syslog configuration, redirecting telemetry, or blocking network traffic to SIEM/logging infrastructure. ETW tampering is particularly impactful as many security tools depend on ETW providers for visibility.
Microsoft Sentinel / Defender
kusto
let ETWTampering = dynamic(["Set-EtwTraceProvider", "logman stop", "logman delete", "logman update", "Remove-EtwTraceProvider", "EtwEventWrite", "NtTraceEvent", "NtTraceControl"]);
let CrashDumpTampering = dynamic(["CrashDumpEnabled", "NMICrashDump"]);
let SyslogTampering = dynamic(["systemctl stop rsyslog", "systemctl stop syslog-ng", "service rsyslog stop", "service syslog stop", "esxcli system syslog"]);
let IndicatorBlocking = dynamic(["Set-EtwTraceProvider", "logman stop", "logman delete", "CrashDumpEnabled", "systemctl stop rsyslog", "systemctl stop syslog-ng", "service rsyslog stop"]);
union DeviceProcessEvents, DeviceRegistryEvents
| where Timestamp > ago(24h)
| where ProcessCommandLine has_any (IndicatorBlocking)
or ProcessCommandLine has_any (ETWTampering)
or ProcessCommandLine has_any (SyslogTampering)
or (ActionType == "RegistryValueSet" and RegistryKey has "CrashControl" and RegistryValueName has_any (CrashDumpTampering))
| extend BlockingType = case(
ProcessCommandLine has_any ("Set-EtwTraceProvider", "logman stop", "logman delete", "logman update", "Remove-EtwTraceProvider"), "ETW Tampering",
ProcessCommandLine has_any ("EtwEventWrite", "NtTraceEvent", "NtTraceControl"), "ETW API Patching",
RegistryValueName has "CrashDumpEnabled" or ProcessCommandLine has "CrashDumpEnabled", "Crash Dump Disabled",
ProcessCommandLine has_any ("rsyslog", "syslog-ng", "syslog"), "Syslog Tampering",
"Other")
| project Timestamp, DeviceName, AccountName, BlockingType, ProcessCommandLine, RegistryKey, RegistryValueName, RegistryValueData, InitiatingProcessFileName
| sort by Timestamp desc high severity
high confidence
Data Sources
Process: Process Creation Command: Command Execution Windows Registry: Windows Registry Key Modification Sensor Health: Host Status
Required Tables
DeviceProcessEvents DeviceRegistryEvents
False Positives
- Performance engineers using logman to manage ETW trace sessions for diagnostics
- System administrators configuring crash dump settings for disk space management on servers
- Security teams intentionally modifying ETW providers during tuning or testing
Last updated: 2026-04-21 Research depth: deep
References (5)
- https://attack.mitre.org/techniques/T1562/006/
- https://medium.com/palantir/tampering-with-windows-event-tracing-background-offense-and-defense-4be7ac62ac63
- https://www.mdsec.co.uk/2020/12/bypassing-user-mode-hooks-and-direct-invocation-of-system-calls-for-red-teams/
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1562.006/T1562.006.md
- https://posts.specterops.io/data-source-analysis-and-dynamic-windows-re-authentication-a-]
Unlock Pro Content
Get the full detection package for T1562.006 including response playbook, investigation guide, and atomic red team tests.
Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance
Related Detections
Parent Technique
T1562Impair DefensesRelated Sub-techniques
T1562.001Disable or Modify ToolsT1562.002Disable Windows Event LoggingT1562.003Impair Command History LoggingT1562.004Disable or Modify System FirewallT1562.007Disable or Modify Cloud FirewallT1562.008Disable or Modify Cloud LogsT1562.009Safe Mode BootT1562.010Downgrade AttackT1562.011Spoof Security AlertingT1562.012Disable or Modify Linux Audit SystemT1562.013Disable or Modify Network Device Firewall