A SAMA CSF cybersecurity roadmap governance Domain 1 sequence is not the usual starting point. Most roadmaps open with technical controls and incident-response capability, because those are visible and easy to justify. Yet institutions in the Eastern Province that have worked through this problem often reach the same conclusion: improvements to incident response do not last when the governance beneath them is informal.
This article explains why governance maturity under the SAMA Cyber Security Framework (CSF) is a sound first phase of a three-year roadmap, which artifacts make that phase concrete, and how a phased board-reporting sequence can bring sponsorship and budget forward.
The pattern: Domain 4 gains that do not hold
The SAMA CSF is issued by the Saudi Central Bank (SAMA) for the financial sector. Its first domain addresses cybersecurity leadership and governance. Its fourth covers cybersecurity operations and technology, including incident management.
The pattern is familiar. An institution invests in detection, playbooks and response exercises. Results improve for a while, then drift. The cause is rarely technical. Typical causes are:
- Nobody is clearly accountable for deciding when an incident is escalated to executives.
- The board has never stated how much cyber risk the institution is willing to accept, so response priorities are set case by case.
- Oversight happens through conversations rather than a recurring, documented forum.
Without governance, incident response depends on individuals. When those individuals change, or when the next budget cycle arrives, the capability weakens.
Signs it is time to sequence governance first
A governance-first roadmap is worth considering when several of these are true:
- Security responsibilities are spread across IT, risk and operations without a written division of duties.
- There is no approved risk-appetite or risk-tolerance statement for cyber risk.
- The board receives security updates irregularly, or as activity lists rather than measures.
- Previous improvement programs delivered tools but not lasting change.
- Budget requests are reviewed one initiative at a time, with no multi-year view.
The governance artifacts that matter
Three artifacts carry most of the weight in a Domain 1 phase.
Role and accountability matrices (RACI)
A RACI matrix states who is responsible, accountable, consulted and informed for each significant security decision. The most useful ones are written around decisions rather than job titles: declaring a major incident, accepting a risk, approving an exception, notifying a regulator. Once written, these matrices expose gaps and overlaps quickly, and they give incident response a clear chain of authority to rely on later.
Risk-tolerance thresholds
A risk-appetite statement is only usable when it is translated into thresholds that operational teams can apply. For example, it might define the level of service disruption, data exposure or financial loss that triggers escalation to a senior committee or the board. These thresholds turn Domain 4 from a technical exercise into one driven by agreed business limits.
Quarterly board metrics
A small, stable set of measures reported every quarter gives the board a consistent view. Key risk indicators (KRIs) show exposure, and key performance indicators (KPIs) show delivery against the roadmap. Stability matters more than volume: the same measures reported over several quarters show direction in a way that a one-off, detailed report cannot.
Why this sequencing supports Domain 4
Once these artifacts exist, incident-response investment has something to attach to. Escalation paths follow the RACI. Severity levels follow the risk thresholds. Reporting to the board follows the quarterly metrics. Improvements are therefore recorded, owned and visible, which makes them harder to lose when staff or priorities change.
This does not mean technical work pauses for a year. A sensible roadmap places urgent control gaps in the first phase alongside governance. The point is about sequence and emphasis: governance maturity comes first in the plan and is treated as the foundation, not as paperwork to finish later.
A phased board-reporting sequence
A common reason roadmaps stall is that the board is asked to approve a large multi-year business case in a single step. A phased sequence is easier to decide on and shows value earlier:
- Baseline and gaps. Present the current maturity position against the SAMA CSF and the main governance gaps, without proposing solutions in detail.
- Governance proposal. Present the draft RACI, the proposed risk-tolerance thresholds and the first set of quarterly metrics for the board to adjust and endorse.
- Costed roadmap. With governance endorsed, present the three-year roadmap with budget estimates, sequenced by dependency and risk.
- First reporting cycle. Report the first quarterly metrics, so the board sees the governance model working before committing to later phases.
Each step asks the board for a limited decision and gives it something concrete in return. Sponsorship builds through use rather than persuasion, which is why this approach can bring approval within a quarter rather than after a lengthy business-case exercise. The timing depends on each institution's governance calendar, so it should be planned against actual committee dates.
What a good outcome looks like
At the end of a well-run strategy exercise, an institution should be able to point to:
- A board-approved strategy and three-year roadmap with budget estimates.
- Documented roles and decision rights for security.
- Risk-tolerance thresholds that operational teams can apply.
- A KPI and KRI set reported to the board on a fixed cycle.
- A clear sequence showing which initiatives depend on which, so Domain 4 work is planned on top of governance rather than beside it.
How we run this work
Our Cybersecurity Strategy & Roadmap service translates your business priorities, regulatory obligations and threat landscape into a costed, prioritized cybersecurity strategy and multi-year roadmap. The engagement runs as a project of 6–10 weeks and follows four stages.
- Understand: interviews with leadership, and a review of the business plan, risk appetite and regulatory position.
- Assess: a maturity baseline against the applicable frameworks and the current threat picture.
- Design: objectives, initiatives, sequencing and investment, tested with stakeholders.
- Approve: a board-ready strategy, roadmap and measures, presented and adjusted for approval.
The deliverables are a cybersecurity strategy document, a three-year roadmap with budget estimates, a target operating model, a board presentation pack and a KPI and KRI dashboard definition. The frameworks we work with are SAMA CSF and NCA ECC, and the obligations that apply to you are built into the objectives and the roadmap, so compliance and security move together.
We recommend a light annual review of the strategy and a full refresh every three years, or sooner after a major change in the business or the regulatory landscape.
Next step
If your incident-response improvements keep losing ground, or your board sees security only as a list of activities, the roadmap sequence is a good place to look. Our Cybersecurity Strategy & Roadmap service is designed to give you a three-year security direction the board can approve and the team can deliver. Where leadership capacity is the constraint, our vCISO Services can provide strategic cybersecurity leadership without a full-time hire.