Tool Files & Artifacts
Event Log Reader
Read a binary .evtx file or pasted event XML, with logon types, NTSTATUS codes and the Keywords mask decoded.
Read Windows event logs two ways: drop a binary .evtx file, or paste the XML of one event. Both decode the fields triage turns on, such as logon types, NTSTATUS codes and the Keywords mask.
This runs in your browser. Nothing you type or open is uploaded.
How to read it
Filter by event ID first. 4624 and 4625 are logons, 4688 is a new process, 7045 is a new service, and 1102 means someone cleared the Security log.
Read the decoded columns, not the raw numbers. A logon type of 10 is Remote Desktop, and a status of 0xC000006A is a bad password on a real account.
The EVTX tab resolves the shared templates inside the file, so every record shows its named fields even when the log came from another machine.
Tab by tab
EVTX file
Read a Windows .evtx file in the browser with the binary XML templates resolved. Grepping an EVTX returns fragments, because each record stores a template reference and its values, not its own XML.
Filter by event ID to cut the list down, then pick a record to read its full XML.
Closed cleanly: no means the log was still open when it was copied. Recent records may sit in a chunk that was never flushed.
1102 is the Security log being cleared. It is the record people skip and often the one that matters most.
Pasted XML
Windows event XML is almost readable, which is the problem. The System block buries the two or three fields you want, and the values that matter most are codes: a logon type of 10, a SubStatus of 0xc000006a, a 64-bit Keywords mask.
Paste one record as XML, from Event Viewer's XML view or wevtutil qe Security /f:xml. Binary .evtx goes in the EVTX Reader instead.
The event data comes first with codes decoded where they sit, then the header. The link at the bottom opens the event in the Event ID reference.
| Type | Meaning |
|---|---|
| 0 | System: used only by the System account at startup. |
| 2 | Interactive: signed in at the console, physically or via a KVM. |
| 3 | Network: reached the machine over the network. SMB share access, and most remote authentication. |
| 4 | Batch: a scheduled task ran under these credentials. |
| 5 | Service: a service started under this account. |
| 7 | Unlock: the workstation was unlocked. |
| 8 | NetworkCleartext: network logon with the password sent in the clear. Usually IIS basic auth. |
| 9 | NewCredentials: RunAs /netonly. The process keeps its own local identity and uses the new credentials for network access only, which is what makes this a common sight in lateral movement. |
| 10 | RemoteInteractive: RDP or Terminal Services. |
| 11 | CachedInteractive: signed in using cached domain credentials, with no domain controller reachable. |
| 12 | CachedRemoteInteractive: the cached equivalent of type 10. |
| 13 | CachedUnlock: unlocked using cached credentials. |
Terms behind it
- Windows Event Log: Windows' record of logons, process starts, and system activity.
- Process Creation Auditing: Logging every new process start, ideally with its full command line.
- Authentication Logs: Records of login attempts, successes, and failures across systems.
- Sysmon: Free Windows driver that logs rich process, network, and file telemetry.
- Log Clearing: Erasing or truncating logs to destroy the record of activity.
- PowerShell Logging: Recording PowerShell commands, scripts, and pipeline activity for audit.
Sources
- MS-EVEN6: EventLog Remoting Protocol. Microsoft's own specification for the Binary XML this tool renders, including the token types, value types and the template/substitution model.
- Windows Event Schema (Microsoft Learn). The normative schema for the System and EventData blocks this page splits apart: the definition of every element it reads.
- 4624: An account was successfully logged on. Microsoft's own field-by-field documentation for the event this tool is most often pointed at, including the full logon-type table.
Worth using too
- python-evtx. A complete, well-documented EVTX parser and the clearest description of the format's structures anywhere. The right tool once a log is larger than a browser tab should handle.
- EvtxECmd (Eric Zimmerman). Parses EVTX to CSV or JSON with community-maintained maps that name the fields per event ID: the standard step between a raw log and a timeline.
- libyal libevtx. The half a browser cannot do: a well-documented BinXML implementation that reads binary .evtx directly. Use it to export records, then bring the XML here.