Detection rules › Sigma

Important Windows Eventlog Cleared

Severity
high
Author
Florian Roth (Nextron Systems), Tim Shelton, Nasreddine Bencherchali (Nextron Systems)
Source
upstream

Detects the clearing of one of the Windows Core Eventlogs. e.g. caused by "wevtutil cl" command execution

MITRE ATT&CK coverage

TacticTechniques
Defense EvasionT1070.001 Indicator Removal: Clear Windows Event Logs

Event coverage

ProviderEvent IDTitle
Eventlog104The LogFileCleared.Channel log file was cleared.

Stages and Predicates

Stage 1: selection

Channel: ['Microsoft-Windows-PowerShell/Operational', 'Microsoft-Windows-Sysmon/Operational', 'PowerShellCore/Operational', Security, System, 'Windows PowerShell']
Provider_Name: Microsoft-Windows-Eventlog

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
Channeleq
  • Microsoft-Windows-PowerShell/Operational corpus 2 (sigma 2)
  • Microsoft-Windows-Sysmon/Operational corpus 2 (sigma 2)
  • PowerShellCore/Operational corpus 2 (sigma 2)
  • Security corpus 2 (sigma 2)
  • System corpus 2 (sigma 2)
  • Windows PowerShell corpus 2 (sigma 2)
Provider_Nameeq
  • Microsoft-Windows-Eventlog corpus 3 (sigma 3)

Neighbors

Broader alternatives (more inclusive than this rule)

These rules match a superset of what this rule catches. They cover the same events plus more. Use them if you want wider coverage and can absorb more false positives.

  • Eventlog Cleared [sigma] (drops 1 filter this rule applies) (first-stage match only; downstream stages may differ)