After a lot of years of reading Windows logs, these are the four I would alert on first. None of them is proof of anything, all of them are worth a human glance:
| Event ID | Meaning | Why it matters |
|---|---|---|
| 4625 | A failed logon | A burst from one source against many accounts is password spraying |
| 4720 | A user account was created | Unexpected new accounts are persistence |
| 4732 | A member was added to a security-enabled local group | Especially the local Administrators group |
| 1102 | The audit log was cleared | Someone wants to hide something. Or a tired admin did |
Two honest caveats:
- Most of these need the right audit policy to be enabled in the first place. If it is not logged, it did not happen.
- A local log can be cleared by whoever controls the machine, so forward events to a collector and alert there.
Tuning is the real work. A rule that fires 400 times a day is a rule nobody reads.