20 Nov 2026 By CISO Consulting team 7 views 4 min read

SAMA ITGF Cybersecurity Audit Scope Definition Explained

A scope statement decides which systems, controls and periods an audit covers, and plans built on last year's architecture can leave live services untested. This explainer sets out the components of a scope statement and why dynamic environments need regular scope updates.

An internal auditor and a CISO reviewing an architecture diagram and audit plan together at a meeting table in a Riyadh office.
In this article
  1. What a scope statement is
  2. Why scope statements go stale
  3. Why this matters under SAMA expectations
  4. Quarterly scope confirmation
  5. Questions an audit committee member can ask
  6. How we help
  7. Next step

A SAMA ITGF cybersecurity audit scope definition is the part of an audit plan that states exactly what will be examined: which systems, which controls and which period. Everything an audit committee later concludes rests on it. If a system is outside the scope statement, the audit report says nothing about it, however well the rest of the work was done.

This article explains what a scope statement contains, why it goes stale faster than most plans assume, and how scope gaps typically surface. It is written for internal auditors, audit committee members and CISOs at institutions regulated by the Saudi Central Bank (SAMA).

A note on sources: SAMA's IT Governance Framework (ITGF) and its Cyber Security Framework expect regulated institutions to maintain independent review of their cybersecurity arrangements. We do not cite specific article numbers here. Confirm the exact wording of the relevant provisions in the current framework text and in your own audit charter before relying on any summary, including this one.

What a scope statement is

In plain terms, a scope statement answers four questions before fieldwork begins:

  • What is in scope: the business services, applications, infrastructure and third-party platforms to be examined.
  • Which controls are tested: the control objectives and the framework requirements they map to.
  • Which period is covered: the dates the audit looks at, which matters when testing operating effectiveness rather than design alone.
  • What is excluded, and why: each exclusion should be explicit, reasoned and approved.

A good statement also records the source of the asset information it relies on, such as the configuration database, architecture diagrams or cloud account inventories, and the date that information was confirmed. This is the component most often missing.

Why scope statements go stale

Most annual audit plans are approved early in the cycle. They are commonly built from the previous year's plan, adjusted for known changes. That works in a stable environment. It works poorly where engineering teams provision cloud services continuously.

A cloud workload can move from a project to production without a corresponding change to the audit universe. The architecture diagram the auditor holds is accurate for the date it was drawn. The risk register may not reflect the new service. The result is a plan that is approved, followed faithfully and still incomplete.

Consider a pattern we see described in the market, presented here as an illustration and not a case study. An internal audit team, during a routine review of change records, finds that cloud infrastructure had been in production for many months while the approved cybersecurity audit plan covered only the on-premises estate. Nothing was wrong with the audit work. The scope simply described an environment that no longer existed. In such situations the institution typically rewrites the scope statement, reopens the plan with the audit committee and re-sequences fieldwork.

Why this matters under SAMA expectations

For a regulated institution, a scope gap is more than an audit inconvenience. It raises three questions a supervisor or audit committee may reasonably ask:

  1. Did independent assurance cover the systems that carry real risk?
  2. Was the committee told accurately what the assurance did and did not cover?
  3. Would management have found the control weakness through its own monitoring, or only after a failure?

An audit report that reads cleanly while omitting production services can give the committee false comfort. That is the real exposure: not the missing test, but the reliance placed on a report whose limits were not visible.

Quarterly scope confirmation

For environments that change often, an annual approval is too infrequent on its own. We suggest a lightweight quarterly confirmation, separate from re-planning the whole audit:

  1. Obtain a current inventory of production services, including cloud accounts, subscriptions and tenants, from the teams that operate them.
  2. Compare it with the audit universe and the approved scope statement.
  3. Record additions, retirements and material changes since the last confirmation.
  4. Assess whether each addition changes the risk ranking of planned audits.
  5. Report the result to the audit committee, with any approved scope amendment.

This takes little time when done routinely and a great deal when done after an incident. It also gives the CISO a standing reason to notify internal audit of architectural change, which is a healthier arrangement than discovery by sampling.

Questions an audit committee member can ask

  • When was the asset inventory behind this scope statement last confirmed, and by whom?
  • Which production cloud services were launched since the plan was approved?
  • Which exclusions are in the plan, and who approved each one?
  • Does the audit period cover the full time each in-scope control was operating?

How we help

We perform cybersecurity audits on behalf of, or alongside, your internal audit function — planned, executed and reported to internal audit standards. Scope is settled in the first stage, where we agree the scope, risks and audit program, and we use risk-based audit planning so that coverage follows where exposure actually sits.

Our process runs in four steps:

  1. Plan: scope, risks and audit program.
  2. Fieldwork: testing and evidence collection.
  3. Report: findings agreed with management.
  4. Follow up: verification of corrective actions.

Fieldwork includes design and operating effectiveness testing, with sampling and evidence review. Findings are rated and carry management responses. 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 as an assessment, and we work with SAMA CSF, NCA ECC and SAMA ITGF.

Next step

If your approved plan was built from last year's architecture, the simplest check is to reconcile it against what is in production today. Our Internal Cybersecurity Audit service can carry out that check and plan the audit around it, giving your audit committee independent assurance from cybersecurity specialists.

Tags: SAMA ITGF internal audit audit scope cloud security audit committee GRC
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