Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

How do we…

How do we score risks consistently when two people assess them?

6 decision pointsThe pack behind this answer: Information Security Risk Management

Add to board memo

The short answer

Recommendation
Have both assessors score alone against the same written four-level anchors, with one sentence of reason for each rating, and apply the same tie-break rules. Agree a one-level difference that leaves the band and position unchanged. Treat a difference that changes either as an unclear anchor, and fix the wording in the method.
Reasoning
Two assessors differ unless they share the same anchors, the same facts and the same tie-break rules. A scenario fixes what is being scored, so both rate the same story. Impact is the worst credible consequence, never averaged, and likelihood is the chance over the next 12 months. Only controls with evidence that they work lower a score. On a 4 × 4 matrix one level can move a risk into a higher band or outside appetite, which changes who must know and who may accept. Recorded reasons let someone else re-derive the score later.
Considerations
  • The 5 calibration risks, the 5 working days and the quarterly signals are the defaults in the CISO Times risk management pack. Your own method may set different ones.
  • Different facts are a gap in information, not in the anchors. Share the evidence and rescore before arguing about the level.
  • A manager may disagree with a rating and give a reason, but may not choose a band. Disputed ratings go to the Head of Information Security.
  • With no second assessor in a small organisation, calibrate once a year with an outside reviewer.

The decision, step by step

Select any step for the reasoning behind it and where the pack covers it.

  • Start
  • Step
  • Decision
  • Outcome
  • Loop back

Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.

Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one.

Read as text

The same flow written out: each step, its reasoning and where the pack covers it. 18 steps.
  1. Start

    Two people will score the same risks

    Two assessors will differ unless they share the same anchors, the same facts and the same tie-break rules. The aim is a rating two people reach independently, because the band decides who must know and who may accept. The numbers themselves matter less than whether the result can be reproduced.

  2. Decision

    Is each risk written as a scenario with one owner?

    Two people cannot score 'phishing' the same way, because each imagines a different event. A scenario fixes the threat, the weakness, the asset or service, and the consequence, so both assessors are scoring the same story.

    In the pack

  3. Outcome

    Rewrite it as a scenario before anyone scores it

    Scoring a topic produces a number nobody can defend. Write the threat, weakness, asset or service and consequence first, and name the executive who would feel the harm.

    In the pack

  4. Step

    Use one scale with written anchors for every level

    Keep one scale. If the organisation already has an enterprise risk scale, adopt it or map this one to it, keeping four levels of impact and likelihood. Each level needs anchors in plain words and, for money, thresholds that match what finance uses. Otherwise the board sees two meanings of 'Severe'.

  5. Decision

    Have these assessors calibrated together in the last year?

    Calibration is done before the method is first used and every year after. If you do not know when it last happened, treat it as not done.

    In the pack

  6. Step

    Run a calibration exercise on a few sample risks

    Both assessors score the same risks independently, 5 in the pack's default, inherent and residual, with reasons. Compare and discuss. Run the pack's calibration test cases through any spreadsheet or tool that applies the method, including the register: each must give the expected band and position. With no second assessor in a small organisation, calibrate once a year with an outside reviewer.

    In the pack

  7. Step

    Each assessor scores alone, with a reason for every rating

    Impact is the worst credible consequence, rated once on whichever of five areas is worst: money, service, data, legal, reputation. It is never averaged. Likelihood is the chance over the next 12 months: use data where you have it, the anchor description where you do not, and the higher level where they disagree. Rate inherent, list controls, then rate residual. Write one sentence of reason for each rating.

  8. Step

    Apply the same tie-break rules

    Between two levels, take the higher. Missing information raises the rating. A control counts only if it is in place and there is evidence it works; a planned control is a treatment action. A control under a security exception is scored as missing. Where personal data is involved, rate impact on the worse of the harm to the organisation and the harm to the people.

  9. Decision

    Do the two sets of ratings differ?

    Compare each rating, inherent and residual, and the reasons behind them. The reasons usually show where the assessors parted.

    In the pack

  10. Decision

    Did they work from different facts or control evidence?

    Often one assessor saw a restore test or a threat report the other did not. That is a gap in information, and clearer anchors will not close it. Settle the facts before arguing about the level.

  11. Step

    Share the evidence, then both rescore

    Put the evidence in front of both assessors and rescore the affected ratings. A control without evidence still does not count, however confident its owner is.

    In the pack

  12. Decision

    Does the difference change the band or the position?

    Only nine scores are possible on the 4 × 4 matrix, and one level can move a risk from Medium to High, or outside appetite. Read both scores on the matrix and against the category's appetite. If you are not sure, treat it as a change.

  13. Step

    Discuss the one-level difference and agree

    A difference of one level on one rating is normal. Agree the rating and keep the reason that won. Nothing in the method needs to change.

    In the pack

  14. Step

    Have the Head of Information Security settle it

    Disputed ratings go to the Head of Information Security, who also checks every High or Critical rating before it is recorded, within 5 working days in the pack's defaults. Where one person is both assessor and Head of Information Security, a second person, such as an outside adviser, checks those ratings. A manager may disagree with a rating and give a reason, but may not choose a band.

  15. Step

    Fix the anchor in the method, and record the change

    A difference that changes the band or position shows an anchor that needs clearer wording or a better example. Change it in the methodology, not in the assessors' heads, so the next pair of assessors benefits. Record the date, the assessors and the change in the calibration record.

    In the pack

  16. Step

    Record the agreed ratings and reasons in your register

    Keep the impact and likelihood ratings, not only their product, with the reason for each and for every change from inherent to residual. A 2 × 4 and a 4 × 2 both score 8, and the ratings show which kind of risk it is. The reasons are what let someone else re-derive the score later.

    In the pack

  17. Decision

    Does this quarter's check show a sign of drift?

    Each quarter, look for signals. A register entry whose band or position cannot be reproduced from its ratings. In the pack's defaults, more than a quarter of risks High or Critical, or none above Low. The same dispute recurring, or more than 1 in 10 ratings challenged. An incident on a scenario rated Low likelihood, or a consequence larger than its impact rating. Any headline measure off target for two quarters running. Treat each as a prompt to investigate.

    In the pack

  18. Outcome

    Scores two assessors can reproduce, with reasons on record

    This is what an auditor tests: pick risks from the register, read the band from the matrix and the position from the appetite table, and get the same answer. Run the same test yourself each quarter so the first time is not in front of the auditor.

    In the pack

Practical checklist

  1. Check each risk is written as a scenario with one owner before anyone scores it.
  2. Use one scale with written anchors for every level, mapped to any enterprise risk scale.
  3. Calibrate before first use and every year after, on the same sample risks scored independently.
  4. Score inherent, list working controls, then score residual, with a reason for each rating.
  5. Take the higher level between two, and score a control under a security exception as missing.
  6. Compare ratings, settle the facts, and send any band or position change to the Head of Information Security.
  7. Record the impact and likelihood ratings and reasons, and check each quarter for signs of drift.

Evidence to have ready

  • The register entries with impact and likelihood ratings and the reason for each.
  • The calibration record: date, assessors, sample risks and any anchor changed.
  • The results of the calibration test cases on the register or tool.
  • The quarterly check, including a re-derivation test of sampled entries.

Assumptions

  • The risks are already written as scenarios, each with one owner.
  • You use one 4 × 4 impact and likelihood scale for all risks. The timings and sample sizes shown are the defaults in the CISO Times risk management pack; your own method may set different ones.

Not covered here