SAMA Cyber Security Framework (CSF v1.0), explained and mapped
The Saudi Central Bank's Cyber Security Framework sets the cyber security requirements for the institutions it regulates, and measures them on a maturity scale. This page sets out its structure, the maturity model, all 32 subdomains, which of them a technical test can evidence, and how the rest are evidenced.
Four domains and 32 subdomains, measured for maturity
Version 1.0, published in May 2017, is the version in force; SAMA has not issued a second edition. Its Cyber Resilience Fundamental Requirements (2022) apply to new and sandbox entities and do not replace the CSF, and banks carry additional requirements from later circulars on top of it.
Six levels, and why level 3 is the line that matters
Each subdomain is assessed on a scale from 0 to 5. SAMA expects its member organisations to reach at least level 3: controls that are defined, approved, implemented and followed consistently, not just practised by the people who know them.
- Level 0 Non-existent
- No documented or practised controls.
- Level 1 Ad hoc
- Controls exist in places, but are informal and depend on individuals.
- Level 2 Repeatable but informal
- Controls are repeated, but not formally defined, approved or applied everywhere.
- Level 3 Structured and formalised
- Controls are defined, approved by management, implemented and followed. The minimum SAMA expects, and where most assessment evidence is asked for: the policy, the procedure, and proof that it runs.
- Level 4 Managed and measurable
- Effectiveness is measured and reviewed, with indicators reported to management.
- Level 5 Adaptive
- Controls are continuously improved in response to measurement, incidents and the changing threat.
What a technical test can evidence, and what needs documents
Like most governance frameworks, the CSF is largely policy, process and oversight. A technical test evidences the cyber security review outright and the technical side of 10 more subdomains. The rest are evidenced with policies, records and approvals, which is also what moves a subdomain to level 3.
| Subdomain | Title | Can a technical test evidence it? |
|---|---|---|
| 3.1 · Cyber Security Leadership and Governance | ||
| 3.1.1 | Cyber Security Governance | Documents and process evidence |
| 3.1.2 | Cyber Security Strategy | Documents and process evidence |
| 3.1.3 | Cyber Security Policy | Documents and process evidence |
| 3.1.4 | Cyber Security Roles and Responsibilities | Documents and process evidence |
| 3.1.5 | Cyber Security in Project Management | Documents and process evidence |
| 3.1.6 | Cyber Security Awareness | Documents and process evidence |
| 3.1.7 | Cyber Security Training | Documents and process evidence |
| 3.2 · Cyber Security Risk Management and Compliance | ||
| 3.2.1 | Cyber Security Risk Management | Documents and process evidence |
| 3.2.2 | Regulatory Compliance | Documents and process evidence |
| 3.2.3 | Compliance with (Inter)national Industry Standards | Documents and process evidence |
| 3.2.4 | Cyber Security Review | Yes: the test is the evidence |
| 3.2.5 | Cyber Security Audits | Documents and process evidence |
| 3.3 · Cyber Security Operations and Technology | ||
| 3.3.1 | Human Resources | Documents and process evidence |
| 3.3.2 | Physical Security | Documents and process evidence |
| 3.3.3 | Asset Management | In part: the technical side |
| 3.3.4 | Cyber Security Architecture | Documents and process evidence |
| 3.3.5 | Identity and Access Management | In part: the technical side |
| 3.3.6 | Application Security | In part: the technical side |
| 3.3.7 | Change Management | Documents and process evidence |
| 3.3.8 | Infrastructure Security | In part: the technical side |
| 3.3.9 | Cryptography | In part: the technical side |
| 3.3.10 | Bring Your Own Device (BYOD) | Documents and process evidence |
| 3.3.11 | Secure Disposal of Information Assets | Documents and process evidence |
| 3.3.12 | Payment Systems | In part: the technical side |
| 3.3.13 | Electronic Banking Services | In part: the technical side |
| 3.3.14 | Cyber Security Event Management | In part: the technical side |
| 3.3.15 | Cyber Security Incident Management | Documents and process evidence |
| 3.3.16 | Threat Management | Documents and process evidence |
| 3.3.17 | Vulnerability Management | In part: the technical side |
| 3.4 · Third Party Cyber Security | ||
| 3.4.1 | Contract and Vendor Management | Documents and process evidence |
| 3.4.2 | Outsourcing | Documents and process evidence |
| 3.4.3 | Cloud Computing | In part: the technical side |
The requirements, the evidence and the maturity, in one place
All 251 control requirements loaded, each assigned to an owner with a due date, maturity tracked per subdomain, evidence collected through connectors, and policies generated in Arabic and English.
A compliance evidence pack for SAMA CSF v1.0 carrying the full control list: what the engagement could test, the result, the findings behind each control and hash-chained evidence your assessor can check.
Outside-in checks mapped to the CSF controls they evidence, continuously: internet-facing assets, cryptography, vulnerabilities and application exposure as an attacker sees them.
Leadership the governance domain asks a named function to own: the strategy, the committee, the roles, the risk register and the reviews, on your working hours.
GRCorb · Threat Exposure Validation Validation · Threat Landscape Monitoring · vCISO · NCA ECC guide
Questions compliance teams ask about SAMA CSF
Who does the SAMA CSF apply to?
Institutions regulated by the Saudi Central Bank, such as banks, insurers and finance companies. Their third parties are drawn in through the third-party domain, which requires the regulated institution to manage its suppliers' cyber security.
Is there a newer version than v1.0?
No. Version 1.0 from May 2017 is in force. The Cyber Resilience Fundamental Requirements published in 2022 apply to new and sandbox entities and sit alongside the CSF rather than replacing it.
What maturity level do we need?
At least level 3, "structured and formalised", on each subdomain. In practice that means a defined and approved policy, a procedure that is followed, and records that prove it runs.
Can a penetration test prove CSF compliance?
No. It evidences the cyber security review subdomain and the technical side of others such as identity and access, application and infrastructure security, cryptography and vulnerability management. Governance, risk management, awareness and third-party management need documents, records and approvals.
Does the CSF cover email security or AI?
Not with a dedicated control. Email authentication and AI findings are mapped to the general controls they touch or reported on their own, rather than forced into a control that does not fit.
How does this relate to NCA ECC?
They are separate obligations that overlap heavily. A bank may be held to both. GRCorb cross-references them so one piece of evidence counts for each where it genuinely applies; our NCA ECC guide lists its 28 subdomains the same way.
Sources
- Saudi Central Bank (SAMA), Cyber Security Framework, in the SAMA Rulebook: rulebook.sama.gov.sa
This page is guidance, not legal advice. Check the current text in the SAMA Rulebook before relying on it for an assessment.