Saudi Arabian Monetary Authority Cyber Security Framework

· About Saudi Arabian Monetary Authority Cyber Security Framework

Key Takeaways

  • The Saudi Central Bank (SAMA) Cyber Security Framework is a mandatory framework for financial institutions regulated by SAMA, and it remains in force on the SAMA Rulebook as of 2026.[1][5]
  • The framework applies to the regulated banking and broader financial sector, including member organizations covered by SAMA’s cybersecurity rules, and it is organized into four domains: governance, risk/compliance, operations/technology, and third-party cyber security.[1][3]
  • SAMA issued the framework under Circular No. 381000091275, dated 28/8/1438H (24 May 2017), and the published framework says it supersedes prior SAMA cyber-security circulars.[2][8]
  • SAMA states it will periodically review and update the framework to address emerging threats, but the public rulebook materials do not show a later wholesale replacement as of 2026.[3][9]
  • Member organizations must use the framework to assess cyber maturity and compliance, and the framework is built on national and international good practice, including NIST, ISO, PCI, and BASEL references.[8][14]
  • Where controls cannot be implemented as written, the framework contemplates compensating controls, internal risk acceptance, and formal waiver or update requests to SAMA, which means noncompliance is managed as a supervisory issue rather than an optional deviation.[2][12]

What It Is

The SAMA Cyber Security Framework is the Saudi Central Bank’s sectoral cybersecurity rulebook for financial institutions it regulates, designed to help member organizations identify and manage cyber risk and protect information assets and online services.[3][8] It is enforced by the Saudi Central Bank / SAMA through its rulebook and supervision of regulated financial institutions.[1][5]

The framework was issued under Circular No. 381000091275 on 28/8/1438H (24 May 2017).[2][8] The public rulebook shows the framework as in force in 2026.[5] SAMA also states it will review the framework periodically and publish updates when needed, but the current public sources do not identify a complete 2025–2026 replacement or a formal delay to implementation of the existing framework.[3][9]

The framework is structured around four domains: Cyber Security Leadership and Governance; Cyber Security Risk Management and Compliance; Cyber Security Operations and Technology; and Third Party Cyber Security.[1] SAMA says changes to the framework are communicated to member organizations and earlier versions are retired when revised.[3]

Who Must Comply

The framework applies to financial institutions regulated by SAMA—its own term is member organizations—including institutions covered by the framework and related banking-sector participants described in SAMA materials.[3][8] The public SAMA materials also describe the framework as sector-wide for the Saudi banking sector and related regulated entities.[7][15]

Its reach is effectively extraterritorial for regulated groups in the sense that it applies to regulated banking groups and subsidiaries where the SAMA supervisory perimeter extends, including Saudi banks and their subsidiaries, and foreign-bank subsidiaries in Saudi Arabia in related SAMA sector guidance.[7] The framework also addresses third parties, so outsourcing does not remove responsibility for cyber controls.[1]

The public materials do not list a broad public-sector or consumer exemption regime; instead, they focus on applicability to regulated financial institutions and on specific implementation differences for different member organizations.[3][15] Where a control cannot be implemented, the framework allows the institution to seek an update, use compensating controls, and manage the gap formally with SAMA.[2][12]

Core Requirements

  1. Governance and accountability — Institutions must establish cyber-security leadership and governance so cyber risk is owned at senior levels and managed as a formal control area.[1][8]
  1. Risk management and compliance — Institutions must identify, assess, and manage cyber risk through a structured risk framework and align their program to the framework’s maturity expectations.[8][15]
  1. Operational security controls — Institutions must implement technical and operational safeguards across systems, services, and information assets, including controls that support secure operations and resilience.[1][8]
  1. Third-party cyber security — Institutions must manage cyber risk introduced by vendors, service providers, and outsourced arrangements under the third-party domain.[1]
  1. Assessment and maturity measurement — Institutions must periodically assess their cyber-security maturity and effectiveness using the framework’s review model and self-assessment approach.[8][15]
  1. Exception handling and escalation — If a requirement cannot be met, the institution should use compensating controls, record risk acceptance, and seek formal SAMA review or framework update rather than treat the control as waived by default.[2][12]

Deadlines and Penalties

| milestone | date | what applies | |---|---:|---| | Framework issued | 24 May 2017 | SAMA issued the Cyber Security Framework under Circular No. 381000091275.[2][8] | | Framework in force | ongoing | The SAMA Rulebook lists the framework as in force in 2026.[5] | | Periodic review/update cycle | ongoing | SAMA states it periodically reviews and updates the framework as needed.[3] |

SAMA’s public framework materials do not publish a single numeric penalty schedule inside the framework text. The practical consequence of noncompliance is supervisory action through SAMA’s regulatory powers, including findings, remediation demands, and potential enforcement measures under the broader Saudi banking and financial regulatory regime.[5][8] The framework itself also signals that unimplemented controls must be handled through formal exception management, which makes deviations auditable and supervisory issues rather than informal choices.[2][12]

How to Comply

  1. Map scope and ownership — Identify every regulated entity, branch, subsidiary, and outsourced service in scope, then assign accountable executives and control owners aligned to the framework’s governance domain.[1][7]
  1. Build a control inventory — Translate the framework into a control register and map each requirement to existing policies, procedures, and technologies, using ISO 27001 as the management-system backbone where applicable.[8][14]
  1. Run a maturity assessment — Perform a baseline self-assessment against the framework and track gaps by domain, evidence, and remediation date; the framework is designed to measure maturity and effectiveness.[8][15]
  1. Strengthen core cyber operations — Align detection, response, recovery, logging, vulnerability management, and secure configuration with NIST CSF 2.0 functions and categories, then document where the SAMA requirement is stricter.[1][14]
  1. Control third parties — Put cybersecurity clauses, audit rights, incident-notification obligations, and resilience requirements into supplier contracts and monitor them through periodic reviews.[1]
  1. Formalize exceptions — Where a control cannot be met, create a documented compensating-control package, risk acceptance, and SAMA-facing update request where needed.[2][12]
  1. Test and evidence — Run tabletop exercises, technical testing, and control-assurance reviews, then retain evidence that can support supervisory review and internal audit.[3][8]
  1. Use an AI-governance overlay for emerging tech — Where cloud, digital banking, or AI tools are used, align governance to ISO 42001 so model risk, data governance, and supplier controls are documented in a way that supports the SAMA framework’s governance and third-party expectations.[1][14]

Related Regulations

  • Saudi Personal Data Protection Law (PDPL) — PDPL overlaps where cyber controls process personal data, but the SAMA framework is sector-specific and typically more operationally prescriptive for regulated financial institutions.
  • Saudi Essential Cybersecurity Controls (ECC) — ECC can overlap on baseline security obligations, but SAMA’s framework is the financial-sector regime for SAMA-regulated entities.
  • SAMA Cyber Resilience Fundamental Requirements (CRFR) — CRFR complements the framework by addressing resilience expectations and incident preparedness in the same supervisory perimeter.[10]
  • NCA Essential Cybersecurity Controls — NCA controls can conflict or duplicate in groups that sit under multiple Saudi regulatory regimes, so institutions should map the stricter requirement and resolve overlaps centrally.
  • SWIFT Customer Security Controls Framework — SWIFT requirements often apply to payment and messaging environments, and they should be aligned with, not treated as a substitute for, SAMA’s framework.[8][14]

Does the framework apply to companies outside Saudi Arabia?

It can, if the company is part of a SAMA-regulated group or is otherwise within SAMA’s supervisory perimeter through a Saudi branch, subsidiary, or regulated banking relationship.[7][8] The key question is not incorporation alone, but whether SAMA regulates the relevant entity or activity.

Is the framework still in force in 2026?

Yes. The SAMA Rulebook lists the Cyber Security Framework as in force, and the published framework materials remain active on the rulebook and SAMA sites in 2026.[5][1]

Has SAMA replaced the framework with a newer version?

The public materials reviewed do not show a full replacement or a new consolidated version superseding the 2017 framework as of 2026. SAMA does state that it periodically reviews and may update the framework, so institutions should watch for rulebook revisions.[3][9]

Does the framework cover cloud computing and digital banking?

Yes, in operational effect. The framework’s controls cover cyber governance, operations, and third-party risk, which are the core domains used to govern cloud and digital channels, even if the public summary does not isolate cloud into a standalone chapter.[1][8]

What happens if a bank cannot implement a control exactly as written?

The framework contemplates compensating controls, risk acceptance, and a formal update request to SAMA when a member organization believes an update is needed.[2][3] That means exceptions must be documented and defensible, not left informal.

Sources

Put it into practice

More compliance guides