Theory · 9 min · Windows endpoint monitoring
Process trees: parent and child
Spot the parent-child pair that proves something is wrong.
Event 4688 (with command-line auditing enabled) and Sysmon event 1 record each new process with its image path, its command line and its parent. Sysmon also adds hashes and a ProcessGuid that survives PID reuse.
Normal software has habits. Word starts printers and help windows, not shells. w3wp.exe (IIS) serves pages, it does not start cmd.exe. explorer.exe starts what the user double-clicks.
So an unusual parent is often stronger evidence than the child: powershell.exe is everywhere, powershell.exe under WINWORD.EXE is not.
Read the whole command line. Flags like -enc, -w hidden, -nop and download cradles (IEX, DownloadString, Invoke-WebRequest) are the usual noise of malicious PowerShell.
Your turn: select the field that proves it. Select the field that proves this did not come from the user typing in a terminal.
Do the interactive check Free, in the browser.
Sources
- Sysmon (event IDs 1 to 29) Microsoft Learn
- 4688(S): A new process has been created Microsoft Learn
- ATT&CK T1059.001: Command and Scripting Interpreter: PowerShell MITRE ATT&CK v20