Home/Refreshers/Windows host triage: refresher
Windows host triage
What to capture first on a suspect Windows machine, where persistence hides, and the events worth knowing by number.
Remember
- Capture memory first, with a tool such as WinPmem. Cache Volatility's symbols if the analysis machine is offline.
- Autoruns lists nearly every persistence place in one pass.
- Prefetch is often off on servers. Amcache and SRUM also record execution.
- A ShimCache entry alone does not prove a program ran on current Windows.
| Event | Log | Means |
|---|---|---|
| 4624 / 4625 | Security | Sign-in and failed sign-in; type 10 is Remote Desktop, type 3 network |
| 4672 | Security | Sign-in with administrator-level privileges |
| 4688 | Security | Process started; command line only if that policy is on |
| 4720 / 4732 | Security | Account created; account added to a group |
| 4698 | Security | Scheduled task created |
| 1102 | Security | Security log cleared |
| 7045 | System | Service installed |
| 4104 | PowerShell Operational | Script block, when that logging is on |
Collect
| Every autostart, hashed and checked | autorunsc -a * -c -h -s |
| Scheduled tasks | schtasks /query /fo LIST /v |
| WMI subscriptions | Get-CimInstance -Namespace root/subscription -ClassName __FilterToConsumerBinding |
| Established connections | Get-NetTCPConnection -State Established |
Watch out
- WMI subscriptions run code on an event and leave nothing in a startup folder.
- The Systems Manager and Azure guest agent logs record commands run through the cloud.
Check it worked
Memory, the autoruns listing, and the event logs are collected, hashed, and off the machine before anything is cleaned.