- Market
- Saudi Arabia
- Written for
- CISO, COO
- Decision
- Rank cyber risks by business consequence to direct budget and treatment
- Languages
- EN · AR
Cybersecurity credentials
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
The method
From asset list to a ranked register a board can act on
Each step narrows the field: from everything that exists, to what could plausibly happen, to what would actually hurt, to what should be done about it.
Scope by business value
The processes and assets whose loss the business would feel — revenue lines, operational systems, data with regulatory weight — named with the owners who would feel it. A scope the leadership recognises as the business, not an IT inventory.
Build the threat scenarios
For each asset, the plausible ways it gets hurt — written as concrete scenarios with the people who run the process, because they know the dependencies a template misses. Scenarios specific enough to argue about, which is the point.
Judge likelihood and consequence
Likelihood from the state of your controls and what is being attacked in your sector; consequence in downtime, money and obligation — the units the board already reasons in. Each scenario placed, with the reasoning written down beside it.
Rank and choose treatment
For each ranked risk: reduce it, transfer it, avoid it, or accept it knowingly — each with a named owner, a cost, and a date it gets looked at again. A register where every line is a decision, not an observation.
The distinction
A scanner ranks weaknesses; a risk assessment ranks losses
A vulnerability assessment is a technical scan: it enumerates the weaknesses in the estate and scores them by technical severity. It is necessary, and it answers a different question. The highest-severity finding on the scan may sit on a system whose loss the business would barely notice, while a modest weakness sits in the path of the process that produces most of the revenue. Severity describes the flaw; risk describes what the flaw can cost you — and only the second ranking can direct a budget. We keep a separate guide on choosing between a vulnerability assessment and a penetration test; this engagement sits above both, deciding where either is worth pointing.
The failure mode of risk work is abstraction: a heat map of coloured squares that offends nobody and decides nothing. The guard against it is writing consequence in real units — hours of production lost, payments that cannot be made, an obligation to notify a regulator — attached to scenarios concrete enough that the process owner recognises their own operation in them. A register in those terms produces arguments in the room, and the arguments are the value: they are the leadership team discovering it disagrees about what matters, while that disagreement is still cheap.
How it runs
The audit-committee question, turned into a ranked answer
Typical engagement — illustrative, not a named client
A mid-sized distribution business is asked by its audit committee how exposed it is to cyber loss and whether the security spend is pointed at the right things. The security team has scan reports and a control list, but no way to connect either to the question being asked.
- 01Workshops with operations, finance and IT name the processes whose interruption the business would feel within a day, and what a day of each actually costs — an exercise finance had never been asked to join before.
- 02Threat scenarios are built against those processes and judged for likelihood against the current state of the controls, with the reasoning recorded so the committee can interrogate it rather than take it on faith.
- 03The register ranks the scenarios and puts a treatment decision, owner and cost against each — including two risks proposed for explicit acceptance, with the committee, not the security team, as the accepting authority.
The committee gets an answer in its own units, the security budget is re-argued from the register rather than from vendor renewals, and the next assessment is an update to a living document instead of a fresh start.
Our role
What we quantify and which calls stay in your risk committee
- 01
Scenarios grounded in your operation
We build the scenarios with your process owners rather than importing a generic library, because the risks that surprise organisations live in dependencies only their own people know about.
- 02
Judgement shown, not asserted
Every likelihood and consequence rating carries its reasoning, so the register can be challenged line by line — a rating that cannot be argued with cannot be trusted either.
- 03
A register built to stay alive
We hand over the register with its review rhythm, owners and triggers, so the next material change to the business updates it rather than invalidating it.
What the business accepts, transfers or spends to reduce is a decision for your leadership — our work is to make sure that decision is made about a ranked, argued, recognisable picture of your exposure rather than a coloured grid.
Common questions
What buyers ask
Our team already runs vulnerability scans — why commission a risk assessment on top?+
Because the scan and the assessment answer different questions for different audiences. The scan tells engineers which weaknesses exist and how severe each is technically; it cannot say which weakness sits in the path of the process that earns the revenue, or what a week of that process stopping costs. The risk assessment supplies exactly that translation — scenarios, likelihood, consequence in business units — and it is what lets a leadership team choose between competing spends. The scan feeds the assessment; it does not replace it, in either direction.
How do you judge likelihood without years of our incident data?+
From three sources that exist even when incident history does not: the state of your controls against each scenario, what is demonstrably being attacked in your sector and region, and the exposure your specific dependencies create. The judgement is comparative rather than actuarial — this scenario is materially more likely than that one, for reasons written down — which is sufficient for its purpose, because the register exists to rank risks against each other for treatment, not to price them to the riyal. Where a figure genuinely cannot be defended, we say so rather than decorate the register with false precision.
What should trigger an update to the risk register between annual reviews?+
Any change that moves a likelihood or a consequence: a new critical system or supplier, a major integration, an acquisition, a regulatory change, an incident — yours or a peer's that proves a scenario is live — or a control that materially improved or quietly lapsed. The register we hand over carries these triggers explicitly, with an owner for each, because a register updated only on the anniversary describes the organisation as it was, and the decisions made from it inherit the staleness.
In this cluster
Next step
Build your register with us
A scoping conversation that names the business processes the assessment must cover and the decision forum the register will be written for.
