Security log cleared
Detects the Security event log being cleared (1102).
What it detects
Detects the Security event log being cleared (1102). There is almost no legitimate reason to clear the Security log outside documented decommissioning — treat as anti-forensics.
MITRE ATT&CK mapping
- T1070.001Indicator Removal: Clear Windows Event Logs· Defense Evasion
False positives and triage
Rare legitimate cases: decommissioning or documented log-rotation procedures. Anything else warrants immediate investigation of the clearing account.
The rule
Declarative YAML read by the detection engine — data, never executed. Confidence 95%. Source: rules/windows/security_log_cleared.yaml, licensed under the Apache License 2.0.
id: windows.audit.security_log_cleared
version: 1.0.0
status: stable
severity: critical
confidence: 0.95
platforms: [windows]
mitre_techniques: [T1070.001]
description: |
Detects the Security event log being cleared (1102). There is almost no legitimate reason
to clear the Security log outside documented decommissioning — treat as anti-forensics.
match:
event_category: audit
event_action: log_cleared
false_positive_guidance: |
Rare legitimate cases: decommissioning or documented log-rotation procedures. Anything
else warrants immediate investigation of the clearing account.
Related detections
Run this rule on your own logs — offline
KIROSEC runs this rule and the rest of the library over Windows, Linux, macOS and cloud audit logs on the analyst's own machine. Every alert links to the events that raised it, and nothing leaves the device.