process tree
The family tree of running processes, where each process was started by a parent.
In more detail
Every process records its parent process ID, so the whole tree can be rebuilt from the running system. Security analysts read it for context: a shell whose parent is a web server, or a core Windows process with an unexpected parent, is a sign that something is wrong.
Example
Windows starts in a fixed pattern: System starts smss.exe, which starts csrss.exe and wininit.exe and exits; wininit.exe starts services.exe and lsass.exe; services.exe starts svchost.exe.Related terms
- Falco field — A named value Falco attaches to each event, such as proc.pname for the parent process name or fd.name for a file or connection.
- command injection — An attack where input meant as data, such as a file name or form field, gets run as commands because a program built code from it.
- parent process — The process that started another process; every process except the first records its parent's PID.
- smss.exe — The Windows Session Manager, the first user-mode process, started by System, which starts csrss.exe and wininit.exe and then exits.
- lsass.exe — The Windows process that checks logons and holds credentials in memory, which makes it a prime target for credential theft.
- svchost.exe — The Windows Service Host process, which runs many built-in services; there are normally dozens of them, all started by services.exe.
Taught in
- Runtime Anomaly Detection with Falco & eBPF — Cloud Security & DevSecOps Engineering
- Forensics Principles, Custody & Imaging — Security Operations & Threat Hunting (SOC)
- Memory Forensics: Process Trees & Injection — Security Operations & Threat Hunting (SOC)
- Malware Triage: Hashes, Strings & Sandboxing — Security Operations & Threat Hunting (SOC)