Lion Cipher Lab

Keep a timestamped, hash-sealed investigation log with tmux and script (and see what bash history quietly loses)

Why it matters

In an incident, the first thing anyone asks you afterwards is: what exactly did you run, when, and what did you see? Most people answer from memory or from bash history, and bash history keeps no output, no times by default, and nothing at all if the shell is killed. A responder whose notes write themselves, carry a timestamp on every line, survive a dropped connection and are sealed with a hash can answer that question in court, in a post-incident review or in a job interview. It costs nothing, takes ten minutes to set up, and it is the habit that separates a careful analyst from a lucky one.

What you'll learn

Steps in this lab

  1. Why your own keystrokes are evidence
  2. Get a Linux terminal and install tmux
  3. Build the case folder, a fixture to examine, and the triage list
  4. Before: run the triage with only bash history, then crash the shell
  5. Start a named tmux session and prove it survives a closed window
  6. Turn on pane logging and timestamped prompts
  7. After: run the same triage inside tmux, then crash it the same way
  8. Record a replayable session with script
  9. Seal the originals with a SHA-256 manifest, and keep a copy off the box
  10. Make a readable working copy: strip escape codes, keep the original
  11. Read the scorecard honestly: what this proves and what it does not
  12. Do it better: the way a pro makes this automatic

Open the full interactive lab →