Open almost any risk register and you will find entries like "Cyber attack", "Data breach" or "Key person dependency". They are not wrong, but nobody can act on them. A good register entry tells the reader what could happen, why, what it would cost, who owns it, and what is being done.

Write the risk as cause, event, consequence

A useful formula:

Because of [cause], there is a risk that [event], which could lead to [consequence].

Compare:

  • Weak: "Ransomware."
  • Strong: "Because several internet-facing servers run unsupported operating systems, there is a risk that attackers exploit a known vulnerability to deploy ransomware, which could stop order processing for up to a week and expose customer data."

The strong version tells you where to act: replace or isolate the old servers. It also tells you why it matters: revenue and privacy impact.

The fields that matter

Field What to write Tip
ID and title Short, unique Titles are for scanning; the statement carries the meaning
Risk statement Cause, event, consequence One risk per entry; split compound risks
Category Cyber, privacy, third party, operational, compliance... Lets you report against the appetite for each category
Owner A named person with authority and budget Not "IT" and not the risk team
Inherent rating Likelihood × impact before controls Shows why the risk matters
Controls Existing controls, linked to your control library Note which have been tested
Residual rating Likelihood × impact with current controls Compare to tolerance
Response Mitigate, transfer, avoid or accept Acceptance needs sign-off at the right level
Action plan Actions, owners, due dates Each action is trackable
Target rating Expected rating after actions Shows the value of the plan
KRIs Indicators with thresholds See key risk indicators
Review date When it will be looked at again High risks at least quarterly

Choosing the owner

The risk owner is the person accountable for managing the risk, usually the business leader whose objectives are affected. They are not necessarily the person doing the work. A ransomware risk to order processing is owned by the head of operations or the COO, while the CISO owns many of the controls. This distinction trips up many registers, and many exam candidates. A RACI matrix makes it explicit.

Scoring without false precision

Five-by-five matrices give an illusion of precision. Keep the scale simple and define each level in business terms:

  • Impact 4 (major): revenue loss over ₹5 crore, or regulatory penalty, or national press coverage, or over 10,000 customer records exposed.
  • Likelihood 4 (likely): expected to happen within the next year, or has happened here or to peers in the past two years.

Defined scales let different people score the same way. Where data exists, quantitative methods such as FAIR give ranges in money terms, which boards often prefer.

Making the register useful

  • Top ten for the board. Nobody reads 200 risks. Report the risks above tolerance, with trends.
  • Link risks to controls and incidents. When an incident happens, ask which risk it was and whether the rating was right.
  • Retire risks. If the cause has gone, close the entry.
  • Review in the business, not just in the risk team. Owners should present their own risks.

Common mistakes

  1. Writing causes or controls as risks ("lack of patching", "no DLP").
  2. Owners that are teams or committees.
  3. Residual equals inherent, which suggests controls have not been assessed.
  4. Actions with no due dates.
  5. Accepting risks above tolerance without escalation.

Learn more

Risk identification, assessment, response and reporting are covered in depth in our free CRISC track. See also risk appetite, tolerance and capacity.

Written and reviewed by the DigiTrust Asia editorial team. How we research, review and correct articles.

General information, not legal advice. Laws and official guidance change; check the current text before acting.

Go deeper on risk

Free CRISC and CISM lessons and practice questions.

Create a free account