Log Clearing
Also called Event Log Wiping.
Erasing or truncating logs to destroy the record of activity.
What it is
Deleting, truncating, or selectively editing event and audit logs to remove the record of attacker actions. This ranges from wiping entire Windows event logs to surgically removing individual entries.
Why it matters
Logs are a primary evidence source, so their destruction is a high-impact anti-forensic move that also signals intent and capability. A cleared log, or the specific event that records the clearing, is itself a strong indicator of compromise.
In practice
Security event logs show a single 'log cleared' record and nothing before it, marking the point an attacker tried to cover their tracks.
What to look for
- Security log event 1102 or System log event 104.
- A sudden drop to zero events from a host that normally sends many.
- Truncated or emptied files under /var/log, or a shortened shell history.
Common mistake
Relying on the host's own logs. Forward logs off the box so a clear on the endpoint cannot erase the copy.
Use it in CyberKit
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Splunk Enterprise Security Commercial
A SIEM where these logs are searched with SPL and turned into correlation searches.
-
Microsoft Sentinel Commercial
Microsoft's cloud SIEM, queried with KQL and fed by connectors for these log sources.
-
Elastic Security Commercial
A SIEM built on Elasticsearch, with a detection rules library and timeline investigations.
-
Wazuh Open source
An open source platform that collects, decodes and alerts on host and log data.
Read next
- Indicator Removal: Deleting the traces an intrusion leaves behind to evade detection.
- Anti-Forensics: Techniques meant to defeat or mislead forensic analysis.
- Disabling Security Tools: Turning off or blinding antivirus, EDR, and logging.