Lion Cipher Lab

Run an access recertification campaign over your own directory — and catch the access nobody will vouch for

Why it matters

Every framework that anyone audits you against — access reviews in NIST SP 800-53 (AC-2, AC-6), the least-privilege pillar of a zero-trust program — eventually asks the same question: for every person who can do something sensitive, does someone still say they should? That periodic yes/no is a recertification (or access-review) campaign, and in most organizations it is a spreadsheet emailed to managers who click "approve all". Doing it once, properly, on a directory you own shows you the mechanics the SaaS governance tools hide: how entitlements are really stored, how a reviewer gets…

What you'll learn

Steps in this lab

  1. What a recertification campaign is, and when you actually run one
  2. The thing you'll certify: entitlements, owners, and the three ways it goes wrong
  3. Get the pieces in place: directory up, venv, ldap3, admin password exported
  4. Seed a realistic org into your directory — traps included
  5. Connect from Python and read one entry
  6. Take the campaign snapshot (and hash it)
  7. Build the reviewer worksheets and route the exceptions
  8. What a good review decision actually asks
  9. Record the reviewers' decisions
  10. Enforce the revocations — and meet the last-member rule
  11. Remediate the access nobody would vouch for
  12. The evidence an auditor will actually accept
  13. Close the campaign: re-check and prove the change
  14. Run it on a cadence — and where it sits next to JML and role mining
  15. Where campaigns quietly fail
  16. What you just did — and why it matters

Open the full interactive lab →