Set 8

Ubuntu L2-Corporal Industry Assignments

(Set 8 | Index 71–80) Root Working Directory: ~/kactii27


71. Process Command-Line Argument Inspection

Scenario: Ops needs to verify how a service was started.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named process_args

  • Start a test process with arguments

  • Inspect full command-line invocation

  • Capture output to process_args.txt

Commands Expected: ps -ef, ps -o pid,cmd, /proc/<pid>/cmdline, redirection


72. File System Type Behavior Comparison

Scenario: Different file systems behave differently under load.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named fs_behavior

  • Identify filesystem type of the working directory

  • Compare behavior notes with another mounted FS (read-only)

  • Save findings to fs_behavior.txt

Commands Expected: df -T, mount, lsblk -f, redirection


73. Process Environment Variable Inspection

Scenario: Environment variables differ between services.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named process_env

  • Start a process with custom environment variables

  • Inspect environment variables of the running process

  • Save output to process_env.txt

Commands Expected: export, /proc/<pid>/environ, tr, redirection


74. Disk Write Pattern Observation

Scenario: Write-heavy workloads may degrade performance.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named write_patterns

  • Perform controlled write operations

  • Observe disk usage changes

  • Capture observations in write_patterns.txt

Commands Expected: dd, df -h, du -sh, redirection


75. Signal Delivery Order & Effects

Scenario: Different signals affect processes differently.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named signal_effects

  • Start a long-running process

  • Send different signals sequentially

  • Observe and document effects

  • Save results to signal_effects.txt

Commands Expected: kill, kill -l, ps, redirection


76. File Timestamp Integrity Check

Scenario: Audit requires verifying timestamp consistency.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named timestamp_integrity

  • Create and modify files

  • Inspect access, modify, and change times

  • Save output to timestamps.txt

Commands Expected: stat, ls -l --time=atime, redirection


77. System Binary Dependency Inspection

Scenario: A binary fails due to missing dependencies.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named binary_deps

  • Inspect shared library dependencies of a binary

  • Identify missing or resolved libraries

  • Save output to deps.txt

Commands Expected: ldd, which, redirection


78. Temporary Directory Safety Review

Scenario: Improper temp usage causes data leaks.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named tmp_safety

  • Inspect system temp directories

  • Review permissions and sticky bit

  • Document findings in tmp_safety.txt

Commands Expected: ls -ld /tmp, stat, redirection


79. User Session Enumeration & Validation

Scenario: Security needs visibility into active user sessions.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named user_sessions

  • List active user sessions

  • Capture login source information

  • Save output to sessions.txt

Commands Expected: who, w, last, redirection


80. Safe Privileged Command Dry-Run Analysis

Scenario: Before production changes, commands must be reviewed safely.

Instructions:

  • Navigate to ~/kactii27

  • Create a folder named privileged_dryrun

  • Identify commands that would require sudo

  • Attempt dry-run or read-only inspection

  • Capture errors and notes in dryrun.txt

Commands Expected: mount, chown, permission error observation, redirection


Last updated