08 Nov 2026 By CISO Consulting team 35 views 5 min read

SAMA CSF Domain 1: What Governance Evidence Auditors Ask For

Domain 1 of the SAMA Cyber Security Framework uses broad words like governance, accountability and oversight. This article explains the four evidence types auditors tend to request first and when a structured assessment helps.

A board table in a Riyadh office with printed governance documents and a laptop, lit by daylight.
In this article
  1. What Domain 1 is asking for
  2. Why this matters in the Kingdom
  3. The gap between policy and proof
  4. The four artifacts reviewers tend to request first
  5. 1. The cybersecurity governance charter
  6. 2. The RACI matrix
  7. 3. Meeting minutes
  8. 4. The escalation log
  9. How the four artifacts connect
  10. When a structured assessment is warranted
  11. How CISO Consulting supports this
  12. Next step

Preparing for a maturity review is easier when you know what the reviewer will ask to see. This article sets out the SAMA cyber security framework domain 1 requirements in plain terms, explains why policy documents alone often fall short, and describes the four evidence types that show governance exists in practice.

What Domain 1 is asking for

The SAMA Cyber Security Framework, issued by the Saudi Central Bank (SAMA), organizes its expectations into domains. The first covers cybersecurity governance. Its language is deliberately broad: governance, accountability, oversight, roles and responsibilities, and the alignment of cybersecurity with the institution's strategy and risk appetite.

In plain language, the domain asks a simple question: who is responsible for cybersecurity in your institution, who oversees them, and can you show that this arrangement operates rather than merely being written down?

That last part is where many submissions weaken. A well-drafted policy states intent. A reviewer assessing maturity wants to see that the intent is applied, repeatedly, by named people, with a record. Exact control wording and numbering should always be taken from the current published framework and any circulars that apply to your institution.

Why this matters in the Kingdom

For a regulated institution, the maturity rating is not an internal exercise. It shapes the conversation with the regulator, the attention of the board and the priority given to remediation funding. Governance is also the domain on which the others depend. If ownership, reporting lines and escalation are unclear, weaknesses in operations, third-party risk or incident response are harder to detect and slower to resolve.

Boards and executive committees also carry accountability here. Domain 1 is as much about demonstrating that senior management is informed and engaged as it is about the security team's own practices.

The gap between policy and proof

A typical first submission includes a cybersecurity policy, an information security strategy and an organization chart. These are necessary, but they answer the question "is governance defined?" Reviewers usually go further and ask "does governance function?" Four evidence types address that second question most directly.

The four artifacts reviewers tend to request first

1. The cybersecurity governance charter

The charter establishes the authority behind the function. A useful one states:

  • the mandate of the cybersecurity function and its reporting line
  • the role of the board or its delegated committee in oversight
  • the composition, purpose and meeting frequency of any cybersecurity steering committee
  • how the charter is approved, reviewed and updated

Common weaknesses are an unsigned or undated document, a charter that has never been reviewed, and a reporting line that differs from what the organization chart shows. Reviewers notice inconsistencies between documents quickly.

2. The RACI matrix

A RACI matrix sets out who is Responsible, Accountable, Consulted and Informed for cybersecurity activities. It turns the word "accountability" into something testable.

A strong RACI covers the real activities of the institution, such as risk acceptance, incident declaration, access reviews, third-party onboarding and policy approval, rather than generic headings. Each activity should have a single accountable owner. Where two functions are both marked accountable, a reviewer will reasonably ask who actually decides.

It also needs to match reality. If the matrix names a role that does not exist, or a person who has left, it signals that the document is not maintained.

3. Meeting minutes

Minutes are the most persuasive evidence of oversight because they are produced as a by-product of the work. Reviewers typically look for:

  • a regular cadence consistent with the charter
  • recorded attendance, including senior stakeholders
  • cybersecurity risk, metrics and incidents on the agenda
  • decisions and actions, with owners and dates
  • follow-up on actions from earlier meetings

Minutes that record only that a topic was "discussed" show little. Minutes that record a decision, an owner and later closure show governance at work. Gaps in the calendar, or a charter that promises quarterly meetings while the record shows two in a year, are the kind of mismatch that lowers a rating.

4. The escalation log

The escalation log shows that issues travel upward to the people with authority to act. It might record security incidents, risk acceptances, policy exceptions, overdue remediation items and regulatory matters, together with who was told, when, and what was decided.

This artifact is often missing because escalation happens by email or conversation and is never consolidated. If that is your situation, start by collecting existing records into a single register with consistent fields. A log that begins today and is kept consistently is more credible than a reconstructed history.

How the four artifacts connect

Reviewers often test the artifacts against one another. The charter says who should meet and escalate. The RACI says who owns each decision. The minutes show the meetings happened. The log shows that matters reached the right forum. When all four agree, governance is demonstrable. When they conflict, the policy documents lose weight, however well written.

A practical self-check before a review:

  1. Read the charter and list every commitment it makes (frequency, membership, reporting).
  2. Compare each commitment with the minutes and the log.
  3. Compare the RACI with current role holders and the organization chart.
  4. Note every mismatch, then decide whether to change the document or change the practice.

Changing the document to match a weak practice is sometimes appropriate, but it should be a deliberate decision. Documents should describe what the institution intends to do and then actually does.

When a structured assessment is warranted

An internal review can resolve a missing log or an outdated RACI. A structured assessment is more appropriate when:

  • you have been notified of a maturity review and need a defensible position within a fixed timeline
  • gaps appear across several domains and you must decide what to fix first
  • ownership of remediation is unclear between security, risk, IT and the business
  • the board needs an independent view of where the institution stands

How CISO Consulting supports this

Our SAMA Cyber Security Framework service covers maturity assessment, gap remediation and evidence preparation against the SAMA Cyber Security Framework. The assessment phase runs 6–10 weeks, and remediation follows as planned. Each control receives an evidence-based maturity rating, and gaps are prioritized by risk, effort and regulatory weight.

The deliverables include a maturity assessment report by domain and control, a gap analysis with a prioritized remediation roadmap, updated policies, standards and procedures, an evidence pack and index, and an executive summary for the board. The evidence pack is organized for reviewers, so artifacts such as the charter, RACI, minutes and escalation log can be located and traced without searching.

On versions, we work from the current published framework and any circulars that apply to your institution at the time of the engagement.

Next step

If a maturity review is approaching, begin by testing your four governance artifacts against one another. If the results show gaps you cannot close alone, or you need a defensible position on a fixed timeline, speak with us about the SAMA Cyber Security Framework service.

Tags: SAMA CSF Cybersecurity Governance Maturity Assessment GRC Saudi Financial Sector Audit Evidence
Readiness self-check

How ready are you? Find out in two minutes

Answer a few questions for your framework. You get a score, your biggest gaps and — if you want it — a detailed assessment from our team.

Ready to talk about your compliance?

Tell us where you stand. We will show you the shortest path to what your regulator expects.

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment