WINDOWS

Windows Event Logs for SOC L1

Source and context beat a memorised number. Security, process, PowerShell — if audit is even on.

Tomek 8 min read BEGINNER

Windows produces a lot of noise. L1 is not reciting Event IDs. It is asking: which channel, which account, what time, what sits next to it.

Start with Security (logon, process, account), then System (services), then PowerShell — if the lab policy actually logs scripts.

The ID cheat sheet is in Resources. Windows docs say which channels exist at all. Analysis pattern:

event → context → correlation → hypothesis → check

A lone 4624 is not proof of an incident. It is proof that someone (or something) logged on with a given logon type.

Want this in a lab or in production?

The article stays free. The form is for scope, not a paywall.

I usually reply within 1 business day. The inquiry is stored on the server; you get a confirmation from hello@tomek.st. Sending does not commit you to a contract.