The SAMA Cyber Security Framework is the baseline cybersecurity requirement set issued by the Saudi Central Bank (SAMA, formerly the Saudi Arabian Monetary Authority) for the financial institutions it supervises. It combines governance, risk, operational and third-party controls and uses a maturity model to measure progress. This guide explains what it covers, who it applies to, and how to build a defensible compliance program around it.
What it is
The SAMA Cyber Security Framework (often written SAMA CSF) was issued by SAMA in 2017 for the institutions under its supervision. It is a regulatory framework issued by the financial regulator and mandated for member organizations, not a voluntary standard and not a certification scheme. The framework includes its own cyber security maturity model, and SAMA also publishes other supporting guidance. Check with SAMA or your supervisory contact for the current version and any updates, since regulators revise such documents and issue clarifications over time.
The framework draws on international practice, including ISO 27001, NIST publications and PCI DSS, and tailors it to the Saudi financial sector. Its stated aims are to create a principle-based approach to cybersecurity, give institutions a common baseline, and raise resilience across the sector.
SAMA issues several regulatory instruments (for example on business continuity, outsourcing and fraud), so this article covers only the Cyber Security Framework.
Who it applies to
The framework applies to financial institutions regulated by SAMA. That generally means banks, insurance and reinsurance companies, finance companies, and other entities under SAMA's supervision, including payment-related and similar firms. Which entities fall in scope, and how the requirements apply to each, is set by SAMA; confirm your status with your supervisor rather than assuming.
It is relevant beyond the regulated entity itself. Institutions are expected to manage cyber risk from third parties, so vendors, cloud providers and outsourced service providers frequently face contractual flow-down of SAMA requirements. Foreign banks with Saudi operations should confirm how the framework applies to branches and subsidiaries.
Many institutions are also subject to the National Cybersecurity Authority (NCA) regime, notably the Essential Cybersecurity Controls (ECC) and related controls. The NCA is the national cybersecurity authority, while SAMA is the sector regulator for finance. Where both apply, treat them as overlapping obligations to reconcile, not as a single requirement.
Key requirements and control areas
The framework is organized into four main domains. Each domain contains sub-domains with control objectives and specific controls.
- Cyber Security Leadership and Governance. Establishing a cybersecurity committee and governance structure, a cybersecurity strategy, policies, defined roles and responsibilities, cybersecurity in project management, and awareness and training.
- Cyber Security Risk Management and Compliance. Operational risk management processes for cyber risk, regulatory compliance tracking, periodic assessments, and independent review of the cybersecurity program.
- Cyber Security Operations and Technology. The technical and operational core: human resources security, physical security, asset management, cybersecurity architecture, identity and access management, application security, change management, infrastructure security, cryptography, bring-your-own-device, secure disposal of information assets, payment systems and electronic banking services, event management, and incident, threat and vulnerability management.
- Third Party Cyber Security. Contractual and outsourcing controls, cloud and other external party arrangements, and oversight of the security posture of suppliers that hold or process institutional data.
The framework uses a principle-and-control structure: each control is stated as a requirement with a defined objective. Institutions are expected to implement the controls proportionate to their size and risk, but the baseline is not optional. Many controls require documented policy, defined ownership and evidence that the control operates, not only that it exists.
Maturity levels
A distinctive feature is the maturity model. Maturity is generally assessed on a scale from level 0 (non-existent) up to level 5 (adaptive), with intermediate levels covering ad hoc, repeatable but informal, structured and formalized, managed and measurable. Levels broadly progress from having an ad hoc process, to documented and approved processes, to processes that are implemented and measured, and finally to continuously improved ones. SAMA sets expectations for the level an institution should reach, and institutions assess themselves against it. Confirm the target level and the assessment method directly with SAMA, as expectations can differ by institution and over time.
Assessment, audit and enforcement
SAMA supervises compliance as a regulator. There is no public certificate for the framework in the way ISO 27001 has one. Instead, institutions typically:
- Perform a self-assessment against the framework and its maturity model, and report results to SAMA as required.
- Undergo independent assessment, often by a qualified external firm, as well as internal audit review.
- Remediate gaps through tracked action plans that SAMA may review in supervisory engagements.
Supervisory consequences are determined by SAMA under its legal powers over the entities it regulates. Specific penalties and enforcement procedures are set by Saudi law and SAMA's own processes, and this article does not state specific amounts. In practice, expect supervisory findings, required remediation plans and, for serious failures, formal regulatory action.
A practical path to meeting it
- Confirm scope and obligations. Establish with your SAMA supervisor which version of the framework applies, the expected maturity targets and any reporting deadlines. List the other regimes that apply, such as NCA controls, PCI DSS and data protection rules.
- Set governance. Assign executive ownership, form the cybersecurity committee or equivalent, and approve a cybersecurity strategy and policy set aligned to the framework's domains.
- Build an asset and data inventory. Controls in operations, access, cryptography and third-party management all depend on knowing what systems and data you hold, including cloud and outsourced services.
- Run a baseline gap assessment. Score every control against the maturity scale, record the evidence behind each score, and note where you only have a policy but no proof of operation.
- Prioritize remediation by risk. Build a roadmap with owners, dates and budget. Tackle foundational gaps first: identity, logging and monitoring, vulnerability management and incident response.
- Bring third parties into scope. Inventory suppliers, tier them by risk, update contracts to carry security and audit-right clauses, and collect assurance evidence on a schedule.
- Test and exercise. Run penetration tests, incident response exercises and recovery tests, and record outcomes and fixes.
- Collect evidence continuously. Maintain evidence throughout the year instead of assembling it before an assessment, and track control performance so you can show maturity at the measured level, not only design.
- Report and review. Submit required assessments, brief the committee and board, and use independent review findings to feed the next improvement cycle.
How it maps to other frameworks
The overlaps below are real but partial. Meeting one framework does not mean you satisfy another.
- ISO/IEC 27001. Significant overlap in governance, risk management, asset management, access control, cryptography, operations security, supplier relationships and incident management. ISO 27001 is a certifiable management system standard; the SAMA framework is a regulatory requirement with its own maturity assessment and Saudi-specific expectations.
- NIST Cybersecurity Framework. The framework's governance, risk, protection, detection and response themes align conceptually with the NIST CSF functions. NIST CSF is voluntary guidance and does not prescribe SAMA's control set.
- NCA Essential Cybersecurity Controls. Both address governance, defense, resilience and third-party security, so many controls overlap. They come from different authorities, so check each requirement and its evidence needs separately.
- PCI DSS. Overlap on access control, encryption, logging, vulnerability management and testing for institutions that handle cardholder data. PCI DSS is a contractual industry standard.
- SOC 2. Some overlap in security-related criteria, mainly useful as supporting assurance from service providers. It is an attestation, not a replacement for SAMA obligations.
FAQs
Is the SAMA Cyber Security Framework mandatory?
Yes, for the financial institutions SAMA regulates. It is a regulatory requirement issued by the Saudi Central Bank, not a voluntary standard. Confirm applicability to your entity type with SAMA.
Is there a SAMA certification?
No public certification comparable to ISO 27001 exists for the framework. Compliance is shown through self-assessment, independent assessment and supervisory review.
How does it differ from the NCA Essential Cybersecurity Controls?
The NCA is the national cybersecurity authority and issues controls across sectors. SAMA is the financial sector regulator and issues requirements tailored to the institutions it supervises. Financial institutions may need to meet both, and many controls overlap.
Does it apply to vendors and cloud providers?
Not directly in most cases, but institutions must manage third-party cyber risk, so suppliers commonly receive contractual requirements that mirror the framework. Cloud use also raises additional regulatory considerations in Saudi Arabia that you should verify separately.
What maturity level do we need to reach?
That depends on SAMA's expectations for your institution and the assessment guidance it has issued. Ask your supervisor for the current target and method rather than relying on a general figure.
How often is it assessed?
Institutions are expected to assess regularly and report as SAMA requires. The specific cadence is set by SAMA, so confirm it for your entity.
How Aristiun helps
Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. For SAMA Cyber Security Framework work, it helps you keep evidence and control status current across the domains, so maturity assessments rest on proof rather than periodic scrambles. You can explore compliance frameworks on the site.
- Automated evidence collection from connected systems such as AWS, Azure, GCP and GitHub, without manual screenshots or spreadsheets.
- Cross-framework mapping, so one evidence base can address SAMA alongside overlapping requirements such as ISO 27001 or NCA controls.
- Real-time control monitoring with alerts when controls drift out of compliance, plus AI-powered gap analysis to find missing evidence early.
- Automated threat modeling from code, IaC and architecture diagrams, and vendor risk mapping that links supplier controls to your requirements.