Parent Processes
Part of the Investigating a Breach section of Coddy's Cybersecurity journey. Lesson 2 of 20.
Finding an unwanted program is only the beginning. You also want to know how it started. A parent process is the program that launched another program.
Look at the parent in this practice record:
seclab inspect processes demo-helperLook for these lines:
demo-helper:
Parent process: demo-browserHere, demo-browser started demo-helper. Read the browser record before drawing a conclusion:
seclab inspect processes demo-browserYou should see:
demo-browser:
Machine: practice-laptop
User: maya
File: demo-browser
Parent process: -
Running: yes
Command: /opt/lumen/demo-browserAn approved browser can launch an unsafe download. That does not mean the browser itself needs to be removed. The link gives you a place to investigate next: what the person opened or downloaded.
Use the parent’s process name when you record your finding:
seclab answer parent demo-browserYou should see:
Recorded your answer to parent.Challenge
EasyTicket from Sam, IT lead
Continue the design-laptop investigation. Identify the program that launched the helper contacting parcel-cache and record its name as parent. Keep both programs running for now so the evidence still shows their relationship, and keep the approved backup working.
Try it yourself
All lessons in Investigating a Breach
1Follow the Evidence
Running ProgramsParent ProcessesFile FingerprintsSave the EvidenceAnother Report2Make the Cleanup Last
Stop the ProgramQuarantine the FileStartup EntriesTest the RestartThe Returning Program