Menu

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 processes

Look for these lines:

demo-browser:
demo-helper:

Use a name from that list to read one record:

seclab inspect processes demo-helper

You should see:

demo-helper:
  Machine: practice-laptop
  User: maya
  File: demo-helper
  Parent process: demo-browser
  Running: yes
  Command: /opt/lumen/demo-helper

The 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-upload

You should see:

demo-upload:
  Source: practice-laptop
  Destination: parcel-cache
  Port: 443
  Process: demo-helper
  Credential: -
  Group: -
  Ip: -
  Allowed: yes
  Reason: allowed
  Rule: 1

This connection names demo-helper as its process. Record a finding with a question name followed by your answer:

seclab answer process demo-helper

You should see:

Recorded your answer to process.

This saves the finding. It does not stop the program.

challenge icon

Challenge

Easy

Ticket 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

Terminal

All lessons in Investigating a Breach