<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Event-Log-Forensics on it-learn.io | IT, Networking &amp; Cybersecurity Blog</title><link>https://blog.it-learn.io/tags/event-log-forensics/</link><description>Recent content in Event-Log-Forensics on it-learn.io | IT, Networking &amp; Cybersecurity Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.it-learn.io/tags/event-log-forensics/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows Event Log Forensics: What Each Event ID Actually Means</title><link>https://blog.it-learn.io/posts/2026-06-01-windows-event-log-forensics-event-ids/</link><pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.it-learn.io/posts/2026-06-01-windows-event-log-forensics-event-ids/</guid><description>&lt;p&gt;If you can read Windows event logs, you can reconstruct what happened on a Windows host. If you cannot, you are guessing.&lt;/p&gt;
&lt;p&gt;This post is the field guide. We cover the event IDs that actually show up in investigations, what each one means in context, how to correlate them across logs, the gotchas that fool beginners, and the queries that turn raw &lt;code&gt;.evtx&lt;/code&gt; files into a defensible timeline.&lt;/p&gt;
&lt;h2 id="where-event-logs-live-and-how-they-are-structured"&gt;Where event logs live and how they are structured&lt;/h2&gt;
&lt;p&gt;Windows event logs are &lt;code&gt;.evtx&lt;/code&gt; files (XML-based, since Vista) stored under &lt;code&gt;%SystemRoot%\System32\winevt\Logs\&lt;/code&gt;. The three logs that matter most for forensics are:&lt;/p&gt;</description></item></channel></rss>