Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
ETW tampering blinds Event Tracing for Windows, the telemetry pipeline most endpoint detection products depend on, so that malicious activity produces no events at all.

What Is ETW Tampering?
Event Tracing for Windows is the high-performance telemetry framework built into the operating system. Providers inside the kernel, inside ntdll, inside the .NET runtime, and inside hundreds of Windows components emit structured events; consumers, including most endpoint detection and response products and Sysmon, subscribe to them. ETW tampering is the deliberate disruption of that pipeline so that the events a defender depends on are never produced or never delivered.
MITRE ATT&CK covers it as T1562.006, Impair Defenses: Indicator Blocking. It is usually deployed in the same breath as an AMSI bypass, for the same reason: together, the two remove script inspection and runtime telemetry, which is most of what a modern agent sees.
EtwEventWrite and NtTraceEvent live in ntdll.dll, mapped into every process. Overwriting the first bytes with a return instruction silences all ETW output from that process. This takes a handful of lines, requires no special privileges, and affects only the attacker’s own process, which makes it hard to notice centrally.Microsoft-Windows-DotNETRuntime provider is one of the richest sources of information about reflectively loaded assemblies, which is exactly what post-exploitation frameworks use. Setting the COMPlus_ETWEnabled environment variable to zero before launching a process turns it off, with no memory patching at all.HKLM\SYSTEM\CurrentControlSet\Control\WMI\Autologger stops a provider being registered with a given trace session at boot. The change persists and is quiet.Security products advertise detections, not data sources. When the data source disappears, the product does not report that it has gone blind; it simply stops alerting, which is indistinguishable from a quiet host. A security team watching a dashboard sees nothing wrong.
That is the central defensive problem with ETW tampering and the reason it is worth treating as a first-class detection target rather than a footnote under evasion.
COMPlus_ variables set.ntdll.dll within a process are abnormal; EDR products with kernel visibility can see the protection change that precedes them.Restrict local administrator rights, since the persistent registry-based techniques depend on them. Enable tamper protection in your endpoint product so its own configuration and service cannot be changed locally. Forward events off the host promptly, because anything held locally can be dropped. Keep Sysmon and agent configuration under change control and alert when it is modified. Finally, include telemetry integrity in your testing: an adversary emulation exercise that checks whether the SOC noticed the silence is more valuable than one that checks whether an alert fired.
Measuring whether your detections survive a deliberate attempt to blind them is a core part of our SOC maturation services.
It depends on the technique. Patching the ETW write function in the attacker’s own process and setting environment variables to disable the .NET provider need no elevation at all. Removing providers from autologger sessions, stopping trace sessions, or affecting other processes requires administrator rights. The unprivileged variants are common precisely because they are available immediately after initial access.
Parts of it do. Products draw on kernel callbacks, driver-level data, file and registry monitoring, and network telemetry as well as ETW, so detection does not vanish entirely. What is lost tends to be the richest in-memory and runtime visibility, including reflectively loaded .NET assemblies, which is the activity attackers most want hidden.
It is a Microsoft provider that emits security-relevant events about memory allocation, process manipulation, and injection. Consuming it requires the consumer to run as a protected process light, which is restricted to signed security products. Because of that protection and its kernel backing, it is substantially harder for user-mode code to silence than ordinary providers.
Build a rule that compares each host’s current telemetry volume per source against its own recent baseline, and alert when a reachable host drops to zero or near zero. Combine it with agent health checks and heartbeat monitoring. Unexplained silence is one of the highest-value detections available and very few organisations implement it.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.