Lion Cipher Lab

Build a C-SCRM plan and tailor controls under NIST SP 800-161r1

Why it matters

Most breaches that make the news do not start with a flaw in code the victim wrote — they arrive through the supply chain: a compromised software update (SolarWinds), a vulnerable open-source library buried three dependencies deep (Log4Shell), a hardware component with untrusted provenance, or a cloud provider outage that takes the whole product down. That is the C-SCRM problem: you are responsible for risk you did not create and often cannot even see, because it lives in the code, hardware, and services you bought or imported rather than built. NIST SP 800-161r1 (Cybersecurity Supply Chain…

What you'll learn

Steps in this lab

  1. The scenario, and the artifact you will produce
  2. Part 1 — The three-tier structure: who decides what, and how it cascades
  3. Part 2 — Criticality analysis: which supplier failure hurts the mission most?
  4. Part 3 — Supplier risk assessment: how likely, how bad, and the foreign-ownership factor
  5. Part 4 — Tailor controls from the 800-161r1 families to the supplier and tier
  6. Part 5 — Assemble the C-SCRM plan document sections
  7. Part 6 — The POA&M residual-risk register
  8. The judgment: C-SCRM vs TPRM, SBOM/EO 14028, and the honest limits

Open the full interactive lab →