Running Programs
Part of the Investigating a Breach section of Coddy's Cybersecurity journey. Lesson 1 of 20.
An account can be secure while an unwanted program is still running on its computer. In this section, you will investigate the programs themselves. Lumen has added new computers and a checkout service; the account protections you set earlier are still in place.
A running program is called a process. Start by listing the processes. Here is a separate practice computer:
seclab inspect processesLook for these lines:
demo-browser:
demo-helper:Use a name from that list to read one record:
seclab inspect processes demo-helperYou should see:
demo-helper:
Machine: practice-laptop
User: maya
File: demo-helper
Parent process: demo-browser
Running: yes
Command: /opt/lumen/demo-helperThe record tells you where the program runs and which file it uses. A name alone does not tell you whether it is safe. Compare it with the connection records:
seclab inspect connections demo-uploadYou should see:
demo-upload:
Source: practice-laptop
Destination: parcel-cache
Port: 443
Process: demo-helper
Credential: -
Group: -
Ip: -
Allowed: yes
Reason: allowed
Rule: 1This connection names demo-helper as its process. Record a finding with a question name followed by your answer:
seclab answer process demo-helperYou should see:
Recorded your answer to process.This saves the finding. It does not stop the program.
Challenge
EasyTicket from Sam, IT lead
Sam has flagged a connection from design-laptop to parcel-cache. Find which program opened it and record its name as process. Leave the programs running while we collect evidence. The approved backup must keep 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