iac.htora.dev · security templates

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

  1. Capture memory first, with a tool such as WinPmem. Cache Volatility's symbols if the analysis machine is offline.
  2. Autoruns lists nearly every persistence place in one pass.
  3. Prefetch is often off on servers. Amcache and SRUM also record execution.
  4. A ShimCache entry alone does not prove a program ran on current Windows.
EventLogMeans
4624 / 4625SecuritySign-in and failed sign-in; type 10 is Remote Desktop, type 3 network
4672SecuritySign-in with administrator-level privileges
4688SecurityProcess started; command line only if that policy is on
4720 / 4732SecurityAccount created; account added to a group
4698SecurityScheduled task created
1102SecuritySecurity log cleared
7045SystemService installed
4104PowerShell OperationalScript block, when that logging is on

Collect

Every autostart, hashed and checkedautorunsc -a * -c -h -s
Scheduled tasksschtasks /query /fo LIST /v
WMI subscriptionsGet-CimInstance -Namespace root/subscription -ClassName __FilterToConsumerBinding
Established connectionsGet-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.

Read the full pageDownload PDF

Registry 0.23.0. Built 2026-11-17.

Made by Habibullah Tora. Source on GitHub. Code under the MIT licence, writing under CC BY 4.0.