firefly gemini flash corporate boardroom dark navy, financial charts on screen, no people, no text 642851

Why Your Board Needs a Cyber Risk Number, Not a Colour

Every board in the world governs financial risk with numbers. Almost none govern cyber risk the same way. This is the problem.

Imagine a CFO who, when asked about the company’s currency exposure, responds with a colour. “Our FX risk is amber,” they say. “We are moderately exposed.” The board nods and moves on.

This would never happen. No serious board would accept a colour as an answer to a financial risk question. They would demand a number — the size of the exposure, the probability of adverse movement, the cost of hedging, the net position. They would want to understand the drivers, the scenarios, and the options. And they would hold the CFO accountable for providing that information.

Now consider what happens in most boardrooms when cyber risk is on the agenda. The CISO presents a heat map. Red squares. Amber squares. Green squares. “Our ransomware risk is high. Our phishing risk is medium. Our supply chain risk is high.” The board asks a few questions, approves the cyber security budget, and moves on.

The problem is not that boards are incurious about cyber risk. The problem is that they have been given the wrong tool. A colour is not information. It is the absence of information dressed up as a report.

This article makes the case for why boards need a number — and what changes when they get one.—

What a Colour Cannot Tell You

The heat map has been the dominant tool for communicating cyber risk to boards for more than two decades. It is intuitive, visual, and easy to produce. It is also fundamentally inadequate as a governance tool — for five specific reasons.

1. A Colour Cannot Be Compared to Anything

When a CISO tells the board that ransomware risk is “High,” what does that mean in the context of the company’s overall risk profile? Is it more or less material than the operational risk from a key supplier failure? More or less significant than the financial risk from a currency movement? More or less important than the reputational risk from a product recall?

The answer is: impossible to know. A colour on a cyber risk heat map exists in isolation — it cannot be compared to any other risk the organisation faces because it is expressed in a different unit of measurement. Every other significant business risk is quantified. Cyber risk is coloured. This makes it impossible to integrate cyber risk into the organisation’s overall risk governance framework in any meaningful way.

2. A Colour Cannot Be Budgeted Against

When the board approves a cyber security budget, they are making a financial decision. They are allocating scarce capital to reduce a risk. To make that decision well, they need to know what they are buying — specifically, how much risk the proposed investment will reduce, and whether that reduction justifies the cost.

A heat map cannot answer this question. “Moving our ransomware risk from Red to Amber” is not a return on investment calculation. It is a subjective assertion that the proposed spend will improve a subjective score. The board has no basis for evaluating whether the proposed investment is the best use of the available capital — or whether a different allocation would produce better risk reduction per euro spent.

3. A Colour Cannot Support Accountability

Under NIS2 — and under the general principles of good governance — boards are accountable for cyber risk management. But accountability requires measurement. If the board approved a “High” ransomware risk rating twelve months ago, and the CISO presents the same “High” rating today, has the situation improved, deteriorated, or remained stable? Without a quantitative baseline, there is no way to know.

A number, by contrast, creates accountability. If the board approved a cyber security investment on the basis that it would reduce annual loss exposure from €500,000 to €200,000, and twelve months later the actual exposure is €450,000, the board has a basis for asking substantive questions. What went wrong? What changed? What needs to happen next?

4. A Colour Hides Disagreement

Risk ratings are not objective. When a CISO assigns a “High” rating to ransomware risk, that rating reflects a set of judgements about threat likelihood, control effectiveness, and impact magnitude. Different practitioners might make different judgements — and produce different ratings — from the same underlying data.

A quantitative model makes these judgements explicit. The assumptions are documented, the inputs are visible, and the outputs are traceable. Disagreements can be identified and resolved. A colour, by contrast, hides the judgements inside a subjective assessment — and makes it impossible to challenge them constructively.

5. A Colour Cannot Travel

Cyber risk does not exist in isolation from the rest of the business. Investment decisions, M&A transactions, insurance renewals, regulatory submissions, and investor communications all require an understanding of the organisation’s cyber risk exposure. A colour cannot be used in any of these contexts. A number can.

When a private equity firm is evaluating an acquisition, they want to know the target’s cyber risk exposure in financial terms — not its heat map rating. When a cyber insurer is underwriting a policy, they want to understand the probable maximum loss — not whether the risk is amber. When a board is deciding how much to invest in a new digital initiative, they need to weigh the cyber risk of the new system against its projected financial return — and they cannot do that with a colour.—

What a Number Changes

The shift from colour to number is not merely a technical improvement in risk reporting. It is a fundamental change in how cyber risk is governed — and it affects every dimension of the board’s relationship with cyber security.

Budget Decisions Become Rational

When cyber risk is quantified, budget decisions become rational. The board can evaluate proposed investments against a clear standard: does this investment reduce our financial exposure by more than it costs? A €50,000 security investment that reduces annual loss exposure by €120,000 is straightforwardly worth making. A €200,000 investment that reduces annual loss exposure by €30,000 requires much stronger justification.

This is how every other capital allocation decision in the organisation is made. Cyber security is no different — except that, without quantification, the comparison is impossible.

Risk Appetite Can Be Defined

Most organisations have a stated risk appetite — a level of risk they are willing to accept in pursuit of their strategic objectives. For financial risks, market risks, and operational risks, this appetite is typically expressed in financial terms. For cyber risk, it is typically expressed in colours — which means it is not really expressed at all.

With a quantified cyber risk assessment, the board can define a genuine cyber risk appetite. “We are willing to accept an annual loss exposure of up to €500,000 from cyber incidents. Any exposure above that threshold requires board-level approval of the mitigation plan.” This is a governance statement that can be monitored, measured, and enforced. A colour-based risk appetite is not.

Accountability Becomes Real

Under NIS2, board members of covered entities can be held personally liable for cyber security failures. This is a significant development — and it changes the stakes of board governance of cyber risk fundamentally.

Personal liability requires the ability to demonstrate that you understood the risk you were governing and took proportionate action to manage it. A heat map does not support that demonstration. A quantified risk assessment — showing that the board understood the financial exposure, approved proportionate mitigation measures, and monitored the outcome — does.

The board members who will be best protected in the event of a significant cyber incident are not those who approved the largest cyber security budgets. They are those who can demonstrate that their decisions were based on rigorous analysis of the actual risk — and that they exercised genuine oversight rather than delegating everything to the IT department.

Cyber Risk Joins the Enterprise Risk Framework

The most significant long-term benefit of cyber risk quantification is the integration of cyber risk into the organisation’s enterprise risk management framework. When cyber risk is expressed in the same units as every other risk the organisation faces — euros, probability, expected loss — it can be compared, ranked, and managed alongside those other risks.

This is the goal that governance frameworks like NIS2 and DORA are pushing organisations toward. It is the standard that sophisticated institutional investors increasingly expect. And it is the foundation of genuinely mature cyber risk governance — as opposed to compliance-driven checkbox exercises.—

The Objections — and Why They Do Not Hold

The most common objections to quantitative cyber risk assessment are worth addressing directly, because they are frequently raised by CISOs and consultants who are comfortable with the heat map model and resistant to change.

“We cannot know enough to produce reliable numbers.” This objection confuses precision with calibration. Quantitative risk assessment does not require exact inputs — it requires calibrated estimates expressed as ranges. A well-calibrated estimate of “€200,000 to €600,000, median €380,000” is more useful and more honest than a subjective “High” rating, even though it acknowledges uncertainty.

“The data required is too difficult to obtain.” The data required for a FAIR™ analysis — threat intelligence, loss data, control assessments — is available to any organisation willing to invest in gathering it. The difficulty is not the absence of data but the absence of a methodology for using it. FAIR™ provides that methodology.

“Our board will not understand quantitative analysis.” This objection underestimates boards and overestimates the complexity of communicating quantitative results. A board that can read an annual report can understand “our most likely loss from a ransomware attack is €380,000, with a 24% probability of occurring in the next twelve months.” The challenge is not board comprehension — it is the willingness of the cyber security function to be held accountable to measurable outcomes.—

Where to Start

For boards that recognise the inadequacy of the heat map model and want to move toward quantification, the starting point is simpler than it might appear.

Begin with your two or three most material cyber risk scenarios — the events that, if they occurred, would cause the most significant financial damage to your organisation. For most organisations, these will include a ransomware attack disrupting operations, a data breach triggering regulatory penalties and reputational damage, and a business email compromise targeting a high-value transaction.

For each of those scenarios, ask three questions: How likely is this to happen in the next twelve months? What would it cost if it did? And what could we do to reduce either the likelihood or the cost — and at what price?

With answers to those questions — even rough, initial answers — you have the foundation of a quantified cyber risk assessment. The FAIR™ methodology provides the structure for turning those initial estimates into a probability distribution of outcomes that your board can act on.

The goal is not perfection. The goal is to replace a colour with a number — and to start governing cyber risk the way you govern every other risk that matters to your organisation.—

The Conversation Your Board Should Be Having

The next time cyber risk is on your board agenda, consider asking these questions instead of accepting the heat map:

  • What is our most likely financial loss from our highest-priority cyber risk scenario?
  • What is the probability of a significant cyber incident in the next twelve months?
  • What does the proposed cyber security budget actually buy us — in terms of risk reduced per euro spent?
  • How does our cyber risk exposure compare to our stated risk appetite?
  • If we experienced a significant cyber incident tomorrow, could we demonstrate to regulators that we exercised genuine governance oversight of cyber risk?

If your current cyber risk reporting cannot answer these questions, you are not governing cyber risk — you are acknowledging it. There is a significant difference.—

How Arctos Intelligence Can Help

Arctos Intelligence works with CEOs, CFOs, and boards across Greece, UAE, and the Balkans to replace colour-coded cyber risk reporting with quantified financial analysis. Our board-level engagements produce the number your governance framework requires — the most likely loss, the worst-case scenario, the annual loss exposure, and the specific investments that reduce it most efficiently.

We present to boards. We work with CFOs on cyber risk budgeting. We help organisations build the governance infrastructure that satisfies NIS2’s accountability requirements — and that protects the individuals responsible for leading the organisation in the event of an incident.

If your board is ready for a number, we are ready to find it.—

Arctos Intelligence provides cyber risk quantification and advisory services to CEOs, CFOs, and boards across Greece, UAE, and the Balkans. All engagements are strictly confidential.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top