CyberKit

Drill Terminal

Terminal

Type real investigative commands into a simulated host in bash, cmd or PowerShell, and read the output.

The setup

You are on a box with a shell and a hunch. The jobs are the first ones of any triage: who you are, where you are, what is running, what is listening, and what the logs say.

Pick bash, cmd or PowerShell with the tabs. Each task asks for one command line, and Run checks it.

Foundational ยท about 30 minutes

What you will be able to do

  • Move around a filesystem and inspect files from a shell you have never used before
  • List processes and network listeners, and pick the suspicious one out of ordinary output
  • Use each shell's own help system to find a command instead of recalling it
  • Translate the same investigative question between bash, cmd.exe and PowerShell
Notes for teaching it
  • Three separate tracks over one identical fake host, which is what makes it work as a comparison lesson: run the same investigation in all three shells and diff the experience.
  • There is no scoring pressure and nothing to break, so it suits open lab time better than a timed assessment.
  • PowerShell's object pipeline is the conceptual jump most learners need help with; the Where-Object challenges are where to spend the class discussion.

Terms behind it

  • Live Response: Collecting volatile evidence from a running system before it's shut down or imaged.
  • Process Discovery: Listing running processes to spot security tools and pick injection targets.
  • Network Connection Artifacts: Active and recent network endpoints recovered from kernel memory.
  • Shell History Files: Per-user logs of typed shell commands; a key record of operator activity on Unix.

Next: Rule Range. All drills