Indicator Removal on Host: Clear Windows Event Logs

Adversaries may clear Windows Event Logs to hide the activity of an intrusion. Windows Event Logs are a record of a computer's alerts and notifications. There are three system-defined sources of events: System, Application, and Security, with five event types: Error, Warning, Information, Success Audit, and Failure Audit.

The event logs can be cleared with the following utility commands:

  • wevtutil cl system
  • wevtutil cl application
  • wevtutil cl security

These logs may also be cleared through other mechanisms, such as the event viewer GUI or PowerShell.

ID: T1070.001
Sub-technique of:  T1070
Tactic: Defense Evasion
Platforms: Windows
System Requirements: Clearing the Windows event logs requires Administrator permissions
Permissions Required: Administrator
Data Sources: API monitoring, File monitoring, Process command-line parameters, Process monitoring
Defense Bypassed: Anti Virus, Host Intrusion Prevention Systems, Log Analysis
Version: 1.0
Created: 28 January 2020
Last Modified: 29 March 2020

Procedure Examples

Name Description

APT28 has cleared event logs, including by using the commands wevtutil cl System and wevtutil cl Security.[13][14]


APT32 has cleared select event log entries.[17]


APT38 clears Window Event logs and Sysmon logs from the system.[20]


APT41 attempted to remove evidence of some of its activity by clearing Windows security and system events.[21]


The BlackEnergy component KillDisk is capable of deleting Windows Event Logs.[4]

Dragonfly 2.0

Dragonfly 2.0 cleared Windows event logs and other logs produced by tools they used, including system, security, terminal services, remote services, and audit logs. The actors also deleted specific Registry keys.[15][16]


FIN5 has cleared event logs from victims.[18]


FIN8 has cleared logs during post compromise cleanup activities.[19]


FinFisher clears the system event logs using OpenEventLog/ClearEventLog APIs .[2][3]

gh0st RAT

gh0st RAT is able to wipe event logs.[5]


Hydraq creates a backdoor through which remote attackers can clear all system event logs.[7][8]


NotPetya uses wevtutil to clear the Windows event logs.[11]

Olympic Destroyer

Olympic Destroyer will attempt to clear the System and Security event logs using wevtutil.[10]


Pupy has a module to clear event logs with PowerShell.[1]


RunningRAT contains code to clear event logs.[9]


SynAck clears event logs.[6]


ZxShell has a command to clear system event logs.[12]


Mitigation Description
Encrypt Sensitive Information

Obfuscate/encrypt event files locally and in transit to avoid giving feedback to an adversary.

Remote Data Storage

Automatically forward events to a log server or data repository to prevent conditions in which the adversary can locate and manipulate data on the local system. When possible, minimize time delay on event reporting to avoid prolonged storage on the local system.

Restrict File and Directory Permissions

Protect generated event files that are stored locally with proper permissions and authentication and limit opportunities for adversaries to increase privileges by preventing Privilege Escalation opportunities.


Deleting Windows event logs (via native binaries [22], API functions [23], or PowerShell [24]) may also generate an alterable event (Event ID 1102: "The audit log was cleared").