Convoys · Compliance and Assurance · SAMA CSF
SAMA Cyber Security Framework.
Saudi Arabia. Regulator: Saudi Central Bank (SAMA).
The convoy's regime for banks and financial institutions in Saudi Arabia. It maps each control consideration of the Saudi Central Bank's framework to the evidence a Kubernetes cluster can show, beside NCA ECC in the same installation, so a bank that answers to both regulators has each regime reported from the same cluster.
Neither Mamluk LLC-FZ nor its products are affiliated with or endorsed by the Saudi Central Bank.
In brief
Who sets these requirements, and how the convoy evidences them.
Saudi Central Bank (SAMA). SAMA regulates banks, insurers, financing companies and other financial institutions in Saudi Arabia. It keeps the abbreviation of its former name, the Saudi Arabian Monetary Authority.
SAMA Cyber Security Framework (SAMA CSF). The Cyber Security Framework sets the cybersecurity requirements for the organisations SAMA regulates, as control considerations in four domains. It is distinct from NIST's Cybersecurity Framework, which is also abbreviated CSF.
National Cybersecurity Authority (NCA). NCA is Saudi Arabia's national authority for cybersecurity. It sets the cybersecurity requirements for government entities and the operators of critical national infrastructure, and assesses compliance with them.
Essential Cybersecurity Controls (ECC). The ECC are NCA's minimum cybersecurity requirements, binding on government entities and critical national infrastructure in Saudi Arabia. The current edition, ECC-2:2024, holds 176 requirements in four domains.
The convoy classes each requirement by how its evidence is obtained: enforced by an admission policy, checked in the cluster, provided by the platform, or the organisation's own evidence. An admission policy is a rule Kubernetes applies to each object as it is created or changed, before the object is stored. It can warn about the object and record the result, or refuse the object. How a regulator's requirement becomes evidence follows one requirement from the regulator's text to the result in the report.
Who it applies to
Banks and financial institutions regulated by SAMA.
The Cyber Security Framework is issued by the Saudi Central Bank and applies to the organisations it regulates in Saudi Arabia: banks, insurance and reinsurance companies, financing companies, credit bureaus and financial market infrastructure. SAMA publishes it openly in its Rulebook.
A bank in Saudi Arabia that also falls under NCA's Essential Cybersecurity Controls answers to two regulators. With both regimes selected, the convoy collects evidence for each regime every day from the same cluster and the same scanner and policy reports, and reports each regime in its own numbering.
Structure
Four domains, 32 subdomains.
Each subdomain of the framework sets a principle and an objective, and then a list of control considerations, numbered in up to four levels. The convoy maps each control consideration at the level SAMA numbers it last, so a subdomain that mixes what a cluster can show with what it cannot does not collapse into a single partial result.
- 3.1 Leadership and governance 7
- 3.2 Risk management and compliance 5
- 3.3 Operations and technology 17
- 3.4 Third parties 3
Evidence
Evidence for each consideration, and no maturity score.
- Enforced, checked and platform. Twenty-nine of the 409 considerations: five enforced by an admission policy, fifteen checked in the cluster and nine provided by the platform. They sit in nine of the 32 subdomains: asset management, identity and access management (including multi-factor authentication for remote and privileged access), application security, change management, infrastructure security and network segmentation, cryptography, electronic banking services, security event management, and vulnerability management. Within them, the technical considerations are classed as for every regime, and the report asks for the institution's evidence of the rest.
- The institution's evidence. The other 380, among them every consideration on leadership and governance, risk management and compliance, people, physical security and third parties, are the institution's to evidence, and the report lists each as such.
- Cloud, with its scope. SAMA's requirements for cloud computing apply to hybrid and public cloud, and exclude private cloud. The report lists them with the institution's evidence, each with a note that it does not apply to a cluster on the institution's own premises, and never leaves them out.
- No invented thresholds. Where the framework sets no figure, such as a retention period for event logs, the convoy adds none.
Sample report
A sample, written by the convoy on a test cluster with sample workloads, for the organisation "Example Bank". Its image versions and cluster name are placeholders, and its run date and regime version are those of the sample, not of a release.
SAMA assesses each subdomain on a maturity scale. The convoy reports the evidence for each consideration and does not score maturity: the maturity level is the institution's to determine, and the evidence is not a level.
The mapping
Mamluk's mapping, keyed to NIST.
Each requirement is mapped to the controls of NIST Special Publication 800-53, Revision 5 (SP 800-53), published by the National Institute of Standards and Technology (NIST), and each NIST control to the checks that evidence it in the cluster. NIST is the United States government's standards agency. Its security publications are free to use, and regulators and auditors outside the United States also use them as a common reference. SP 800-53 is a control catalogue: a numbered list of safeguards, each stating one thing an organisation should do, such as AC-6, least privilege, or AU-11, keeping audit records for a set period. Its controls are grouped in 20 families, and because the catalogue is detailed and open, it serves as a common language between regulations that are each written in their own terms.
The checks and their NIST mapping are shared by every regime. For each regime selected, the convoy collects evidence every day from the same cluster and the same scanner and policy reports, and reports it in its regulator's own numbering.
SAMA states that its framework draws on NIST, ISO, the Information Security Forum, Basel and PCI DSS, but it publishes no mapping of its control considerations to any of them.
The regulator publishes no official crosswalk to NIST, so the mapping is Mamluk's own. Before the regime was released, it was checked against the regulator's text a second time, statement by statement, by a reviewer other than its author.
The report states whose mapping it uses, in these words: “SAMA publishes no mapping of the framework's considerations to NIST SP 800-53. The mapping in this report is Mamluk's own. SAMA assesses each sub-domain on a maturity scale. This report gives no maturity level: it records what the cluster shows for each consideration, and the maturity level remains the Member Organization's own assessment.” It records the technical evidence the cluster provides; it does not make an organisation compliant, and compliance is determined by your assessor.
Regimes
One convoy, every regime.
Every regime runs in the same installation of the convoy. An organisation that answers to two regulators selects both, and each is licensed separately.
Glossary
The organisations, standards and tools the convoy's pages name.
- NIST National Institute of Standards and Technology
- NIST is the United States government's standards agency. Its security publications are free to use, and regulators and auditors outside the United States also use them as a common reference.
- SP 800-53 NIST Special Publication 800-53, Revision 5
- SP 800-53 is a control catalogue: a numbered list of safeguards, each stating one thing an organisation should do, such as AC-6, least privilege, or AU-11, keeping audit records for a set period. Its controls are grouped in 20 families, and because the catalogue is detailed and open, it serves as a common language between regulations that are each written in their own terms.
- NCA National Cybersecurity Authority
- NCA is Saudi Arabia's national authority for cybersecurity. It sets the cybersecurity requirements for government entities and the operators of critical national infrastructure, and assesses compliance with them.
- ECC Essential Cybersecurity Controls
- The ECC are NCA's minimum cybersecurity requirements, binding on government entities and critical national infrastructure in Saudi Arabia. The current edition, ECC-2:2024, holds 176 requirements in four domains.
- SAMA Saudi Central Bank
- SAMA regulates banks, insurers, financing companies and other financial institutions in Saudi Arabia. It keeps the abbreviation of its former name, the Saudi Arabian Monetary Authority.
- SAMA CSF SAMA Cyber Security Framework
- The Cyber Security Framework sets the cybersecurity requirements for the organisations SAMA regulates, as control considerations in four domains. It is distinct from NIST's Cybersecurity Framework, which is also abbreviated CSF.
- QCB Qatar Central Bank
- QCB is Qatar's central bank and the regulator of its banks. Its circular on technology risks, issued in January 2018, sets the technology and cybersecurity requirements for the banks it regulates, in 516 numbered statements.
- NCSA National Cyber Security Agency
- The National Cyber Security Agency is Qatar's national authority for cybersecurity. Its national standards include the National Information Assurance Standard, version 2.1, issued by the National Cyber Security Agency.
- Qatar NIA National Information Assurance Standard
- The National Information Assurance Standard, version 2.1, issued by the National Cyber Security Agency in May 2023, applies to all organisations, which it defines as businesses operating within the State of Qatar, and to their information assets. It holds 356 control statements in 26 domains, and marks each as a baseline or an additional control.
- MAS Monetary Authority of Singapore
- The Monetary Authority of Singapore is Singapore's central bank and the regulator of its financial sector. It issues binding notices to banks, insurers and capital markets intermediaries, and guidelines that set out the good practice it expects them to adopt.
- MAS TRM MAS Technology Risk Management
- MAS's Notices FSM-N05, on technology risk management, and FSM-N06, on cyber hygiene, in force from 10 May 2024, and its Technology Risk Management Guidelines of January 2021. The notices are binding; the Guidelines are guidance, adopted in proportion to an institution's risks. The convoy holds them in one regime of 259 requirements and marks each as binding or guidance.
- CBI Central Bank of Iraq
- The Central Bank of Iraq licenses and regulates Iraq's banks and payment service providers. It issues the Cyber Resilience Controls for the financial and banking sector, and the Banking Reform Standards assessed for private banks.
- CBI regime CBI Cyber Resilience Controls and Banking Reform Standards
- The CBI's Cyber Resilience Controls (June 2024), published in Arabic, which apply to every bank and payment provider, and standards B2, B3, B7 and B9 of its Banking Reform Standards 2025, which apply to private banks. The convoy holds them in one regime of 524 requirements and marks each as Controls or Standards.
- CBUAE Central Bank of the UAE
- The CBUAE licenses and regulates banks and other financial institutions in the United Arab Emirates. Its Operational Risk Management Regulation sets their requirements for information and communications technology and cybersecurity, and requires them to comply with the cybersecurity regulations of the other UAE authorities.
- UAE CSC UAE Cyber Security Council
- The Cyber Security Council is the federal authority for cybersecurity in the United Arab Emirates, and issues the UAE Information Assurance Standard.
- UAE IA UAE Information Assurance Standard
- The Information Assurance Standard is the UAE's federal standard of security controls, binding on federal government entities and on critical information infrastructure, banks among them. Version 2.1 holds 134 controls in fifteen families, and maps each control to NIST SP 800-53 itself.
- GCC Gulf Cooperation Council
- The GCC's six member states are Saudi Arabia, the United Arab Emirates, Qatar, Kuwait, Bahrain and Oman.
- namespace
- A namespace is a named partition of a Kubernetes cluster, which usually holds one application's or one team's workloads. Permissions and policies are commonly set per namespace.
- admission policy
- An admission policy is a rule Kubernetes applies to each object as it is created or changed, before the object is stored. It can warn about the object and record the result, or refuse the object.
- Kyverno
- Kyverno is an open-source policy engine for Kubernetes. The convoy uses it for what Kubernetes cannot do by itself, such as verifying an image's signature, and reads the results of its own policies from Kyverno's policy reports.
- trivy-operator
- trivy-operator is an open-source security scanner that runs inside the cluster. It scans every workload's images for known vulnerabilities, and audits each workload's configuration and the permissions granted in the cluster.
- NetworkPolicy
- A NetworkPolicy is the Kubernetes object that states which network traffic may reach a group of workloads. A workload that no NetworkPolicy selects accepts traffic from anywhere in the cluster.
- Pod Security Kubernetes Pod Security Standards
- The Pod Security Standards are three built-in levels, privileged, baseline and restricted, of what a workload may do to the server it runs on, such as running as root or reading the server's own files. Kubernetes enforces the level set for each namespace.
- OSCAL Open Security Controls Assessment Language
- OSCAL is NIST's machine-readable format for control catalogues and assessment results. Governance, risk and compliance tools import results in it, so findings need not be typed in again.
- NSA and CISA National Security Agency and Cybersecurity and Infrastructure Security Agency
- The two United States agencies publish joint guidance on hardening Kubernetes, which the convoy's checks also follow.
Price and availability
Each regime is licensed at USD 24,000 per organisation, per year, with the Tersane core licence; there is no base fee. The convoy needs a version of Kubernetes which BKE provides; the prerequisites give the requirement. See the Compliance and Assurance Convoy for how it works, and its documentation for installation. Activating a regime describes how a regime is added to the licence and to a running installation. Its reports can be read in your own cluster, by role, in the Compliance App.
Discuss SAMA CSF
To discuss the regimes your organisation must meet, or the convoy's licensing, contact Mamluk.
Contact Mamluk