Lion Cipher Lab

Hunt registry persistence in Sysmon registry events (Event IDs 12-14)

Why it matters

The Windows registry is where most persistence lives. A single value under a Run key starts a program at every logon; a Debugger value under Image File Execution Options swaps a system tool for a backdoor; a per-user COM entry quietly loads an attacker's DLL into Explorer. Sysmon records every one of those writes -- and also every write by every installer, updater and chat app on the fleet, which is thousands of harmless events a week. An analyst who alerts on 'something wrote to a Run key' is paged all day and learns to ignore the pager. This lab teaches the two moves that work in practice:…

What you'll learn

Steps in this lab

  1. What registry persistence is, and why you hunt it in telemetry
  2. The six key families you will watch
  3. How Sysmon records a registry write
  4. Build a week of registry events for 40 hosts
  5. Why 'alert on any write to an autostart key' fails
  6. Score three rules, family by family
  7. Read every false positive and the one miss
  8. Stack the fleet: the row that exists on one machine
  9. Optional: look at your own machine (read-only)
  10. Honest limits, and what sits in front of this
  11. Where this goes next

Open the full interactive lab →