Elastic Security Detection Rules

Windows Event Logs Cleared

Last updated 10 days ago on 2025-02-21
Created 4 years ago on 2020-11-12

About

Identifies attempts to clear Windows event log stores. This is often done by attackers in an attempt to evade detection or destroy forensic evidence on a system.
Tags
Domain: EndpointOS: WindowsUse Case: Threat DetectionTactic: Defense EvasionData Source: Windows Security Event LogsData Source: Windows System Event LogsLanguage: kuery
Severity
low
Risk Score
21
MITRE ATT&CK™

Defense Evasion (TA0005)(opens in a new tab or window)

↳ Indicator Removal (T1070)(opens in a new tab or window)

License
Elastic License v2(opens in a new tab or window)

Definition

Rule Type
Query (Kibana Query Language)
Integration Pack
Prebuilt Security Detection Rules
Index Patterns
winlogbeat-*logs-system.security*logs-system.system*logs-windows.forwarded*
Related Integrations

system(opens in a new tab or window)

windows(opens in a new tab or window)

Query
event.action:("audit-log-cleared" or "Log clear") and winlog.api:"wineventlog" and
  not winlog.provider_name:"AD FS Auditing"

Install detection rules in Elastic Security

Detect Windows Event Logs Cleared in the Elastic Security detection engine by installing this rule into your Elastic Stack.

To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(opens in a new tab or window).