BASIC LINUX COMMANDS

01 INCIDENT-STYLE LAB BRIEF

Scenario. You have joined a controlled Linux assessment environment where the first objective is to establish a reliable command-line baseline. Before moving into more advanced security testing, the analyst must confirm the active working context and the identity under which commands are executing.

Operational context. The supplied lab workflow uses the TuteDude virtual machine, opened through VMware, with the provided student account. The exercise focuses on two foundational shell observations: the current directory and the logged-in username.

02 LAB ENVIRONMENT & ACCESS

03 PRACTICAL EXECUTION FLOW

01 Prepare the virtual environment Download the supplied TuteDude.ova training image and open it in VMware.

02 Authenticate to the lab Use the credentials supplied with the lab material to enter the student environment.

03 Establish shell context Open the Linux terminal and work from the authenticated student session.

04 Record the working directory Use the standard shell command for printing the present working directory. The supplied evidence shows /home/student.

05 Record execution identity Use the standard command that prints the current username. The supplied evidence shows student.

06 Capture evidence Preserve clear screenshots showing the command and its resulting output. Keep the terminal prompt visible where practical.

04 EVIDENCE PACKAGE

Evidence standard. A professional submission should make the command, execution context, and output readable without requiring the reviewer to infer what happened.

05 ANALYST NOTES

The working directory is a key shell-context indicator. In the supplied lab evidence, it resolves to /home/student.

The username establishes which account is executing the commands. In the supplied evidence, the active account is student.

Command output should be captured immediately after execution to maintain a clean chain of evidence.

Avoid cropping away the terminal prompt when the prompt helps demonstrate the active user or host context.

This baseline verification is useful before file-system enumeration, privilege analysis, process inspection, or other security-testing activities.