Lion Cipher Lab

Assemble an authorization package and make a risk-based ATO decision (the NIST RMF authorize step)

Why it matters

Somewhere behind every system you use, a person decided it was safe enough to switch on. Not a scanner, not a checklist — a person, who put their name on the risk. That decision is the job everyone in GRC is eventually promoted into, and almost nobody practises it before they're handed it. This lab lets you rehearse it on a system small enough to fit in your head. You'll learn to draw a boundary, turn a pile of findings into one honest sentence about risk, choose between the four real decisions available to you, and write the memo. Even if you never work for a US federal agency, the skill…

What you'll learn

Steps in this lab

  1. What 'authorize' means, and who is actually signing
  2. Pick your system and lay out the package folder
  3. Draw the authorization boundary — the most-argued-about page in the package
  4. Assemble the three documents — and know which question each one answers
  5. Turn a list of findings into a statement of residual risk
  6. The four decisions actually available to you
  7. Write the decision memo
  8. Why the AO signs it and not the engineer — and why 'all green' is the wrong bar
  9. After the signature: ongoing authorization, and what this looks like outside government

Open the full interactive lab →