Lion Cipher Lab

Read a Procmon capture: the files, registry keys, and processes a sample touched

Why it matters

Process Monitor is the DFIR analyst's microscope on a Windows host: it records every file, registry and process/thread operation in real time. The problem is that 'every operation' means a firehose — well over a million events in a couple of minutes on an idle box — and a sample's malicious behaviour is maybe ten of them. Anyone can click Capture. The skill that actually pays is READING the result: filtering the noise away, isolating the handful of events that matter, and reconstructing from them exactly what the sample did to the machine. This drill hands you a real-shaped capture from an…

What you'll learn

Steps in this lab

  1. The scene: one sample, an isolated sandbox, and a capture full of noise
  2. Read the columns: what each field in a Procmon row means
  3. WHEN this host telemetry is the right lens — and WHEN it drowns you
  4. Meet the firehose: an unfiltered slice
  5. Filter #1 — by process name: keep only the target
  6. Filter #2 — by Operation: keep only the behaviours that matter (and WHY these four)
  7. Filter #3 — by Result: what SUCCESS vs NAME NOT FOUND tells you
  8. Reconstruct the behaviour timeline
  9. Pull the IOCs
  10. How a pro does it better: filter FIRST, snapshot before, correlate with a capture

Open the full interactive lab →