15 Nov 2026 By CISO Consulting team 40 views 5 min read

SAMA ITGF Cybersecurity Audit Scope: Four Documents First

SAMA ITGF requires regular cybersecurity audits, yet many audits begin before scope is defined. This guide sets out the four scoping documents internal audit should finalize before an external assessor arrives.

An internal audit manager reviewing an audit plan with colleagues at a meeting table in a modern Saudi office.
In this article
  1. What the framework expects
  2. What changes for the organization
  3. The usual gaps
  4. The four scoping documents
  5. 1. Asset inventory for the audit universe
  6. 2. Control-framework mapping
  7. 3. Prior-year findings register
  8. 4. Risk-based sampling rationale
  9. A sensible order of work
  10. How we support internal audit
  11. Next step

Annual planning for cybersecurity assurance usually starts with a question about the assessor: who, when and at what cost. A better starting point is the SAMA ITGF cybersecurity audit scope. When internal audit has not defined what is in and out of scope before fieldwork begins, the result is often incomplete coverage of critical systems or duplicate testing of areas already reviewed. This article explains what the SAMA IT Governance Framework (ITGF) expects regarding cybersecurity audit, and the four scoping documents internal audit should finalize before an external assessor arrives.

What the framework expects

The Saudi Central Bank (SAMA) issues the IT Governance Framework for the institutions it regulates. Within its audit-related provisions, it expects cybersecurity to be subject to independent audit on a recurring basis, with the results reported to senior governance bodies. We refer to this requirement here by its subject rather than by a clause number, so confirm the exact article reference against the current published version of the framework used by your institution.

In practical terms, the requirement has three consequences for internal audit:

  • Cybersecurity must appear in the audit plan every year, not only when an incident or a regulatory visit prompts it.
  • The audit must be independent of the teams that operate the controls.
  • Findings must reach the audit committee and be tracked until corrective action is verified.

SAMA also publishes the Cyber Security Framework (SAMA CSF), and many entities are subject to the NCA Essential Cybersecurity Controls (ECC). The audit scope therefore usually has to reflect more than one set of expectations at the same time.

What changes for the organization

An annual requirement turns cybersecurity audit from an event into a program. Internal audit has to decide what is covered each year, how coverage rotates, and how it can show the audit committee and SAMA that high-risk areas are not repeatedly deferred. That decision is much easier to defend when it is documented before the engagement, not reconstructed afterwards from the assessor's report.

The usual gaps

  • The assessor is briefed verbally, so scope depends on who attended the kickoff meeting.
  • The asset list used for the audit differs from the one operations uses, so systems are missed.
  • Controls are tested against one framework while the committee expects another.
  • Last year's findings are not carried into the plan, so closed items are retested and open items are overlooked.
  • Sample sizes are chosen by convenience, and nobody can explain them to the committee.

Each gap maps to one scoping document.

The four scoping documents

1. Asset inventory for the audit universe

This is the list of systems, applications, networks, data stores and third-party services that could be audited. It should be reconciled with the inventory held by IT and security, and marked to show which assets are critical, which hold sensitive data, and which are externally exposed or operated by a vendor.

The point is not to audit everything. It is to make the boundary explicit, so that exclusions are decisions and not accidents.

2. Control-framework mapping

Map the controls to be tested to the frameworks that apply to your institution, such as SAMA CSF, SAMA ITGF and NCA ECC where relevant. One control often satisfies several requirements, and a single test can serve all of them. A mapping prepared in advance avoids testing the same control three times under three names, and shows the audit committee which obligations the year's plan covers.

3. Prior-year findings register

List every finding from earlier internal audits, external assessments and regulatory observations, with owner, agreed action, due date and current status. This register does two jobs. It tells the assessor which areas need verification of corrective action, and it prevents re-raising issues management has already resolved. It also gives the committee a clear view of whether remediation is genuinely progressing.

4. Risk-based sampling rationale

Record how populations will be sampled and why. For example, which systems get full testing, which get sampled, and what drives the difference: criticality, change volume, prior findings or incident history. Include the evidence types you expect, such as configuration extracts, access reviews, tickets and logs. A written rationale makes the sample defensible when someone asks why one system was tested and another was not.

A sensible order of work

  1. Reconcile the asset inventory and agree the audit universe with IT and security.
  2. Map controls to the applicable frameworks and select the control set for this year.
  3. Update the findings register and flag items needing verification.
  4. Draft the sampling rationale, using the risk ranking from the first three steps.
  5. Obtain audit committee review of the resulting scope before fieldwork is scheduled.
  6. Brief the assessor in writing, using the four documents as the engagement baseline.

Finishing these before fieldwork starts is what allows the assessor's time to be spent on testing rather than on discovering what the audit is supposed to cover.

How we support internal audit

We perform cybersecurity audits on behalf of, or alongside, your internal audit function. Each audit is planned, executed and reported to internal audit standards, giving your audit committee independent assurance from cybersecurity specialists.

Our process has four stages: plan the scope, risks and audit program; carry out fieldwork with testing and evidence collection; report findings agreed with management; and follow up by verifying corrective actions. The four scoping documents above feed directly into the first stage, so work you complete beforehand shortens planning and sharpens the audit program.

The audit includes risk-based audit planning, design and operating effectiveness testing, sampling and evidence review, and rated findings with management responses. We also carry out follow-up audits. The deliverables are an audit plan and program, working papers, an audit report for the audit committee, and a follow-up report. An audit takes 3–6 weeks per audit (assessment), and our work covers SAMA CSF, NCA ECC and SAMA ITGF.

Next step

If you are building the annual cybersecurity audit program, start by drafting the four documents and test them against last year's audit. If you would like a specialist partner to plan and execute the audit alongside your team, our Internal Cybersecurity Audit service is designed for that.

Tags: SAMA ITGF Internal Audit Cybersecurity Audit Audit Scoping Regulatory Compliance Audit Committee
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