Chapters0/54 ▾
- 1.Architecture & Log Sources0/5
- 2.Indicators of Malicious Activity0/5
- 3.Investigation Tools & Threat Hunting0/5
- 4.Process Improvement, Automation & AI0/5
- 5.Vulnerability Scanning Methods0/5
- 6.Analyzing Scan Output0/5
- 7.Prioritization, Mitigation & Controls0/5
- 8.Attack Frameworks & the Response Process0/5
- 9.Incident Response Techniques0/5
- 10.Vulnerability Reporting & Communication0/5
- 11.Incident Reporting & Metrics0/4
Chapter 2 · Lesson 2 of 5
Host indicators: process lineage, masquerading and built-in tools
1 min read
On an endpoint, the strongest clue is usually who started a process and with what arguments. A mail client or office application has no legitimate reason to launch a command shell.
When the chain continues into PowerShell with switches such as -w hidden (no window), -nop (skip the profile) and -enc (a base64-encoded command), the arguments exist to hide what is running. Legitimate maintenance and logon scripts descend from service or session hosts, not from the program that just opened an attachment.
- Masquerading: the genuine svchost.exe runs from the System32 folder with services.exe as its parent. A copy in a user's temp folder started by explorer.exe is an imposter, whatever its name.
- Living off the land: certutil used with -urlcache to download a file and then -decode to turn it into an executable is abuse of a signed Microsoft tool, so alert on the argument pattern, not the image name.
- In-memory execution: IEX combined with DownloadString runs a script without writing a file, and a wmiprvse.exe parent means it was launched through WMI, in this pattern usually by a remote call from another machine. Disk scanning finds nothing; script block logging and lineage do.
Example: a spreadsheet program starts cmd.exe, which starts PowerShell with -enc and a long base64 string. Even before decoding it, the parent, the hidden window and the encoding together make this a finding, not routine maintenance.
Check yourself
1. A host inventory lists two running processes named svchost.exe: one with image path C:\Windows\System32\svchost.exe whose parent is services.exe, and one with image path C:\Users\jrivera\AppData\Local\Temp\svchost.exe whose parent is explorer.exe and which holds an open connection to an external address. Which conclusion fits?
2. Process creation events on a user workstation show outlook.exe as the parent of cmd.exe, which in turn started powershell.exe with the arguments -nop -w hidden -enc SQBFAFgAIAAoAE4A. The events are stamped 10:42 on a Tuesday. What does this chain indicate?
Facts checked 2026-11-15 · Sources: CompTIA CySA+ (CS0-004) certification page and exam objectives, AWS CloudTrail User Guide: Logging data events
CompTIA CySA+ cheat sheet: every key fact on one page →