Central Bank of Iraq Cyber Resilience Controls for the Financial and Banking Sector: a practical guide
The Central Bank of Iraq has issued a document titled «ضوابط الصمود السيبراني للقطاع المالي والمصرفي في العراق» (Cyber Resilience Controls for the Financial and Banking Sector in Iraq). It tells financial and banking institutions what they need in order to anticipate cyberattacks, withstand them, contain them and recover quickly [1][2]. This guide explains who the controls are for, how they are organised from Governance to Testing, what they say about how often to audit and test, and then gives a practical checklist tied to the document’s own control numbers.
What are the Cyber Resilience Controls, and who issued them?
The controls are a 48-page document issued by the Central Bank of Iraq’s Information Technology and Payments Department (دائرة تقنية المعلومات والمدفوعات), Policies, Regulation and Studies Section; its cover reads "first edition" [2]. The CBI published it as a news item on its website linking to the document [1], and also lists it among the instructions and controls on its Information Technology and Payments page [3].
The introduction says the document’s purpose is to guide institutions and entities in the financial and banking sector in strengthening their cyber resilience, and to detail the measures they must take to reduce the risks that cyber threats and attacks pose to financial and banking stability [2]. It defines cyber resilience as an institution’s ability to keep performing its functions by, first, anticipating and adapting to risks, threats and attacks and, second, withstanding, identifying, detecting, containing, responding to and recovering quickly from cyber events [2].
Who do the controls apply to?
The document addresses "institutions and entities in the financial and banking sector" in general terms and does not list the licence types it covers [2]. Its glossary defines non-bank financial institutions (NBFI) [2]. It states that it is a reference for the board and senior management, given their role in ensuring cyber resilience, and for all staff responsible for designing, monitoring and implementing the cyber resilience framework [2].
The controls also reach beyond the institution itself. They make the level of cyber resilience part of contracts and service-level agreements with connected entities, such as other financial institutions, vendors and service providers, and make those agreements subject to periodic audit and assessment (Risk Management 2.2) [2]. Contracts must bind third parties to the institution’s cybersecurity requirements (Protect 13.1.4) [2].
If you are a bank, the controls address you directly. If you are a payment company or another non-bank licensee, confirm how they apply in light of your licence and the CBI instructions for your category. We note only that the CBI lists the controls on its Information Technology and Payments page alongside instructions addressed to e-payment service providers [3].
Are they mandatory?
The document describes itself as guidance, but words most of its controls as obligations ("must", «يجب») [2]. It also sets a clear route for non-compliance: the institution submits a compliance plan to the Central Bank of Iraq requesting an exception, and the exception must be for a defined period (Governance, IT Policy, Standard and Procedure, item (e)) [2]. In other words, a gap is not left silent; it goes to the CBI with a plan to close it.
How the document is organised
The document opens with a glossary, an introduction and implementation principles, followed by chapters with Arabic titles and English labels in brackets [2]:
- Governance, which contains two numbered sections: IT and Security Infrastructure Management (1) and Risk Management (2)
- Identify
- Protect
- Detect
- Respond
- Awareness
- Testing
It closes with a list of references [2].
Four principles
Before the chapters, the document sets four principles for effective implementation [2]: stakeholder considerations, meaning cooperation with participants, service providers and other connected parties; sustaining and enhancing cyber resilience inside the institution and with the institutions connected to it; ongoing efforts to improve it; and a risk-based approach, meaning measures are prioritised according to the level of risk each institution faces.
How the controls relate to the NIST Cybersecurity Framework
The document states that its guidelines are based in general on the NIST Cybersecurity Framework, and that its activities can be grouped into categories such as Identify, Protect, Detect, Respond and Recover [2]. Its references list three sources: ISO/IEC 27001, ISO/IEC 27005 and the NIST Cybersecurity Framework [2].
The document does not name a version of the NIST framework [2]. The current version, CSF 2.0, has six Functions: Govern, Identify, Protect, Detect, Respond and Recover [6][7]. The Iraqi document handles governance in its own opening chapter and has no separate Recover chapter; business continuity, disaster recovery and backup sit inside the Respond chapter [2]. If your programme is built on NIST CSF, map it to the CBI control numbers directly rather than assuming the two line up one to one.
How to read the control numbers
The document does not use short control codes. It uses the chapter name and then the item number, with sub-levels and sometimes lettered items (a, b, c) [2]. "Detect 2.1.4", for example, is the fourth item under Internal Audits, within Audits in the Detect chapter [2]. This guide refers to controls the same way.
What each section requires
Governance
The chapter lists the stakeholders in IT governance: the board of directors, the CEO, the IT Steering Committee, the Cybersecurity Committee, the CIO, the CTO, the CISO, the Risk Management Committee, the Chief Risk Officer and business executives [2]. The board’s responsibilities include approving IT strategy and policy documents and confirming the status of compliance with the cybersecurity policy [2].
The Governance chapter sets up two committees here (Risk Management adds a third, in 2.4.1). The IT Steering Committee has representatives from IT, risk management, human resources, internal audit and legal, among others. The Cybersecurity Committee has representatives from IT, information and cybersecurity, risk management and the internal complaints committee, among others [2]. Every institution must have a "cybersecurity policy" approved by the board and updated regularly, and must employ cybersecurity specialists in its information security department [2]. The Documentation item adds practical requirements: an up-to-date organisation chart for the IT department, a job description with a named backup for everyone in it, segregation of duties, detailed design documents for critical systems, and up-to-date operating procedures [2].
IT and Security Infrastructure Management
This section requires a mechanism to measure the performance of cybersecurity governance and technical controls, and lists 96 key performance indicators that the institution measures "at least" [2]. They cover governance committee meetings, awareness and training, risk assessments, incidents and resolution times, vulnerability-assessment and penetration-test findings and their remediation, backups, third parties and more [2]. In practice, this list can serve as the basis of the scorecard reported to the board.
Risk Management
The document requires a cyber resilience framework approved by the board and senior management, reviewed and updated periodically [2]. It sets out six sub-sections [2]:
- Business and Supporting Functions (2.1): identify them and classify them by sensitivity and criticality, to set priorities for protection, response and recovery.
- Risk from Interconnections (2.2): manage the risk coming from connected entities.
- Supplier and Third-Party Security Management (2.3): assess their risk and apply controls to detect and prevent breaches linked to them.
- IT Risk Governance (2.4): an IT risk management committee, a risk appetite, and a risk tolerance set after approval by the board or the risk management committee.
- IT Risk Assessment (2.5): a business impact analysis (BIA), risk scenarios, and a periodic assessment by the information security department.
- IT Risk Response (2.6): one of four responses, namely avoid, reduce or mitigate, share or transfer, and accept, with a set of key risk indicators (KRIs).
Identify
The Identify chapter has four sections [2]. Assets Management: an IT asset inventory showing the owner, custodian, location, licence and other details, reviewed periodically, with a disposal policy, an approved software list and a strict ban on unlicensed software. Software Assets: a separate test environment, and user acceptance testing (UAT) signed off by business units before go-live. Capacity Management: monitoring performance, capacity and utilisation. Data Classification.
Data Classification sets four levels: public, restricted, confidential and top secret, and sets requirements for these levels in areas including storage, encryption, remote access, electronic transfer, destruction, meetings and disclosure [2]. One of its most important items: if classified information is disclosed or suspected to have leaked, the Central Bank of Iraq is notified directly by official letter or email describing the incident, and top-secret information requires an urgent, confidential notification together with a letter to the CBI [2].
Protect
Protect is the longest chapter, with 14 sections: endpoint controls, data center controls, network security management, ATM/POS transactions, malicious code protection, internet access management, email management, identity and access control of information systems, patch management, IT service delivery management including change management, mobile financial services, database security, third-party security and application security [2].
Several items in this chapter set explicit values that are easy to check [2]:
- Passwords (8.2.3 to 8.2.7): at least eight characters; a mix of at least three of upper case, lower case, special characters and numbers; a maximum validity of 90 days; a maximum of three consecutive failed login attempts; and no reuse of a password until at least three others have been used.
- Privileged accounts (8.4.2): strong authentication, strong remote-access controls, a limited number of privileged users, privilege granted on a need-to-access basis, timely review of privileged activity, and no sharing of privileged accounts.
- Security patches (9.1): identify, classify and prioritise them, set a timeframe for each category, and test them before production.
- Networks (3.1): baseline security standards for systems and devices, security zones in the network design, firewalls and intrusion detection and prevention systems, secure login such as SSH with unencrypted options such as Telnet disabled, default passwords changed, and unused ports closed.
- ATMs and POS (4): anti-skimming solutions, tamper-resistant keypads, 24-hour video monitoring with footage kept for at least one year, and merchant training.
- Mobile financial services (11.3 and 11.5): limits on transaction value and frequency, fraud and anti-money-laundering checks, and periodic risk analysis and security assessment.
- Databases (12.1.3, 12.1.5 and 12.6.2): direct access only for database administrators, no migration of critical-system databases from production to any other environment, and a review of database security requirements at least once a year.
- Third parties (13.1 and 13.2): non-disclosure and secure deletion of the institution’s information at the end of the service, multi-factor authentication for their access to critical systems, and an annual review of the cybersecurity risk management policy.
- Web applications (14.1 and 14.2): at least a three-tier architecture for important applications, secure communication protocols only, a web application firewall (WAF) for external applications, multi-factor authentication for every web application that staff or customers reach over the internet, a recommendation to consider the OWASP Top 10, and developers barred from changing production source code or production data.
Detect
Detect starts with Security Monitoring (Detect 1) [2]: intrusion detection and prevention systems; regular review of system, application and network-device logs, which must be protected and kept for a defined period; and a capability for continuous real-time or near-real-time monitoring. The document mentions establishing a security operations centre (SOC) as one of the practices that achieve this.
Then come Audits (Detect 2), where the document uses the phrase «إطار عمل المرونة السيبرانية» (cyber resilience framework): its compliance, adequacy and efficiency must be assessed regularly through testing, independent compliance programmes and audits by qualified parties [2]. Four items follow: Internal Audits (2.1), Independent Audit (2.2), Regulatory Compliance (2.3) and Compliance with International Industry Standards (2.4). The last names PCI DSS, EMV and SWIFT CSP among the CBI regulations and instructions that institutions must comply with [2].
Respond
The document requires an incident management framework that sets roles, severity criteria and escalation procedures, periodic testing of the escalation and response plan, and an IT emergency response team made up of the institution’s own staff (Respond 1.1 to 1.5) [2]. It requires the institution to inform the Central Bank of Iraq as soon as possible if any disaster occurs, and to keep customers informed of any major incident (1.6 and 1.7) [2]. After an incident, a root-cause and impact analysis report covers three areas: root causes; impact, including scope, size and any breach of regulatory requirements; and corrective and preventive measures (1.9) [2]. For what we offer here, see Incident response & retainers.
The chapter also covers business continuity and disaster recovery (Respond 2) [2]: an approved business continuity plan supported by a business impact analysis; a disaster recovery plan built on scenario analysis; a disaster recovery site geographically separate from the main site; defined recovery time (RTO) and recovery point (RPO) objectives; and testing at least once a year. Then Data Backup and Restore Management (Respond 3) [2]: a written policy and a strategy for each application, backup frequency set by information classification, encryption of sensitive backups before they leave the site, and periodic testing of restore capability.
Awareness
Awareness has three sections [2]. Awareness Program: a plan with activities, resources, timelines and objectives, delivered through several channels including SMS, ATM screens, social media and websites, with a feedback strategy. Security Awareness and Training: appropriate training for all relevant staff, a security-awareness training or workshop for all employees, and training for the information systems audit team. Customer Education: here the document repeats the common saying that customer awareness is the best defence against fraud.
Testing
This chapter has a single section: Vulnerability Assessment and Penetration Testing [2]. The institution runs regular vulnerability assessments that combine automated tools and manual techniques, covering common flaws such as SQL injection and cross-site scripting in application-based systems, and then validates that remediation is complete (Testing 1.1 to 1.3). It runs penetration tests that simulate real attacks on network infrastructure and internet-facing systems "periodically or as needed" (Testing 1.4). The Protect chapter adds that web applications are scanned for vulnerabilities before they go to production and undergo periodic independent penetration testing (Protect 14.4.9 and 14.4.11) [2].
What the document says about frequency and assessment
The document sets a number for some activities and leaves others to words such as "periodically" and "regularly" [2]:
| Activity | What the document says | Control |
|---|---|---|
| Internal information systems audit | At least once a year, under an annual audit plan that includes branches; report kept for regulators | Detect 2.1.3, 2.1.4 |
| Independent information security audit | Comprehensive, independent and regular; no interval set | Detect 2.2 |
| Regulatory compliance process | Periodically, or when new regulatory requirements take effect | Detect 2.3.1 |
| Testing and review of the BCP and DRP | At least once a year | Respond 2.1.5 (d), 2.2.11 |
| Testing of the incident escalation and response plan | Periodically | Respond 1.4 |
| Testing of backup restoration | Periodically | Respond 3.10 |
| Vulnerability assessment | Regularly | Testing 1.1 |
| Penetration testing of network and internet-facing systems | Periodically or as needed | Testing 1.4 |
| Independent penetration testing of web applications | Periodically | Protect 14.4.11 |
| Review of database security requirements | At least once a year, or when legal and regulatory requirements change | Protect 12.6.2 |
| Review of the cybersecurity risk management policy | Annually | Protect 13.1.8 |
| Review and update of the cyber resilience framework | Periodically | Risk Management (2) |
| Password validity | 90 days at most | Protect 8.2.5 |
| Retention of ATM video footage | At least one year | Protect 4.6 |
Among the KPIs the document asks institutions to measure is "completion of the annual self-assessment" (IT and Security Infrastructure Management, KPI 28) [2].
What the document does not set as a number includes the interval for independent audits, the interval for vulnerability assessments and penetration tests, and the retention period for security logs (Detect 1.4 and 2.2; Testing 1.1 and 1.4) [2]. In those cases, write the interval you have chosen into your policy and have it approved, so the auditor has a number to test against.
A readiness checklist
The checklist below turns the Central Bank of Iraq cybersecurity requirements into checks, in our own words. It is a starting point, not a substitute for reading the full text. Each item is tagged with the control numbers it rests on [2].
Governance and Risk Management
- A cybersecurity policy approved by the board, with the date of its last update (Governance, IT Policy, items (a) and (c)).
- An IT Steering Committee and a Cybersecurity Committee with the required membership, each with minutes (IT Governance; Information Security Governance).
- The governance roles the document lists (CISO, CIO, CTO, Chief Risk Officer) defined and assigned where they exist in your structure (Governance).
- An up-to-date organisation chart, a job description with a backup for each IT role, and segregation of duties (Documentation).
- The KPIs in IT and Security Infrastructure Management measured and reported (KPIs 1 to 96).
- Every gap that cannot be closed now documented in a compliance plan, with a time-bound exception request to the CBI (Governance, IT Policy, item (e)).
- An IT risk management committee, and an approved risk appetite and risk tolerance (2.4.1 to 2.4.3).
- A business impact analysis, risk scenarios and key risk indicators (2.5.1, 2.5.2, 2.6.1).
- A risk assessment of suppliers and third parties, and cybersecurity, non-disclosure and secure-deletion clauses in their contracts (2.3; Protect 13.1.4, 13.1.6).
Identify
- An IT asset inventory with an owner and a custodian for each asset, reviewed periodically (Identify 1.3 to 1.6).
- An approved software list, and no unlicensed software (1.11 to 1.14).
- A classification policy with the four levels and the handling rules for each, and a written procedure for notifying the CBI when classified information leaks (Identify 4).
Protect
- Password and privileged-account settings that match the stated values (8.2, 8.4).
- A patch management procedure with a timeframe for each category (9.1).
- Multi-factor authentication on every web application that staff or customers reach over the internet, and a WAF in front of external web applications (14.1.3, 14.1.4).
- Network baseline standards, security zones, encrypted remote administration and changed default passwords (3.1).
- ATM/POS and mobile financial services controls, where you offer those services (4, 11).
- Direct database access limited to database administrators (12.1.3).
Detect
- Intrusion detection and prevention, regular log review, and a retention period written into policy (Detect 1.2, 1.4).
- A continuous monitoring capability, in-house or through a security operations centre (1.5).
- An annual information systems audit plan, an internal audit at least once a year, and documented follow-up of findings (2.1.3, 2.1.4).
- A regular independent information security audit (2.2).
- A regulatory compliance process, and a documented position on each of PCI DSS, EMV and SWIFT CSP that applies to you (2.3, 2.4).
Respond
- An incident management framework with documented severity criteria and escalation procedures, and an IT emergency response team (Respond 1.1 to 1.5).
- Periodic testing of the escalation and response plan (1.4).
- A written procedure for informing the CBI as soon as possible if a disaster occurs, and for informing customers of major incidents (1.6, 1.7).
- A template for the root-cause and impact analysis report with its three parts (1.9).
- An approved BCP and DRP tested within the last year, a geographically separate recovery site, and defined RTO and RPO values (2.1, 2.2).
- Periodic testing of backup restoration (3.10).
Awareness and Testing
- Awareness training or a workshop for all employees, and training for the information systems audit team (Awareness 2.3, 2.4).
- A customer education programme with defined channels (Awareness 1, 3).
- Regular vulnerability assessment combining automated and manual techniques, with remediation validation (Testing 1.1 to 1.3).
- Penetration testing of network infrastructure and internet-facing systems, and independent testing of web applications (Testing 1.4; Protect 14.4.11).
The controls and the banking-reform technical audit
The Cyber Resilience Controls and the CBI’s Standards Booklet for private commercial and Islamic banks («كتيب المعايير») are two separate documents issued by the Central Bank of Iraq [2][4]. The booklet describes its standards as mandatory for private banks [4], and some of them bear directly on cybersecurity:
- Standard B7.1: strong, secure and stable infrastructure that is resilient and can withstand cyberattacks, and protection of all data from unauthorised access and manipulation, in line with CBI specifications detailed in the Assessment Guidelines [4][5].
- Standard B7.2: assurance of the bank’s adherence to the infrastructure and data-encryption specifications is conducted by a third-party specialist firm from a list of CBI-approved firms [4][5].
- Standard B9: fully documented and audited business continuity and disaster recovery plans, audited by a firm from the same list [4][5].
The booklet’s text does not name the Cyber Resilience Controls [4][5], but the two documents overlap in subject matter. Business continuity and disaster recovery plans, for example, are required both in the controls' Respond chapter (Respond 2) and in the booklet’s B9 [2][4]. A bank that organises its evidence by control number therefore enters the technical audit with its evidence already in order. For details, see Banking-reform technical audit readiness. (The CBI’s English version of the booklet states that it is provided for reference only and that the Arabic version is the formal reference [5].)
How Red Crow by DigiFort helps
Red Crow is DigiFort’s cybersecurity practice. Through Compliance & audit readiness we work with banks, payment companies and licence applicants: we find the gaps against the CBI Cyber Resilience Controls, close them with you, and build the evidence your auditor will ask for. The Central Bank wrote the checklist. We work through it with you.
Each step of our method produces something specific, and each output answers particular chapters of the controls [2]:
| Step output | Where it maps in the controls |
|---|---|
| Scope, gap register and readiness scorecard | Every chapter, item by item |
| Remediation plan, with an owner and a date for each item | The compliance plan and exception request (Governance, IT Policy, item (e)) |
| Test findings and a review of logging and monitoring | Testing 1; Detect 1 |
| Incident-response plan, playbooks and a tabletop exercise | Respond 1, including periodic testing of the escalation plan (1.4) |
| Evidence pack and mock-audit report | Audits (Detect 2) |
For banks: an engagement usually starts with supplier registration with your procurement team, then scoping, a proposal in your tender format, the gap register, remediation and the evidence pack.
For payment companies and licence applicants: a fixed-scope readiness assessment in which you receive a licence-checklist mapping, a penetration-test scope, a policy-set gap, an incident-response-plan gap and a remediation plan.
Where our role ends: DigiFort signs the gap register, the readiness scorecard, the remediation plan, the evidence pack and the mock-audit report. Third-party assurance under the Standards Booklet is signed by a CBI-approved third party[4].
Frequently asked questions
Who issued the Cyber Resilience Controls, and where is the official text?
The Central Bank of Iraq’s Information Technology and Payments Department, Policies, Regulation and Studies Section, issued them as a first edition [2]. The official text is an Arabic document published on the CBI website in a news item carrying the document’s title [1], and listed on the CBI’s Information Technology and Payments page [3].
Do the controls cover payment companies and non-bank financial institutions?
The document addresses institutions and entities in the financial and banking sector without listing licence categories, and its glossary defines non-bank financial institutions [2]. The CBI lists it on its Information Technology and Payments page alongside instructions addressed to e-payment service providers [3]. Confirm how it applies to your category in light of your licence and CBI instructions.
Are the controls mandatory, and what if a control cannot be met?
The document describes itself as guidance, but most of its controls are worded with "must" («يجب»). Where an institution does not comply, it submits a compliance plan to the Central Bank of Iraq requesting an exception for a defined period (Governance, IT Policy, item (e)) [2].
How often must information systems be audited and continuity plans tested?
The internal information systems audit happens at least once a year under an annual plan (Detect 2.1.3 and 2.1.4), and the business continuity and disaster recovery plans are tested and reviewed at least once a year (Respond 2.1.5 and 2.2.11) [2]. The independent audit is described as regular, with no interval set (Detect 2.2) [2].
Do the controls require penetration testing?
Yes. The Testing chapter requires penetration tests of network infrastructure and internet-facing systems periodically or as needed (Testing 1.4), alongside regular vulnerability assessments (Testing 1.1). The Protect chapter requires periodic independent penetration testing of web applications (Protect 14.4.11) [2].
How do the controls relate to NIST CSF and to international payment and financial-messaging standards?
The document says its guidelines are based in general on the NIST Cybersecurity Framework, and its references list ISO/IEC 27001 and ISO/IEC 27005 [2]. In the Detect chapter (item 2.4) it names PCI DSS, EMV and SWIFT CSP among the CBI regulations and instructions that institutions must comply with [2].
Sources
- Central Bank of Iraq, «ضوابط الصمود السيبراني للقطاع المالي والمصرفي في العراق» (news page): https://cbi.iq/news/view/2607
- Central Bank of Iraq, Information Technology and Payments Department, «ضوابط الصمود السيبراني للقطاع المالي والمصرفي في العراق», first edition (Arabic PDF): https://cbi.iq/static/uploads/up/file-171939700326129.pdf
- Central Bank of Iraq, Information Technology and Payments page: https://cbi.iq/page/133
- Central Bank of Iraq, «كتيب معايير البنك المركزي العراقي» (CBI Standards Booklet, for private commercial and Islamic banks), Arabic (official) version (PDF): https://cbi.iq/static/uploads/up/file-17761583642351.pdf
- Central Bank of Iraq, CBI Standards Booklet, English reference version (PDF): https://cbi.iq/static/uploads/up/file-176050874125670.pdf
- NIST, The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29 (PDF): https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf
- NIST, Cybersecurity Framework: https://www.nist.gov/cyberframework
Related
Talk to us
A senior practitioner replies.