The Saudi Central Bank (SAMA) issued its Business Continuity Management (BCM) Framework on 27 February 2017 (1/6/1438H). It is the document that codifies what SAMA expects from the institutions it supervises when it comes to preparing for, responding to and recovering from disruption. In SAMA's rulebook it is listed as in force.
This guide is the cornerstone of our SAMA series. It walks through who the framework applies to, its 13 requirement areas, the overlap with ISO 22301, and a realistic path to compliance for a mid-market institution. It summarises the framework in our own words; always work from the official text for compliance decisions.
Who the SAMA BCM Framework applies to
Section 1.4 of the framework lists who must comply:
- All organisations affiliated with SAMA (the framework's "Member Organizations")
- All banks operating in Saudi Arabia
- All banking subsidiaries of Saudi banks
- Subsidiaries of foreign banks situated in Saudi Arabia
In May 2022, SAMA extended the framework to insurance and reinsurance companies (circular 202200000249). Insurers had to assess their gaps against it, submit a plan within ninety working days, report progress quarterly from the end of the first quarter of 2023, and reach full compliance within a year.
The scope is the whole institution: section 1.3 extends it to subsidiaries, employees, subcontractors, third parties and customers. If you are a finance company, payment service provider or fintech, check the circulars that apply to your licence category for how the framework reaches you.
How the framework is structured: 13 requirement areas
Section 2, "Business Continuity Requirements", is where the obligations sit. It is organised into 13 areas:
| # | Requirement area | What it covers, in brief |
|---|---|---|
| 2.1 | BCM Governance | Board ownership, a board-mandated BCM committee, a BCM manager and a dedicated BCM function |
| 2.2 | BCM Strategy | A business continuity strategy aligned to the institution's objectives |
| 2.3 | Business Continuity Policy | An approved policy that sets the programme's scope and rules |
| 2.4 | Business Impact Analysis (BIA) and Risk Assessment (RA) | Identifying critical activities, their impacts over time, recovery objectives and the risks to them |
| 2.5 | Business Continuity Plan (BCP) | Plans to continue critical activities through a disruption |
| 2.6 | IT Disaster Recovery Plan (DRP) | Plans to recover the technology that critical activities depend on |
| 2.7 | Cyber Resilience | Continuity and recovery in the face of cyber incidents |
| 2.8 | Crisis Management Plan | How the institution manages a crisis, including decision-making and escalation |
| 2.9 | Testing | Regular BCP and DRP tests, and records of the tests executed |
| 2.10 | Awareness and Training | Making sure employees and third parties can carry out the plans |
| 2.11 | Communication | Internal and external communication about BCM and during incidents |
| 2.12 | Periodic Documents Review | Keeping BCM documents current through scheduled reviews |
| 2.13 | Assurance | Independent checks that the programme works as intended |
Each area is written as a principle, an objective and a set of control considerations. Two areas are worth reading closely because they are more prescriptive than ISO 22301.
Governance (2.1). The board, or a delegated executive member, holds ultimate responsibility for the BCM programme and should allocate budget for it. The board should mandate a BCM committee with senior-management representation; the framework's examples include the CRO, COO, CIO, CISO and the BCM manager. The committee needs a charter covering objectives, roles, a minimum number of participants and meeting frequency, with meetings at least quarterly. A qualified BCM manager should be formally appointed, and a dedicated, adequately staffed BCM function established.
Testing (2.9). BCP and DRP tests should be defined, approved, executed and monitored on a regular basis, both to train employees and third parties and to prove the plans work as written. The framework splits this into BCP testing, DRP testing and executed tests, so keep evidence for each.
SAMA versus ISO 22301 — where they align and where they don't
SAMA's framework draws on international BCM practice, and an institution running an ISO 22301 management system will already cover much of it: impact analysis, plans, testing, documented review and continual improvement all have direct counterparts.
The differences that matter in practice:
- It is mandatory. ISO 22301 is a voluntary, certifiable standard. The SAMA framework is a regulatory requirement for in-scope institutions, assessed by the regulator rather than a certification body.
- Governance is prescribed. ISO 22301 requires leadership commitment but leaves the structure open. SAMA expects a board-mandated committee with senior-management members, a charter and at least quarterly meetings.
- IT disaster recovery and cyber resilience are their own areas. ISO 22301 treats technology recovery inside the general continuity solutions. SAMA gives the IT DRP (2.6) and cyber resilience (2.7) dedicated requirement areas, and testing (2.9) covers DRP tests explicitly.
- A crisis management plan is required. ISO 22301 covers response structures generally; SAMA calls out a crisis management plan as its own area (2.8).
- Awareness, communication and document review are explicit. SAMA gives each its own area (2.10 to 2.12), where ISO 22301 spreads them across support and performance clauses.
The most efficient path is to run the management system to ISO 22301 and layer the SAMA-specific evidence on top, rather than running two programmes. See the ISO 22301 implementation guide for the underlying structure.
What a SAMA examiner samples first
Examination scope varies, but the evidence that proves a programme is real is predictable. In our experience the strongest opening set is:
- The BCM committee charter and recent minutes. They show governance is operating, not just documented.
- The latest BIA for the most critical service. Usually card authorisation, core banking, or a fintech's primary product. Dependencies and impact ratings should be current.
- The BCP and IT DRP for that same service. Activation criteria, roles, recovery objectives and recovery steps.
- Test records for those plans. When each was tested, what was observed, and which improvement actions followed.
- Assurance and review records. Evidence that someone independent checked the programme and that leadership saw the results.
The three most common SAMA findings
Across the engagements we have visibility into, three patterns recur:
Finding 1: Plans authored, not tested. BCPs and DRPs sit in the document repository, last touched the day they were approved. No test schedule covers them and no post-test report exists. The fix is unglamorous: schedule regular tests, run at least a tabletop for each critical plan, and record observations with named improvement actions.
Finding 2: Stale BIAs. The BIA was performed once, two or three years ago. Critical processes have changed since and the dependency map no longer reflects reality. Make the BIA a scheduled artefact owned by process owners, with a review trigger when a process changes materially.
Finding 3: Governance on paper. The committee exists in the charter, but minutes are thin, quarterly meetings slip, and decisions are not traceable to actions. Use a standing agenda with named inputs (test results, open actions, BIA changes) and record decisions and owners every time.
All three are operational discipline issues, not framework-interpretation issues.
A realistic 12-month SAMA compliance roadmap
For an institution starting from a low baseline, a typical sequence looks like this:
Months 1-2: Governance, strategy and policy (2.1 to 2.3). Obtain the board mandate, charter the BCM committee, appoint the BCM manager, and approve the strategy and policy.
Months 2-4: BIA and risk assessment (2.4). Run BIA workshops for every critical activity. Capture impacts over time, dependencies and recovery objectives, and assess the risks to them.
Months 4-7: Plans (2.5 to 2.8). Author BCPs, IT DRPs and the crisis management plan for critical activities, covering cyber scenarios. Version-control everything.
Months 7-9: Testing (2.9). Build the test schedule, run tests for the top plans, and record results and improvement actions.
Months 9-10: Awareness, communication and review (2.10 to 2.12). Run training, confirm communication routes, and complete the first scheduled document review.
Months 10-12: Assurance (2.13). Commission an independent review of the programme, address findings, and prepare the evidence set for supervisory dialogue.
A platform that keeps BIAs, plans and tests in one dataset can shorten the plan-and-test phases. Committee, policy and training work still depends on people and approvals, so do not plan on software compressing those.
The evidence pack
Whether the request comes from an examiner, internal audit or the board, keep these ready:
- Board mandate, BCM committee charter and recent minutes
- BCM strategy and policy, with approval records
- BIA and risk assessment summaries for critical activities
- BCP, IT DRP and crisis management plan register, with status and owners
- Test schedule, test records and improvement actions
- Training and awareness records
- Document-review log
- Assurance reports and management responses
The pack is most credible when it comes from a single underlying dataset: tests that reference real plan IDs, improvement actions that trace back to test observations, and minutes that reference real BIA outcomes. Building each artefact separately in Word or Excel makes inconsistencies likely.
Where SAMA is heading
SAMA had not published a dedicated operational resilience framework as of January 2026, according to KPMG in Saudi Arabia, though supervisory expectations have tightened. Two practical implications follow.
First, treat cyber and continuity as one programme. The framework's cyber resilience area overlaps with the NCA ECC cybersecurity resilience controls, so institutions in scope of both should evidence them together.
Second, expect more attention on third parties. The framework's scope already extends to subcontractors and third parties. Keep continuity evidence for critical vendors, including their test results and your plans for their failure.
How BCMStack maps to the requirement areas
BCMStack covers governance, policy and training records as well as the analysis, planning, testing and incident areas.
| SAMA requirement area | BCMStack module | What it covers |
|---|---|---|
| 2.1 Governance | Governance | The BCM committee's seats and deputies, meetings with attendance and quorum, and a decision register linked to the records it concerns and the improvement actions it raised |
| 2.3 BCM policy | Governance | The policy, charter and methodologies, versioned, approved by someone other than the author, with review dates |
| 2.4 BIA and RA | BIA · Risk | Guided BIA with impact over time, dependencies and recovery objectives; a risk register linked to processes, applications, vendors and locations |
| 2.5 BCP | BCP | Plans with structured fields, phased recovery steps, communications and an activation log |
| 2.8 Crisis Management Plan | Crisis | Crisis events with actions, impacts, decisions and BCP activation |
| 2.9 Testing | Exercises | Test programmes, scenarios, injects, observations and after-action reviews, including DR tests |
| 2.10 Awareness and training | Governance | Courses and completion records, and coverage of everyone named in an approved plan |
| 2.11 Communication | Call trees · Crisis | Call trees with acknowledgement tracking, and a crisis communications log |
| 2.13 Assurance | Reporting | Cross-module reporting and PDF exports from one audit trail |
Because these areas share one dataset, the evidence agrees with itself: a test references the plan it tested, and an improvement action traces back to the observation that raised it.
Where to start
If you are early in your SAMA BCM journey, the highest-leverage moves in the first ninety days are:
- Get the board mandate and charter the committee. Without operating governance, every other artefact goes stale.
- Define scope tightly. Identify the critical activities and ringfence them.
- Get one critical service to BIA-and-plan quality. Use it as the template for the rest.
- Run a test early. It exposes gaps that documentation alone hides.
- Build the evidence pack as you go. Every artefact should be reusable in supervisory dialogue.
The cluster articles in this series unpack each move:
- What SAMA examiners ask first — the opening-meeting script
- How to write a SAMA-grade BCM committee charter
- How to implement ISO 22301 in Saudi Arabia — the management-system foundation SAMA evidence sits on
If your institution is also in scope for the National Cybersecurity Authority's controls, read NCA ECC business continuity requirements next, and NCA ECC vs SAMA BCM if both apply to you.
To see how BCMStack works for Saudi institutions, see business continuity software in Saudi Arabia.
Sources: SAMA BCM Framework (rulebook), section 2 requirement areas, 2.1 BCM Governance, 2.9 Testing, May 2022 circular for insurers.