Control Maturity and Status Reporting
Red, amber and green don't tell a board anything. Define control maturity and report status in a way that shows real movement.
What you'll be able to do
- Build a maturity model your organization can defend
- Define control status so two people rate the same control the same way
- Report quarterly movement instead of static colors
- Link status changes to the evidence behind them
A control maturity model and quarterly report
What's in it. A maturity model your organization can defend, control-level status definitions, and the quarterly report that shows movement rather than colour.
You build it lesson by lesson, using your own organization, and submit it for your certificate. It's yours to keep and adapt.
Who it's for
GRC managers, CISOs and anyone who reports control status to leadership.
What's inside
- Part 1Where the requirement comes from 16 min
- Part 2How small teams and enterprises meet it 14 min
- Part 3The method, step by step 20 min
- Part 4Hands-on lab: small team choose one 90 min
- Part 5Hands-on lab: enterprise choose one 120 min
- Part 6Finish and submit your deliverable 20 min
Built for your size
The requirement is the same everywhere. How you meet it depends on who you have. You pick the lab that matches your organization.
How you earn the certificate
Submit your finished deliverable, which is scored against a published rubric, and pass a short scenario quiz. Your certificate goes to your wallet and can be checked by anyone on the public register.