Lion Cipher Lab

Active Directory-native deception: a honey user, a decoy SPN, and a SACL tripwire that fires when an attacker looks

Why it matters

Once an intruder gets a single foothold in a Windows shop, the very first thing they do is enumerate Active Directory — every user, every group, every service account — because AD is the map to everything worth stealing. Tools like BloodHound exist to automate exactly that walk. Host-based decoys (bait files, honey local accounts) sit on one machine; the attacker may never touch that machine. AD-native decoys sit in the directory itself, where the attacker is guaranteed to look. That is what makes them so powerful: you plant an account and an SPN that no human and no service ever has a reason…

What you'll learn

Steps in this lab

  1. What AD-native deception is — and why it is the next rung
  2. Get a lab AD if you do not already have one
  3. Rule one and rule two — the judgment that decides if deception helps or hurts
  4. Tripwire #1 — create the honey user (a D3FEND Decoy User Credential)
  5. Tripwire #2 — register a decoy SPN so the honey user is Kerberoastable
  6. Tripwire #3 — a SACL that fires the moment an attacker READS the object
  7. Turn on the recorders BEFORE you attack
  8. Simulate the attacker — trip all three wires yourself (your own lab only)
  9. Confirm the events fired — read them like an analyst
  10. The detection rule shape — and why it is near-zero false positives by design
  11. Where AD decoys beat more logging, the ceiling, and what you learned

Open the full interactive lab →