Security event 1102
The audit log was cleared
Channel: Security. Category: Other Events.
What it records
Generated by the Windows Eventlog service itself (Provider Microsoft-Windows-Eventlog, not the Security-Auditing provider) every time the Security event log is cleared. The event's LogFileCleared payload records the SID, account name, domain, and logon ID of whoever performed the clear.
Why it matters
Because it's written by the Eventlog service as part of the clear operation, 1102 is the canonical 'someone cleared the Security log' tripwire and normally shouldn't occur at all in routine operation. Microsoft's own guidance is to monitor and investigate every occurrence. Forwarding it off-host / alerting on it in real time matters because it can otherwise be lost along with the rest of the log it documents.
What triggers it
Legitimately: an administrator manually clearing the log via Event Viewer or `wevtutil cl Security` for space/retention housekeeping. Maliciously: an intruder clearing the log via `wevtutil cl Security`, PowerShell's `Clear-EventLog`, or Event Viewer's 'Clear Log' action after finishing their objectives, to erase evidence of prior activity. Note it's the clearing action itself that's captured, not the contents that were cleared.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Account Name (Subject) | Who cleared the log: the single most important fact to capture immediately, since the event log itself is the resource that was just wiped. |
| Account Domain | Domain/computer context for the clearing account, which confirms whether it was a local or domain identity that performed the clear. |
| Logon ID | Correlates the clearing action back to the specific logon session (via the matching 4624) that performed it, tying the act to a broader session timeline. |
In practice
Logged when a user clears the Security event log, e.g. via 'wevtutil cl Security' or Event Viewer's 'Clear Log' action; the event records the Subject who did it (Account Name such as CORP\jsmith, Logon ID) as the first entry in the now-empty log. Because it survives the very clear it describes, an analyst finding 1102 from an account with no legitimate log-management role treats it as a strong anti-forensic indicator.
Sample record
The audit log was cleared. Subject: Security ID: S-1-5-21-3623811015-3361044348-30300820-500 Account Name: administrator Domain Name: CORP Logon ID: 0x3E7F2A1
ATT&CK techniques
- T1070.001: T1070.001
Sources
Paste a record into Event XML or open a log in EVTX Reader.