Lion Cipher Lab

Detect credential dumping: LSASS access, the API calls, and the memory artifacts

Why it matters

Once an attacker has a foothold on one Windows box, the very next move that turns a single compromised machine into a compromised network is credential theft: reach into the part of Windows that holds passwords, hashes and Kerberos tickets, and steal the keys to every other system. The richest target is LSASS — the Local Security Authority Subsystem Service, the process that validates logons and caches secrets in its memory — and the second is the SAM, the registry database of local account password hashes. A defender who can read the handful of artifacts these thefts leave behind can catch…

What you'll learn

Steps in this lab

  1. The behaviour we're detecting, in plain English
  2. The one Sysmon event that catches an LSASS read: Event ID 10
  3. The scenario: an LSASS-access alert lands on your queue
  4. Read the ProcessAccess record: target, mask, and the read bit
  5. The memory artifact on disk: the lsass.dmp FileCreate
  6. The second theft: SAM/SECURITY/SYSTEM hive extraction
  7. Concept map: LSASS dumping vs SAM extraction vs DCSync — and the MITRE tree
  8. The pro's judgment: tune out the legit accessors, know when you need memory forensics, and respond

Open the full interactive lab →