Lion Cipher Lab
Run a Change Management Process for a Security Change
- GRC / Compliance
- Intermediate
- ~60 min
- Free · no account required
Why it matters
Ungoverned change — someone pushing a config or a rule with nobody reviewing it, no plan to undo it, and no record it happened — is one of the top causes of BOTH outages and security incidents. That is exactly why every serious framework (NIST, ISO 27001, SOC 2, ITIL) treats change management as a control, not bureaucracy. A GRC or security-leadership role is judged on being able to walk a real change through the process and hand an auditor authorized, tested, documented proof afterward. This lab builds that muscle for real: you take one urgent security change and produce every artifact — the…
What you'll learn
- Writing a complete RFC (Request for Change)
- Classifying changes as standard, normal, or emergency
- Building a rollback/backout plan with a go/no-go decision point
- Running a CAB (Change Advisory Board) decision and the emergency (ECAB) path
- Producing change records that stand up as audit evidence (SOC 2 CC8.1 / ISO 27001 8.32)
Steps in this lab
- What change management is — and why it's a security control, not paperwork
- The scenario, and the three types of change
- Write the RFC — the hands-on core (part 1: the plan)
- Write the RFC (part 2: the rollback plan — the field people skip)
- Run the CAB review — and the emergency (ECAB) path
- Implement, then close the loop: post-implementation review and audit evidence
- The way a pro does it better — right-size the process, and don't rubber-stamp