Learn the concept.
A risk register helps a team compare concerns and track decisions. Scores are a model for discussion, not precise predictions.
Use a consistent scale
Define what low, medium, and high mean for likelihood and impact in the organization.
Identify the owner
Assign responsibility for the risk and track the chosen treatment, due date, and status.
Revisit after treatment
Record remaining risk after safeguards are applied. Verify treatment rather than reducing the score because a task was assigned.
Field example03 / A
Put it in context
A shared administrator account receives a high impact rating under Harbor Books’ scale. An owner plans named accounts and a review date. The risk remains open until the change is verified.
A treatment plan is not a completed fix
Fictional shared-administrator-account risk.
- OpenAssess using the agreed scale
Record assumptions, impact, and likelihood.
- PlannedAssign named-account rollout
Name the owner and target date.
- ImplementedCollect change evidence
A reported change still needs validation.
- VerifiedUpdate the risk decision
Record remaining risk and the authorized disposition.
Read the visualShould the item be marked resolved when a plan is approved?
No. Track implementation and verification, then record the appropriate risk decision.
Make a decision.
Use what you just learned. A correct answer lets you save this lesson to your progress.
Take this with you.
A risk score needs a rationale, an owner, and a review date.
Next lesson: From requirements to controls