Security-Visibility - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/security-visibility/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioMon, 12 Oct 2026 14:33:41 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgPowerShell ETW Trace Disabling Techniqueshttps://feed.craftedsignal.io/briefs/2026-10-etw-evasion-powershell/Mon, 12 Oct 2026 14:33:41 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-etw-evasion-powershell/Adversaries utilize PowerShell cmdlets to disable or modify Event Tracing for Windows (ETW) providers to impair security visibility and evade detection.Adversaries frequently target Windows Event Tracing (ETW) to blind security monitoring solutions. By leveraging PowerShell cmdlets such as Remove-EtwTraceProvider or Set-EtwTraceProvider, attackers can programmatically disable or modify the configuration of tracing providers. Disabling these providers prevents the logging of sensitive activities, including process creation, network connections, and script execution, which are critical for detecting malicious post-exploitation activity. This technique is typically employed during the late stages of an attack chain to facilitate persistence or long-term data exfiltration without triggering security alerts.

Impact

Successful suppression of ETW providers results in significant gaps in security telemetry. Defenders lose visibility into script execution and process-related events on compromised hosts. This degradation of observability allows attackers to operate with a reduced risk of detection, effectively neutralizing host-based detection capabilities that rely on ETW-derived event logs.

Recommendation

  1. Deploy the provided Sigma rule to detect attempts to manipulate ETW providers via PowerShell script blocks.
  2. Ensure PowerShell Script Block Logging (Event ID 4104) is enabled across the environment to capture the command line content.
  3. Review logs for the identified cmdlets and investigate associated processes for unauthorized administrative activity.
]]>highadvisoryevasiondefense-impairmentpowershellwindowssecurity-visibility