SAK T.E.CTechnology · Evaluation · Compliance Book a demoDemo
Framework guide · Saudi Arabia · Saudi Central Bank

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.

The structure

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.

4main domains
32subdomains
251control requirements, as loaded in GRCorb
3the minimum maturity level SAMA expects
The maturity model

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.
All 32 subdomains

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.

SubdomainTitleCan a technical test evidence it?
3.1 · Cyber Security Leadership and Governance
3.1.1Cyber Security GovernanceDocuments and process evidence
3.1.2Cyber Security StrategyDocuments and process evidence
3.1.3Cyber Security PolicyDocuments and process evidence
3.1.4Cyber Security Roles and ResponsibilitiesDocuments and process evidence
3.1.5Cyber Security in Project ManagementDocuments and process evidence
3.1.6Cyber Security AwarenessDocuments and process evidence
3.1.7Cyber Security TrainingDocuments and process evidence
3.2 · Cyber Security Risk Management and Compliance
3.2.1Cyber Security Risk ManagementDocuments and process evidence
3.2.2Regulatory ComplianceDocuments and process evidence
3.2.3Compliance with (Inter)national Industry StandardsDocuments and process evidence
3.2.4Cyber Security ReviewYes: the test is the evidence
3.2.5Cyber Security AuditsDocuments and process evidence
3.3 · Cyber Security Operations and Technology
3.3.1Human ResourcesDocuments and process evidence
3.3.2Physical SecurityDocuments and process evidence
3.3.3Asset ManagementIn part: the technical side
3.3.4Cyber Security ArchitectureDocuments and process evidence
3.3.5Identity and Access ManagementIn part: the technical side
3.3.6Application SecurityIn part: the technical side
3.3.7Change ManagementDocuments and process evidence
3.3.8Infrastructure SecurityIn part: the technical side
3.3.9CryptographyIn part: the technical side
3.3.10Bring Your Own Device (BYOD)Documents and process evidence
3.3.11Secure Disposal of Information AssetsDocuments and process evidence
3.3.12Payment SystemsIn part: the technical side
3.3.13Electronic Banking ServicesIn part: the technical side
3.3.14Cyber Security Event ManagementIn part: the technical side
3.3.15Cyber Security Incident ManagementDocuments and process evidence
3.3.16Threat ManagementDocuments and process evidence
3.3.17Vulnerability ManagementIn part: the technical side
3.4 · Third Party Cyber Security
3.4.1Contract and Vendor ManagementDocuments and process evidence
3.4.2OutsourcingDocuments and process evidence
3.4.3Cloud ComputingIn part: the technical side
How SAK covers SAMA CSF

The requirements, the evidence and the maturity, in one place

GRCorb

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.

Threat Exposure Validation Validation

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.

Threat Landscape Monitoring

Outside-in checks mapped to the CSF controls they evidence, continuously: internet-facing assets, cryptography, vulnerabilities and application exposure as an attacker sees them.

vCISO service

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

Before you ask

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

This page is guidance, not legal advice. Check the current text in the SAMA Rulebook before relying on it for an assessment.

Chat with us