Lion Cipher Lab

Detect and prevent tampering with your AWS security logging (CloudTrail, GuardDuty, Config, flow logs)

Why it matters

An intruder who reaches an AWS account with enough permissions often does the same thing first: turn off the cameras. Stop the trail, delete the GuardDuty detector, stop AWS Config, delete the flow logs, or set the log bucket to expire everything after a day. Every investigation after that point is blind. MITRE ATT&CK tracks this as its own technique for exactly that reason. The defender's job is to notice within minutes, and better still, to make the off-switch refuse to work. This lab gives you both halves on your own machine: rules you measure honestly with precision and recall, a silence…

What you'll learn

Steps in this lab

  1. The attack you are defending against: turning off the cameras
  2. The tamper map: which API calls blind which sensor
  3. Set up a folder and check Python
  4. Generate one week of CloudTrail records with planted tampering
  5. Score the naive rule: catch everything, drown the analyst
  6. How the tuned rule thinks: scope, severity, suppression, escalation
  7. The quiet tamper: the trail is still ON
  8. Honest negative: suppression is a gift to whoever holds the suppressed role
  9. Latency: how many minutes the attacker gets
  10. The heartbeat: catch the silence no event rule can see
  11. Prevention: an SCP that makes the off-switch refuse
  12. Replay the SCP against the week: 8 of 9 blocked, and what it breaks
  13. A sink the attacker cannot touch: organization trail, log-archive account, Object Lock
  14. What none of this can see
  15. When to use which control, and how a pro runs it

Open the full interactive lab →