Every bank, insurer, financing company, credit bureau and financial market infrastructure regulated by the Saudi Central Bank (SAMA) has to run its cyber security programme against the SAMA Cyber Security Framework and prove it operates at maturity level 3 or higher. The framework is principle-based rather than a checklist, so the hard part is turning its domains, subdomains and control considerations into owned controls, measurable maturity and evidence SAMA will accept. This guide explains who is in scope, what the four domains require, how the maturity model and self-assessment work, how incidents are reported to SAMA, and what the framework means for service accounts, API keys and AI agents. It is written for CISOs, compliance and audit teams in Saudi financial institutions and for the technology suppliers that serve them. The national baseline from the National Cybersecurity Authority is covered separately in the Saudi NCA Essential Cybersecurity Controls Guide.
Status checked 13 November 2026: the SAMA Rulebook lists the Cyber Security Framework (number 381000091275, issued 24 May 2017) as In-Force, alongside the Cyber Resilience Fundamental Requirements (issued 1 January 2022). Confirm the current version on the SAMA Rulebook before relying on any detail here.
Key takeaways
- Level 3 is the floor. SAMA states that Member Organisations should operate at maturity level 3, structured and formalised, or higher, which means controls are defined, approved, implemented and monitored with KPIs, not just practised.
- Four domains, 32 subdomains. Leadership and Governance (7), Risk Management and Compliance (5), Operations and Technology (17) and Third Party Cyber Security (3), each with a principle, an objective and numbered control considerations.
- Governance is prescriptive. The cyber security function must be independent of IT, the committee meets at least quarterly, and the CISO is a full-time senior manager who must be a Saudi national with a SAMA no-objection.
- Non-personal privileged accounts are named. Subdomain 3.3.5 requires their use to be limited and monitored, their passwords kept confidential and changed frequently and at the end of each session, which covers service accounts and machine credentials.
- SAMA must hear about incidents immediately. Medium or high classified incidents are reported to SAMA IT Risk Supervision straight away, media contact needs SAMA's no objection, and a formal report follows once operations resume.
Scope: who and what is covered
Section 1.4 of the framework applies it to all Member Organisations regulated by SAMA:
- all banks operating in Saudi Arabia;
- all insurance and/or reinsurance companies operating in Saudi Arabia;
- all financing companies operating in Saudi Arabia;
- all credit bureaus operating in Saudi Arabia;
- the financial market infrastructure.
All domains apply to banks. For the other institution types the framework makes four adjustments, summarised below.
| Subdomain | Banks | Insurers, financing companies, credit bureaus, FMI |
|---|---|---|
| 3.1.2 Cyber Security Strategy | Applies in full, aligned with the banking sector cyber security strategy | Applies; alignment with the banking sector strategy is mandatory where applicable |
| 3.2.3 Compliance with (Inter)national Industry Standards | Applies: PCI DSS, EMV and the SWIFT Customer Security Controls Framework | Excluded, but PCI DSS and/or SWIFT CSCF should be implemented where the organisation stores, processes or transmits cardholder data or uses SWIFT services |
| 3.3.12 Payment Systems | Applies | Excluded |
| 3.3.13 Electronic Banking Services | Applies | Excluded, but multi-factor authentication should be implemented where online services are offered to customers |
The assets in scope are broad. Section 1.3 covers the Member Organisation's information assets, including electronic and physical information, applications and databases, computers and ATMs, storage devices, premises and networks. Section 1.1 states that the framework supersedes all previous SAMA circulars on cyber security, and section 1.6 makes SAMA solely responsible for interpreting its principles, objectives and control considerations.
Newly licensed entities: the Cyber Resilience Fundamental Requirements (CRFR) apply to entities intending to qualify for the SAMA Regulatory Sandbox and entities seeking a licence. SAMA describes the CRFR as a prioritised baseline aligned with the CSF and the Business Continuity Management Framework, not a replacement: entities must still comply with the CSF and other SAMA requirements after a licensing decision.
Key obligations
The framework is organised in four domains. Each subdomain carries a principle, an objective and control considerations; the table lists the subdomains as they appear in the SAMA Rulebook.
| Domain | Subdomains |
|---|---|
| 3.1 Cyber Security Leadership and Governance | 3.1.1 Cyber Security Governance; 3.1.2 Cyber Security Strategy; 3.1.3 Cyber Security Policy; 3.1.4 Cyber Security Roles and Responsibilities; 3.1.5 Cyber Security in Project Management; 3.1.6 Cyber Security Awareness; 3.1.7 Cyber Security Training |
| 3.2 Cyber Security Risk Management and Compliance | 3.2.1 Cyber Security Risk Management (identification, analysis, response, monitoring and review); 3.2.2 Regulatory Compliance; 3.2.3 Compliance with (Inter)national Industry Standards; 3.2.4 Cyber Security Review; 3.2.5 Cyber Security Audits |
| 3.3 Cyber Security Operations and Technology | 3.3.1 Human Resources; 3.3.2 Physical Security; 3.3.3 Asset Management; 3.3.4 Cyber Security Architecture; 3.3.5 Identity and Access Management; 3.3.6 Application Security; 3.3.7 Change Management; 3.3.8 Infrastructure Security; 3.3.9 Cryptography; 3.3.10 Bring Your Own Device; 3.3.11 Secure Disposal of Information Assets; 3.3.12 Payment Systems; 3.3.13 Electronic Banking Services; 3.3.14 Cyber Security Event Management; 3.3.15 Cyber Security Incident Management; 3.3.16 Threat Management; 3.3.17 Vulnerability Management |
| 3.4 Third Party Cyber Security | 3.4.1 Contract and Vendor Management; 3.4.2 Outsourcing; 3.4.3 Cloud Computing |
Leadership and governance
- Board and committee: the board holds ultimate responsibility and allocates budget. It may delegate to a cyber security committee mandated by the board and headed by an independent senior manager from a control function, with the CISO and senior managers of relevant departments as members and internal audit as an observer. The committee meets at least quarterly and approves and monitors programmes, risk processes, KRIs and KPIs.
- Independent function: the cyber security function is separate from IT, with its own reporting line, budget and staff evaluations, reporting to the CEO or managing director or to the general manager of a control function.
- CISO: a full-time senior management appointment, sufficiently qualified, a Saudi national, and subject to a SAMA no-objection.
- Projects: cyber security objectives are part of project objectives, a risk assessment is done at the start, and an independent party performs a cyber security review.
- Awareness and training: programmes for staff, third parties and customers run throughout the year and are evaluated for effectiveness; specialist training goes to cyber security staff, developers and risk assessors.
Risk management and compliance
- Risk process: aligned with enterprise risk management, with formally approved risk appetite and tolerance. Risk assessment is triggered early in projects, before critical changes, when outsourcing and when launching new products. Accepted risks need business owner sign-off, must sit within appetite, are reported to the committee and must not conflict with SAMA regulations.
- Standards: banks comply with PCI DSS, the EMV technical standard and the SWIFT Customer Security Controls Framework.
- Review: customer-facing and internet-facing services get an annual cyber security review and penetration test, with findings tracked to closure.
- Audit: independent, regular audits performed under generally accepted auditing standards and the framework, following the organisation's audit plan.
Operations and technology
- Event management (3.3.14): a designated security operations centre, 24x7 monitoring, a monitoring standard that sets mandatory events per asset by classification, a SIEM for central correlation, protected logs and periodic independent testing of the SOC, for example by red teaming.
- Threat and vulnerability management (3.3.16, 3.3.17): a threat intelligence process that uses internal and external sources and shares relevant intelligence with SAMA and other stakeholders; risk-based scanning of all information assets, with mitigation timelines per vulnerability class and a defined patch deployment method.
- Cryptography (3.3.9): a cryptographic standard listing approved solutions and their restrictions, when they must be applied, and key management across the lifecycle including archiving and recovery.
- Electronic banking (3.3.13): MFA for registration and all e-banking services, including sign-on, beneficiary changes, high-risk transactions and password reset; access revoked after three successive incorrect passwords or PINs; mobile number changes only at a branch or ATM, with SMS alerts to old and new numbers; and SAMA approval before a new e-banking service launches.
Third parties
- Contracts (3.4.1): right to audit, cyber security requirements and SLAs in contracts, a risk assessment during procurement, an incident escalation process, and exit requirements including escrow where applicable.
- Outsourcing (3.4.2): SAMA approval before material outsourcing, following the SAMA outsourcing circular.
- Cloud (3.4.3): SAMA approval before using hybrid or public cloud services or signing the provider contract, and explicit SAMA approval for cloud services located outside Saudi Arabia; private cloud is excluded. See the Financial Cloud Outsourcing Rules Map.
Timeline and current status
| Date | Event |
|---|---|
| 24 May 2017 (28/8/1438 H) | SAMA issues the Cyber Security Framework, number 381000091275, superseding earlier SAMA cyber security circulars |
| 1 January 2022 (28/5/1443 H) | SAMA issues the Cyber Resilience Fundamental Requirements for sandbox entrants and licence applicants |
| 13 November 2026 (date checked) | Both documents shown as In-Force in the Cyber Resilience section of the SAMA Rulebook |
Section 1.8 sets out how the framework changes. SAMA reviews it periodically, including against emerging threats. A Member Organisation that believes an update is needed submits a formal request to SAMA, and remains responsible for compliance with the current text until SAMA approves and publishes a change. Under version control each change retires the previous version and SAMA notifies all Member Organisations, with changes marked.
Enforcement and penalties
The framework works through supervision rather than a penalty table of its own.
- Self-assessment: implementation is subject to periodic self-assessment using a SAMA questionnaire. SAMA reviews and audits the self-assessments to determine each organisation's compliance and maturity level, and uses the framework to compare Member Organisations with each other.
- Exceptions: where a control consideration cannot be tailored or implemented, the organisation should consider compensating controls, internal risk acceptance and a formal waiver request to SAMA under the framework's waiver process (Appendix D).
- Regulatory approvals: material outsourcing, public or hybrid cloud, cloud outside Saudi Arabia, new e-banking services and the CISO appointment all depend on SAMA approval or no-objection, so a weak control position can block business plans directly.
- Sanctions: the CSF text does not set out its own fines. Consequences for non-compliance flow from SAMA's supervisory powers over the licensed entity under the laws that govern each sector, so legal teams should map those powers for their licence type.
Incident reporting to SAMA
Subdomain 3.3.15 Cyber Security Incident Management sets the reporting path.
- Immediately: inform SAMA IT Risk Supervision when a medium or high classified security incident has occurred and been identified (3.3.15, item 5).
- Before any media contact: obtain a no objection from SAMA IT Risk Supervision for any media interaction about the incident (item 6).
- After recovery: submit a formal incident report once operations resume, covering incident title, classification, time of occurrence and detection, affected assets, technical details, root cause analysis, corrective actions, impact and estimated cost (item 7).
The CRFR uses a similar rule for its entities (control 3.2.16): inform SAMA immediately, at the address given in the CRFR, for cyber security, fraud and disruptive incidents classified medium or above. Neither text sets an hour-based deadline, so define "immediately" in your incident procedure and agree the classification criteria in advance.
What it means for AI agents and non-human identities
The 2017 text does not mention AI agents, but subdomain 3.3.5 Identity and Access Management applies to every identity that reaches an information asset. Its principle limits access to what the business requires on a need-to-have and need-to-know basis, and its objective is that only authorised, sufficient privileges go to approved users.
| 3.3.5 control consideration | What it means for service accounts, API keys and agents |
|---|---|
| Joiner, mover and leaver for all user types, with an accountable party initiating changes for external staff and third parties | Every service account, API key and agent identity has a named human owner who requests, changes and retires it; HR events do not cover machines, so ownership must |
| Formal approval of access requests, prompt processing and an audit trail of requests | Machine credentials go through the same request and approval workflow, with the trail kept; no self-provisioned keys in pipelines |
| Periodic review of access rights and profiles | Include NHIs and agent permissions in access reviews; the framework sets no fixed frequency, so set one in policy |
| Centralised and, where possible, automated IAM | Hold machine identities in a central inventory rather than per team spreadsheets |
| MFA for sensitive and critical systems, all remote access and privileged access to critical systems | Machines cannot use MFA, so use strong non-password authentication (certificates, workload identity, short-lived tokens) and record the compensating control and risk acceptance |
| Non-personal privileged accounts: limit and monitor use, keep passwords confidential, change them frequently and at the end of each session | Vault privileged service account credentials, check them out per session and rotate on check-in; prefer ephemeral credentials so there is nothing to rotate |
| Individual accountability for privileged and remote access | Agents acting for a user should carry the user's delegated identity or be traceable to it, not share a single privileged account |
- Event management: include machine and agent authentication events in the 3.3.14 monitoring standard, and baseline their behaviour. See the Service Account Behavioural Baselining Guide.
- Third parties: API keys and OAuth grants issued to vendors and SaaS platforms are third-party access under 3.4; capture them in the contract and exit process so they are revoked at termination.
- Evidence: show the inventory, owners, review records and rotation logs for NHIs when SAMA reviews the self-assessment. See Audit Readiness for AI Agents and NHIs.
Compliance steps
- Confirm scope: record your licence type, which of 3.1.2, 3.2.3, 3.3.12 and 3.3.13 apply, and whether the CRFR also applies during licensing.
- Set up governance first: board mandate, committee charter with quarterly meetings, an independent cyber security function and a CISO appointment with SAMA no-objection. Many other controls need this structure to reach level 3.
- Baseline maturity: score every subdomain against the six levels (0 non-existent, 1 ad hoc, 2 repeatable but informal, 3 structured and formalised, 4 managed and measurable, 5 adaptive) using the SAMA self-assessment questionnaire. Level 3 needs documented and approved policies, standards and procedures plus monitored KPIs; level 4 adds KRIs and trend reporting.
- Close the gaps by risk: prioritise subdomains below level 3 that touch critical assets, starting with 3.3.5, 3.3.14, 3.3.15 and 3.3.17.
- Handle exceptions formally: for anything that cannot be met, document compensating controls, get internal risk acceptance within appetite and request a SAMA waiver.
- Align third parties: update contracts for right to audit, incident escalation and exit; check that every material outsourcing and public or hybrid cloud use has SAMA approval.
- Prove it: keep evidence per control consideration, run the annual review and penetration test for internet-facing services, and schedule independent audits.
- Map overlaps: reuse evidence for the NCA controls and the Personal Data Protection Law. See the Saudi NCA Essential Cybersecurity Controls Guide and the Saudi Arabia PDPL Guide.
Smaller vs larger institutions: a financing company or credit bureau can often reach level 3 with a compact policy set, an outsourced SOC under a 3.4 contract and a single GRC register. A large bank needs per-subdomain control owners, automated evidence collection and KRIs to move towards level 4.
Measuring progress
- Share of subdomains self-assessed at level 3 or above.
- Number of open waivers and risk acceptances, and their age.
- Share of privileged accounts, human and non-personal, under session check-out and rotation.
- Share of medium or high incidents reported to SAMA within the internal "immediately" target.
- Share of material outsourcing and cloud contracts with SAMA approval and right-to-audit clauses on file.
Common failure patterns
- Policy without operation: documents are approved but KPIs are not monitored, so self-assessments claim level 3 that a SAMA review will not support.
- Function not independent: cyber security still reports through the CIO or shares IT's budget, which the governance subdomain rules out.
- Machine accounts outside IAM: service accounts with static passwords that never change, contrary to the non-personal privileged account rules in 3.3.5.
- Cloud before approval: teams adopt a public cloud or SaaS service, often hosted outside the Kingdom, without the SAMA approval 3.4.3 requires.
- Undefined "immediately": no agreed incident classification or reporting trigger, so the first SAMA notification happens days late.
Practitioner checklist
- Record the applicability decision for 3.1.2, 3.2.3, 3.3.12 and 3.3.13 and whether the CRFR applies.
- Confirm the committee charter, quarterly meetings, independent reporting line and CISO no-objection are on file.
- Self-assess every subdomain against the six maturity levels and evidence level 3 or above.
- Bring all service accounts, API keys and agent identities into the IAM inventory with owners and periodic review.
- Vault non-personal privileged credentials with per-session check-out and rotation.
- Write the monitoring standard for 3.3.14, including machine identity events, and test the SOC independently.
- Define incident classification and the "immediately" target for SAMA notification, plus the media no-objection step.
- Check SAMA approvals for material outsourcing, public and hybrid cloud and offshore cloud services.
- Document compensating controls, risk acceptances and waiver requests for every gap.
Standards and references
- SAMA Rulebook: Cyber Resilience (CSF and CRFR status and texts)
- SAMA: Cyber Security Framework, Chapter 1 Introduction
- SAMA: Cyber Security Framework, Framework Structure and Features
- SAMA: Cyber Security Framework, Control Domains and 3.1 Leadership and Governance
- SAMA: Cyber Security Framework, 3.2 Risk Management and Compliance
- SAMA: Cyber Security Framework, 3.3 Operations and Technology
- SAMA: Cyber Security Framework, 3.4 Third Party Cyber Security
Related NHI Mgmt Group resources: Saudi NCA Essential Cybersecurity Controls Guide · Financial Services Cyber Regulation Map · Saudi NCA Cloud Cybersecurity Controls (CCC) · Financial Cloud Outsourcing Rules Map. This guide summarises the SAMA Cyber Security Framework and is not legal advice.