Granite joins WeKomply family of compliance solutions

I’m just a CEO. Don’t talk to me about CVSS scores

Actually, I have two roles: I’m both a CEO and a security professional. 

As a security professional, I want the details. As a CEO, I don’t really care about the details – I just want to know what they mean for the business. 

Here is the kind of language security people like to use when describing a cyber risk:

“An unauthenticated remote attacker can exploit this CVSS 9.1 vulnerability to write arbitrary files and execute arbitrary commands on the device’s operating system with root privileges.”

And here is what I think we should move towards:

“We have a high risk for a dedicated cyber attack that could make our customer-facing service unavailable for several days and impact customer trust for a long period of time.”

Which one do you think is going to resonate more with your executives, your board and your CEO?

We like to talk about CVEs and CVSS scores, critical vulnerabilities, patch levels, multi-factor authentication coverage, compliance findings, security log data and firewall metrics. Executives care about something else. Revenue, that’s the top line. Profitability, that’s the bottom line. Customers: are they happy? Stakeholders: are we providing enough value for them? Operations: are they running smoothly? Reputation: is it good or bad? Growth: are we growing enough? And these are the people who make the investment decisions for security. That is quite a big difference, and it’s up to us to narrow it.

I believe cybersecurity has never been a technology problem, and not even a compliance problem. It’s all about risk. The fact is, we security people would have a much easier time with our executives if we talked about risk instead of technical details.

Risk management works, as long as you keep it simple

Risk is the possibility that uncertainty will affect your business objectives. Basically, you are not going to reach the goals you have for the business: you don’t hit the revenue you wanted, or your profitability is lower than planned. On a smaller scale, the same goes for security goals and business unit goals.

Risk is a natural part of every business. If you run a business, you are taking some risk, and that’s exactly why business people understand it. You can take a risk or you can mitigate it, and both are valid options. Risks can also be positive, but I’ll leave those out here because I’m trying to keep this simple.

To do risk management you need a process, and this one is really simple:

  1. Identify. What could go wrong, and what could prevent us from achieving our objectives?
  2. Assess. How big is the risk: what would the impact be, and how likely is it to occur?
  3. Mitigate. What security controls do we already have in place, and what else do we need?
  4. Monitor. Has the risk changed, and are the controls still working?


The world changes, the business changes and the risks change. Our security controls evolve, some become obsolete and sometimes we need new ones. It’s a changing environment 24×7, so we keep identifying new risks and updating our assessments and mitigation.

Assessment is where you can do the most harm or the most good

Of these four steps, I would focus on assessment, because mitigation and everything else is based on it. If you do it right, the rest of the process is easy.

There are two factors, impact and likelihood, or consequence and probability, whatever terms you want to use. First you assess the impact, and you are not assessing just any impact. You are trying to assess the realistic worst-case scenario.

Once you have done that, you assess the likelihood for that particular level of impact. The question is not whether something will happen, but how likely it is that this worst-case scenario will happen. This is the hard part. The impact assessment is a bit easier.

Now you have a coherent assessment, a pair that describes one scenario. If you use the worst-case scenario for impact and the most likely scenario for likelihood, you have a mismatch.

Why focus on the high-impact scenarios? You could focus on the other end of the spectrum, but high probability typically means lower impact, and those events you can handle more or less as business as usual. The risk management process doesn’t provide the real value there. The real value is in the high-impact scenarios: you identify them, you assess them, and you mitigate them as well as you can with the budget you have, to the level that makes sense for them.

A five-point scale is enough

I use ratings from 1 to 5. You can use whatever scale you like, but this one is pretty typical, and you can use AI to help you with the wording if you want to.

Impact
Likelihood

1. Insignificant: negligible effect on business operations or objectives.

1. Rare: would be surprising if it occurred.

2. Minor: limited impact that can be managed through normal business processes.

2. Unlikely: could occur, but is not expected.

3. Moderate: clear business impact requiring management attention and corrective actions.

3. Possible: a realistic and credible scenario.

4. Major: significant impact on operations, customers, finances or strategic objectives.

4. Likely: expected to occur unless actively managed.

5. Severe: threatens the organisation’s ability to operate, fulfil its core obligations or achieve its strategic objectives.

5. Almost certain: occurrence is highly expected or already underway.

Impact is the easy one, because you can write down the levels based on your own business. If you have a certain level of revenue and profitability, that gives you a monetary value for, say, the moderate level. Then it’s easy to say that if this service goes down, it’s going to have roughly this type of effect.

Likelihood is the hard part, and it includes guesswork. That’s part of the process, so don’t get scared. It’s not 100% science.

The worst thing on a risk report is a flat line

You can complicate this if you like, but my suggestion is not to. Use simple methods and you get simple results.

A typical risk map has impact on one scale and likelihood on the other. The critical risks are the red ones in the top right corner, and it’s really simple to see where to focus.

Then you have the risk trend. It really doesn’t matter what the actual risk level is. The trend is what’s important: are we moving up, moving down, or is it just a flat line where nothing happens? The flat line is the worst. Moving up is better than a flat line, because if it’s flat, no one is doing their actual risk management work and no one is identifying new risks.

On top of that, you want information on the status of your risks and where they are in the process.

Risk is the common language of security and business

The biggest reason for me is that this creates a common language between security and business, because risk is the element that unifies them.

It also helps you identify the crown jewels of the business: what creates the most value, what has to be running 24/7 and what would hurt the company the most. You end up with a prioritised list of your most important assets, your biggest risks and where to invest your money.

Compare that to a tick-in-a-box compliance exercise and you get much better, more prioritised results. And here is what business people like: the same list tells you which risks and assets you should not invest in beyond the bare minimum, so you can save that money for the assets and risks that are actually critical.

“It can’t be this simple”

I know what you are thinking at this point. It can’t be this simple, just a five-by-five and a qualitative assessment, and then I have something to discuss with the board and the CEO or CFO? It has to be quantified. There have to be better, more complex and nicer-looking algorithms. Maybe Monte Carlo simulations, which you can now do easily with AI. Maybe some proof from academic studies. I want my package to be bulletproof.

So let me ask you: which of these impact assessments is the most precise?

  • A) Impact is assessed as moderate (3/5), with a clear business impact requiring management attention, corrective actions and medium-level financial losses (EUR 50k–200k).
  • B) Impact is assessed to be EUR 100k.
  • C) Impact is assessed to be EUR 102,523.12.

 

C is nonsense. B is okay. A is definitely the best. We have so many assumptions in risk assessments that you shouldn’t try to create precise-looking results when they are not precise. A is the best because it shows that this is a qualitative assessment, with a certain type of impact and a certain range.

I’m a CEO, I’m a simple person, and most of my colleagues are too. We want to see solid processes and good data, but please don’t overcomplicate it if a ballpark is good enough. That’s my advice to all security people.

And my advice to everyone else: take the risk and try it.

This text is based on my talk “It’s all about risk” at Cyber Security Nordic 2026.

Teppo Kattilakoski, founder and CEO of Granite
Published 9th of November 2026