Convoys · Compliance and Assurance · CBI
Iraq: the Central Bank of Iraq's Cyber Resilience Controls.
Iraq. Regulator: Central Bank of Iraq (CBI).
The convoy's regime for the Central Bank of Iraq's Cyber Resilience Controls and the technology standards of its Banking Reform Standards. It holds every requirement under the CBI's own numbering, and shows beside each whether it comes from the Controls or the Standards.
Neither Mamluk LLC-FZ nor its products are affiliated with or endorsed by the Central Bank of Iraq.
In brief
Who sets these requirements, and how the convoy evidences them.
Central Bank of Iraq (CBI). 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 Cyber Resilience Controls and Banking Reform Standards (CBI regime). 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.
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 payment providers in Iraq.
The Central Bank of Iraq issued the Cyber Resilience Controls for the Financial and Banking Sector in June 2024, for every bank and payment service provider it regulates, in force from their issue. Its Banking Reform Standards 2025 apply to private banks, commercial and Islamic. Standard B7 requires a private bank to comply with the Cyber Resilience Controls, so a private bank is assessed on both. The phase of the CBI's assessment that covers standards B2, B3, B7 and B9 has no published date.
Each private bank submits an annual assurance report from a firm the CBI approves. The convoy's evidence supports that review and does not replace it. The CBI has not recognised or accepted the convoy's reports.
The rules require a bank's data centres, and at least one disaster recovery site at least 75 kilometres from them, to be inside Iraq. The convoy runs on the bank's own Kubernetes cluster, in Iraq. Its evidence stays on the cluster's volume unless delivery by S3 or by email is configured; an S3 endpoint, mailbox or mail relay outside Iraq places the evidence outside Iraq, so set the S3 endpoint to a store in Iraq.
Structure
The Controls and four Standards, 524 requirements.
The regime holds the 434 requirements of the Cyber Resilience Controls, marked "Controls (all banks and
payment providers)", and the 90 items of standards B2 (core banking system), B3 (online banking), B7
(infrastructure and data) and B9 (business and operational resilience), marked "Standards (private
banks)". The report shows beside each requirement which of the two it is, and the assessment's OSCAL
document carries the same distinction: always for the Controls and risk for
the Standards.
- GV Governance 36
- IM IT and security infrastructure management 1
- RM Risk management 28
- ID Identify 34
- PR Protect 261
- DE Detect 17
- RS Respond 40
- AW Awareness 13
- TS Testing 4
- B2 Standard B2, core banking system 24
- B3 Standard B3, online banking 16
- B7 Standard B7, infrastructure and data 24
- B9 Standard B9, business and operational resilience 26
The Controls are published in Arabic only, and the regime is built from that text, the first edition of June 2024. The Standards are published in Arabic with an English reference translation, in which the Arabic prevails; the regime is built from the English reference translations of the Standards Booklet and the Detailed Assessment Guidelines 2025. The summaries in the report are Mamluk's own English paraphrase, not an official translation. The CBI's numbering restarts in each function and repeats some numbers, so a Controls requirement carries a function prefix and the CBI's number (for example PR-9.1a), and a Standards requirement the standard and its item (for example B7 B.6). The prefixes and the letters added to the CBI's numbers are Mamluk's.
Evidence
What the cluster shows, and what remains yours.
- Enforced, checked and platform. Forty-five of the 524 requirements: two enforced by an admission policy, thirty-seven checked in the cluster and six provided by the platform. Among them are approved software, the separation of test from production, server access and administration, network zones and segregation, encryption in transit, user identities and audit trails, patching, backups and their encryption, the protection of logs, and vulnerability assessment.
- Your evidence. The other 479, among them governance, risk management, data classification, the data centre, ATMs and points of sale, email and internet use, third parties, incident management, business continuity and the Standards' notices and assurance reviews, are your bank's to evidence, and the report lists each as such. Multi-factor authentication is among them: the cluster shows that sign-in is delegated to your identity provider, not that the provider requires a second factor. So are the data centres and the disaster recovery site in Iraq: a cluster cannot show where its hardware stands.
- Where the cluster shows part of a requirement. Where a requirement asks for more than the cluster can show, the report states what the checks evidence and what remains the bank's, beside the verdict. The Controls name no algorithm, so no verdict states that an algorithm is approved.
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.
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.
The CBI maps none of these requirements to NIST SP 800-53. The CBI is the source and owner of the texts: the report uses their numbering and their structure, and every summary is Mamluk's own paraphrase in English.
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: “The CBI publishes no mapping of these requirements to NIST SP 800-53. The mapping in this report is Mamluk's own.” 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 CBI
To discuss the regimes your organisation must meet, or the convoy's licensing, contact Mamluk.
Contact Mamluk