Case FB66D0 · GRC · L1 Foundations
The Risk Register
- 01 What is it?
- 02 How is it abused?
- 03 How do you stop it?
What a strong answer covers
Try it out loud first. Then check yourself:
- Lists each risk with owner, cause, impact, likelihood, inherent and residual rating, treatment and next review date.
- Fails as a compliance artefact: vague risks like "cyber attack", no owner, stale scores, never seen by decision makers.
- Write risks as cause, event, consequence: "unpatched VPN lets ransomware encrypt plant systems, halting production".
- A business owner decides treatment and security advises; accepted risks get an expiry date and a re-review.
- Link risks to controls, incidents and KRIs so a failed control or new incident moves the score before the annual review.
If the interviewer pushes back
- Two business units rate the same risk very differently. How do you make scoring consistent across the company?
- How would you tell a stale register from a living one in your first week at a new employer?