CBUAE operational risk rules, what licensed firms must show
Map your critical operations, show how technology, providers and incidents are controlled, and keep your notification routes ready.
Official sources
Use the Central Bank's Rulebook to read the current text of each regulation.
Official website
The CBUAE Rulebook page for the Operational Risk Management Regulation. The Outsourcing Regulation for Banks is in the same Rulebook.
Visit rulebook.centralbank.ae ↗Get the document
The Central Bank publishes both regulations free of charge in the CBUAE Rulebook. The Rulebook says it has no legal effect and that the text issued through formal channels such as the Official Gazette prevails.
Open the official page ↗Works alongside
ISO 22301, ISO 27001, DORA and the NIST CSF cover related ground on resilience and technology risk.
Browse all frameworks →What CBUAE is
The Operational Risk Management Regulation sets the minimum standard for how licensed financial institutions manage operational risk and operational resilience. It includes duties on ICT and cybersecurity, incident management, business continuity, change management and third party risk.
The separate Outsourcing Regulation for Banks adds rules for banks on contracts, data, outsourcing outside the UAE and approval from the Central Bank before outsourcing material activities.
How CBUAE got to where it is today
The milestones that changed what organisations have to do.
Earlier operational risk rules
The Central Bank issues Circular 163/2018, the Operational Risk Regulation and Standards, on 29 August 2018.
Outsourcing rules for banks
The Outsourcing Regulation for Banks, C 14/2021, takes effect on 15 July 2021.
Deadline for older outsourcing contracts
All outsourcing agreements, including those signed before the regulation, had to comply by 31 December 2023.
New Central Bank law
Federal Decree-Law No. 6 of 2025 on the Central Bank and the regulation of financial institutions becomes the legal basis cited by the new regulation.
Operational Risk Regulation in force
The new Operational Risk Management Regulation, C 1/2026, takes effect on 14 September 2026 and cancels the 2018 circular.
Dates are for orientation. The official website holds the authoritative record.
Do you need it?
If any of these sound familiar, probably yes.
You are a bank, insurer or other financial institution licensed by the Central Bank of the UAE.
You rely on technology providers or cloud services for critical operations.
You need to map critical operations and test continuity and recovery.
You must be ready to notify the Central Bank within hours of a serious event.
What it asks of you
The rules fall into six areas, from Board duties to incident reporting.
Governance and risk framework
Board approval, senior management duties, an independent risk function and a documented framework.
Operational resilience
Map critical operations, set tolerance for disruption and plan for disruption.
ICT and cybersecurity
A Board-approved technology and cyber risk framework, with the system of record kept in the UAE.
Incident management
Classify, respond to, record and learn from incidents.
Third parties and outsourcing
Due diligence, contracts, regulator access, exit plans and approval for material outsourcing.
Notification and disclosure
Notify the Central Bank on time and disclose how you manage operational risk.
The 4 parts, 19 article groups and 132 obligations
This page follows the Central Bank of the UAE's Operational Risk Management Regulation, which covers operational risk, resilience, ICT and cybersecurity and third parties for licensed financial institutions, and the separate Outsourcing Regulation for Banks. References use article and clause numbers from the Rulebook.
19 article groups · 132 obligations
AOperational risk framework and governanceBoard and management duties and the risk framework (Operational Risk Management Regulation, Articles 2 and 4 to 7).5 article groups · 32 obligations
a2Operational risk framework (Article 2)One documented framework to identify, assess, monitor and control operational risk.6 obligations
- ORM 2.1
Have an operational risk management framework with strategies, policies, procedures, systems and controls to identify, assess, monitor, report and control operational risk in good time.
What you do
- Write the framework
- Name owners for each part
- ORM 2.2
Integrate the framework into your broader risk management and governance.
What you do
- Link it to the enterprise risk framework
- Use shared risk categories
- ORM 2.3
Keep strategy, policies and processes consistent with your risk profile and appetite, and revise them when the risk profile changes materially.
What you do
- Set review triggers
- Record each revision
- ORM 2.4
Cover all material aspects of operational risk, including activities outsourced to or reliant on third parties.
What you do
- Include outsourced services in risk assessments
- Review yearly
- ORM 2.5
Document at minimum the governance structure, policies including appetite and tolerance, assessment tools, common terminology, limits and thresholds, monitoring and reporting, and mitigation strategies.
What you do
- Use a checklist against the article
- Keep one controlled document
- ORM 2.6
Manage internal and external fraud risk within the framework, including incidents or threats affecting customers.
What you do
- Add fraud scenarios to risk assessments
- Track fraud incidents and customer impact
Evidence to keep
- Operational risk management framework
- Risk appetite and tolerance statement
- Fraud risk assessment
a4Role of the Board (Article 4)The Board carries ultimate responsibility and approves the key strategies.7 obligations
- ORM 4.1
Have the Board bear ultimate responsibility for an adequate operational risk framework that is integrated into broader risk management and includes operational resilience.
What you do
- Record Board accountability in its charter
- Report to the Board regularly
- ORM 4.2
Have the Board itself, not a committee, approve and review at least annually the operational risk and resilience strategies, the risk appetite and tolerance, the tolerance for disruption and the continuity and recovery plans, with a review of those plans at least every three years if delegated.
What you do
- Put the approvals on the Board calendar
- Record the delegation of annual plan reviews
- ORM 4.3
Run a formal process to oversee senior management and confirm approved strategies and limits are applied.
What you do
- Receive regular dashboards
- Challenge exceptions
- ORM 4.4
Have the Board approve, oversee and ensure the effectiveness of the ICT and cybersecurity risk management framework.
What you do
- Table the framework for approval
- Review its effectiveness each year
- ORM 4.5
Make sure internal audit independently reviews the operational risk framework.
What you do
- Include the framework in the audit plan
- Report findings to the Board
- ORM 4.6
Build a strong operational risk culture and communicate the approach to staff, third parties and group entities.
What you do
- Run awareness sessions
- Include risk behaviours in performance goals
- ORM 4.9
Set up a Board operational risk committee or designated Board committee if you are designated systemically important, or if the Central Bank requires it.
What you do
- Check your designation
- Write the committee charter if needed
Evidence to keep
- Board approvals and minutes
- Tolerance for disruption statement
- Internal audit review of the framework
a5Role of senior management (Article 5)Management turns the framework into working controls and reports upward.7 obligations
- ORM 5.1
Have senior management put the Board-approved framework and resilience strategy into effective policies, controls and systems.
What you do
- Assign owners to each policy
- Track implementation
- ORM 5.2
Monitor the operational risk profile and material exposures through strong processes and reporting.
What you do
- Use a risk dashboard
- Review it monthly
- ORM 5.3
Report operational risk and resilience to the Board regularly, in a timely and proactive way.
What you do
- Fix a reporting calendar
- Escalate emerging issues early
- ORM 5.4
Report any breaches or expected breaches of appetite, tolerance, thresholds and limits to the Board itself, not only a committee.
What you do
- Define breach escalation rules
- Keep a breach log
- ORM 5.6
Assess the internal control system regularly, at least yearly for banks and insurers, and give a report on internal control to the Board and the Central Bank.
What you do
- Prepare the report each year
- Include key controls for critical operations and improvement actions
- ORM 5.7
Regularly evaluate the design, implementation and effectiveness of ICT and cybersecurity risk management.
What you do
- Review control test results
- Report gaps
- ORM 5.8
Provide enough staff, skills and resources, and make sure staff receive regular training.
What you do
- Match headcount to risk
- Track training completion
Evidence to keep
- Management reports to the Board
- Annual report on internal control
- Resourcing and training plan
a6Operational risk function (Article 6)An independent second-line function under the Chief Risk Officer.3 obligations
- ORM 6.1
Run an adequately resourced, sufficiently independent operational risk management function under the Chief Risk Officer.
What you do
- Define its charter
- Protect its independence
- ORM 6.2
Have the function form an independent view of risks and controls, challenge business use of tools, maintain policies, monitor the profile, identify threats, assess vulnerabilities of critical operations, and provide training.
What you do
- Document each task
- Keep challenge notes
- ORM 6.3
Have the function report its findings and recommendations to the Board regularly.
What you do
- Add a standing item to Board packs
- Track recommendations
Evidence to keep
- Operational risk function charter
- Challenge and review reports
- Training materials
a7Internal control system (Article 7)Controls, three lines of defence, reporting and stress testing.9 obligations
- ORM 7.1
Foster a strong control environment with an effective internal control system covering risk assessment, control activities, monitoring, and information and communication.
What you do
- Map controls to the four components
- Review them yearly
- ORM 7.3
Cover all activities in the control system, including those fully or partly reliant on third parties.
What you do
- Include providers in control testing
- Collect provider assurance reports
- ORM 7.4
Use control measures such as approval authorities, segregation of duties, dual control, limit monitoring, access safeguards, reconciliations and mandatory leave.
What you do
- Review which controls are in use
- Close any gaps
- ORM 7.7
Review processes for manual steps that could be automated, and assess the accuracy and risks of automated controls.
What you do
- Flag manual controls
- Test automation accuracy
- ORM 7.8
Keep a register of processes, the process universe, with a process owner and risk owner for each.
What you do
- Build the register
- Update it with changes
- ORM 7.9
Apply three lines of defence: business management, risk and compliance functions, and internal audit.
What you do
- Document responsibilities for each line
- Avoid overlaps
- ORM 7.10
Monitor operational risk profiles and exposures with reporting that is comprehensive, accurate, consistent, actionable and timely in normal and stressed conditions.
What you do
- Define report content and frequency
- Test reports in drills
- ORM 7.13
Stress-test operational risk periodically, including exercises such as penetration testing across ICT, physical, people and other risk vectors.
What you do
- Plan yearly stress tests
- Record results and fixes
- ORM 7.14
Include independent third-party penetration testing, at least for Critical Functions, and present results to the Board.
What you do
- Appoint an independent tester
- Present findings to the Board
Evidence to keep
- Internal control framework
- Process universe register
- Operational risk reports
- Penetration test reports for critical functions
BResilience, ICT and incidentsHow you protect critical operations, manage technology risk and handle disruption (Articles 3, 8, 9, 10, 11 and 12).6 article groups · 38 obligations
a3Operational resilience (Article 3)Know your critical operations and plan to keep them running.6 obligations
- ORM 3.1
Have an operational resilience strategy, with policies and controls, that helps you respond to, adapt to, recover from and learn from disruption.
What you do
- Write the strategy
- Link it to the risk framework
- ORM 3.2
Use the risk framework to find internal and external threats and failures in people, processes and systems and assess critical operations for vulnerabilities.
What you do
- Run scenario workshops
- Record vulnerabilities
- ORM 3.3
Set out when senior management must alert the Board about disruption or potential disruption.
What you do
- Define escalation triggers
- Test them in exercises
- ORM 3.4
Identify critical operations and the people, technology, processes, data, facilities and providers that support them, with their dependencies, in a map kept up to date through change management.
What you do
- Build a map for each critical operation
- Update it with each change
- ORM 3.5
Treat payment systems and services, accurate financial records, solvency and liquidity management and anything the Central Bank designates as critical operations at minimum.
What you do
- Confirm your critical list includes these
- Record any additions
- ORM 3.6
Develop and regularly review incident response, business continuity and disaster recovery plans for all critical operations.
What you do
- Keep all three plans current
- Review them at least yearly
Evidence to keep
- Operational resilience strategy
- Critical operations map
- Incident response, business continuity and disaster recovery plans
a8ICT and cybersecurity management (Article 8)A strong technology and cyber risk framework inside the operational risk framework.10 obligations
- ORM 8.1
Implement an ICT and cybersecurity risk framework covering risk identification, mitigation, regular monitoring and testing, and ongoing proactive management.
What you do
- Define the four stages
- Assign owners
- ORM 8.2
Address ICT and cybersecurity risk and resilience in your risk appetite and tolerance, including performance and tolerance for disruption.
What you do
- Add ICT measures to the appetite statement
- Set tolerance levels
- ORM 8.3
Maintain ICT and cybersecurity infrastructure for current and projected needs, including during stress, to keep data and systems intact, confidential and available.
What you do
- Run capacity reviews
- Plan upgrades
- ORM 8.4
Keep the Board and senior management informed about ICT and cybersecurity risk exposures, incidents and weaknesses found in testing.
What you do
- Add an ICT section to Board reports
- Share test findings
- ORM 8.5
Run protection, detection, response and recovery programmes for ICT and cybersecurity, regularly tested and informing risk decisions.
What you do
- Test each programme yearly
- Use the results in risk reviews
- ORM 8.6
Make the ICT and cybersecurity policy cover governance, risk ownership, security measures, monitoring, data management, operations, incident and recovery plans, project management and systems development.
What you do
- Use a checklist against the article
- Review the policy yearly
- ORM 8.7
Review ICT and cybersecurity risk management against industry standards, test it for gaps against tolerance, and use actionable threat intelligence.
What you do
- Compare to a recognised standard
- Subscribe to threat feeds
- ORM 8.8
Manage ICT systems proactively, including those run by providers, and plan the renewal or retirement of obsolete and unsupported hardware and software.
What you do
- Track end-of-support dates
- Plan replacements
- ORM 8.9
Keep the Master System of Record continuously in the UAE, including when outsourced, with branches of foreign institutions able to keep an up-to-date copy in the UAE with Central Bank approval.
What you do
- Document where the system of record is held
- Seek approval if using a copy
- ORM 8.10
Comply with regulations on ICT, cyber and information security issued by other relevant UAE authorities.
What you do
- List applicable UAE rules
- Assign an owner for each
Evidence to keep
- ICT and cybersecurity policy
- ICT risk assessments
- Test results and monitoring reports
- Master System of Record location evidence
a9Incident management (Article 9)Plans to respond to and learn from incidents across their full life cycle.5 obligations
- ORM 9.1
Develop and implement incident response and recovery plans for incidents that could disrupt critical operations, including ICT and cybersecurity incidents.
What you do
- Write plans per scenario
- Align with your tolerance for disruption
- ORM 9.2
Review, test and update the plans using lessons from previous incidents and fix root causes of material incidents.
What you do
- Hold a review after each incident
- Measure fix effectiveness
- ORM 9.3
Keep an inventory of internal and third-party resources needed for response and recovery.
What you do
- List teams, tools and providers
- Check availability yearly
- ORM 9.4
Cover the whole incident life cycle: severity classification, response and recovery procedures, roles, communication plans including to the Central Bank, and a register of incidents.
What you do
- Define severity criteria
- Keep the incident register current
- ORM 9.5
Make incident management cover all critical operations and all resources in the critical operations map.
What you do
- Check each critical operation has a plan
- Update with map changes
Evidence to keep
- Incident response and recovery plans
- Incident register
- Lessons learned records
a10Risk data and systems (Article 10)Systems that deliver reliable risk data and reporting, including in a crisis.4 obligations
- ORM 10.1
Make sure risk information systems deliver the performance your risk profile needs, including under stress.
What you do
- Test reporting under stress
- Fix capacity gaps
- ORM 10.2
Have governance and internal controls to manage and protect data effectively.
What you do
- Name data owners
- Review data controls yearly
- ORM 10.3
Make ICT systems able to monitor operational risk and resilience, compile accurate risk and loss data, and meet internal and external reporting needs including during a crisis.
What you do
- Maintain a loss database
- Test ad hoc reporting
- ORM 10.4
Subject aggregation and reporting processes to strong validation and periodic internal audit review.
What you do
- Add the processes to the audit plan
- Record validation checks
Evidence to keep
- Risk data governance documents
- Reporting capability tests
- Internal audit review of aggregation
a11Business continuity planning (Article 11)Continuity and disaster recovery plans built on realistic scenarios and tested at least yearly for critical operations.9 obligations
- ORM 11.1
Maintain continuity and disaster recovery plans for critical operations that fit into the operational risk and resilience framework, built on the critical operations map.
What you do
- Link each plan to the map
- Keep one owner per plan
- ORM 11.3
Have the second and third lines review the plans at least yearly for critical operations.
What you do
- Schedule yearly reviews
- Keep review notes
- ORM 11.4
Identify disruption scenarios and how they affect critical operations, including dependencies and key staff unavailability.
What you do
- Build a scenario library
- Plan for key person absence
- ORM 11.6
Assess each scenario with a quantitative and qualitative impact or business impact analysis across financial, operational, legal and reputational effects.
What you do
- Run a business impact analysis
- Update it when operations change
- ORM 11.7
Set clear triggers for activating the plans, such as maximum tolerable outage thresholds.
What you do
- Define thresholds
- Train decision makers
- ORM 11.8
Set measurable recovery time and recovery point objectives that reflect the Board-approved tolerance for disruption.
What you do
- Agree targets per critical operation
- Measure actual recovery
- ORM 11.9
Include communication arrangements for the Board, management, staff, authorities including the Central Bank, customers, the public and providers.
What you do
- Prepare contact lists and message templates
- Test them
- ORM 11.10
Review and test plans regularly, at least yearly for critical operations, include key providers where relevant, and report results to the Board and management.
What you do
- Run a yearly test
- Report outcomes
- ORM 11.11
Run exercises under severe but plausible scenarios to assess your ability to deliver critical operations through disruption.
What you do
- Choose realistic scenarios
- Record gaps and fixes
Evidence to keep
- Business continuity and disaster recovery plans
- Business impact analyses
- Test and exercise reports
a12Change management (Article 12)Plan and control changes to products, processes and systems.4 obligations
- ORM 12.1
Run a well-resourced change management process to plan, manage and approve changes in operations, including new, changed or discontinued products, processes and systems.
What you do
- Use one approval route
- Resource it adequately
- ORM 12.2
Involve the operational risk function throughout change management so controls and control functions are involved.
What you do
- Add risk sign-off to the change workflow
- Keep records
- ORM 12.3
Set change policies that consider inherent risks, risk profile effects, controls, residual risk, limits, capacity, the role of the three lines, impacts on the critical operations map and data, and communication, including for emergency changes.
What you do
- Use a change risk checklist
- Define an emergency change route
- ORM 12.4
Monitor changes in operations after implementation to find and manage problems.
What you do
- Run post-implementation reviews
- Track issues to closure
Evidence to keep
- Change management policy
- Change risk assessments
- Post-implementation reviews
CThird parties, notification and disclosureProvider oversight, regulator notifications and public disclosure (Articles 13 to 16).3 article groups · 19 obligations
a13Third party risk management (Article 13)Assess, contract, monitor and plan an exit for providers that support critical operations.12 obligations
- ORM 13.1
Have a Board-approved strategy and policies for assessing, monitoring and managing third party risk within the operational risk framework.
What you do
- Write the strategy
- Obtain Board approval
- ORM 13.2
Avoid over-reliance on outsourcing and keep enough staff, expertise and resources to manage the activities you are licensed for.
What you do
- Document retained capability
- Review yearly
- ORM 13.3
Perform a risk assessment and appropriate due diligence before entering any arrangement with a provider.
What you do
- Use a due diligence checklist
- Keep the results
- ORM 13.4
For arrangements supporting critical operations, verify the provider has at least equivalent operational resilience.
What you do
- Request provider resilience evidence
- Test it where possible
- ORM 13.5
Obtain the Central Bank's notice of non-objection before outsourcing any activity that could significantly affect critical operations if disrupted.
What you do
- Identify such activities
- Submit requests early
- ORM 13.6
Govern provider arrangements by binding written contracts covering rights, obligations, data ownership and confidentiality, termination, and for critical operations the right to inspect records and receive audit and risk reports.
What you do
- Use contract templates with these clauses
- Check each contract
- ORM 13.7
Require providers in contracts to comply with Central Bank requests and notifications, and for critical arrangements allow Central Bank on-site examinations.
What you do
- Add regulator access clauses
- Confirm providers accept them
- ORM 13.8
Make the contract terms on inspection and regulator access enforceable against subcontractors where data may be shared with them.
What you do
- Require flow-down clauses
- Ask for a subcontractor list
- ORM 13.9
Keep resources and controls to manage providers, including a register of arrangements for critical operations, performance and risk metrics, ongoing assessments including financial health, and management of dependencies.
What you do
- Maintain the register
- Review provider performance on a schedule
- ORM 13.10
Address reliance on providers in the continuity plan and in the map of critical operations assets.
What you do
- Add providers to the map
- Include them in continuity scenarios
- ORM 13.11
Keep viable contingency and exit plans for providers material to critical operations, and assess how easily each provider could be replaced.
What you do
- Write exit plans
- Record substitutability for each provider
- ORM 13.12
Be ready for the Central Bank to require you to end a provider arrangement or a critical operation that depends too heavily on providers.
What you do
- Reduce single-provider dependence
- Keep exit options current
Evidence to keep
- Board-approved third party risk strategy
- Due diligence and risk assessments
- Contracts and register of outsourced activities
- Exit plans
a15Notification and reporting (Article 15)Tell the Central Bank quickly about significant deviations, events and high-risk incidents.4 obligations
- ORM 15.1
Notify the Central Bank promptly of a significant deviation from your Board-approved risk appetite, policies or tolerance for disruption, or of a material operational risk that is not properly addressed.
What you do
- Define what counts as significant
- Name who notifies
- ORM 15.2
Notify the Central Bank of events that significantly affect critical operations: within 4 hours with the affected critical operations, within 24 hours with a summary report, and again on return to normal operations.
What you do
- Prepare a 4-hour and 24-hour template
- Keep a contact sheet
- ORM 15.3
Notify the Central Bank within 72 hours of any high-risk incident, as defined in Board-approved criteria.
What you do
- Define high-risk criteria in policy
- Test the 72-hour process
- ORM 15.4
Provide any operational risk information the Central Bank asks for, and meet its regular reporting and notification requirements.
What you do
- Keep a reporting calendar
- Track new notices
Evidence to keep
- Notification procedure with deadlines
- Notification log
- Incident classification criteria
a16Disclosure (Article 16)Say publicly how you manage operational risk and resilience.3 obligations
- ORM 16.1
Have a policy on public disclosure about operational risk and internal controls that sets what is and is not disclosed.
What you do
- Write the policy
- Get approval
- ORM 16.2
Publicly disclose key information about your operational risk and resilience approach and exposure, in proportion to your size and role.
What you do
- Draft a yearly disclosure
- Have it reviewed by risk and legal
- ORM 16.4
Give insight in your disclosures into how you protect personal data.
What you do
- Add a privacy practices section
- Keep it consistent with other statements
Evidence to keep
- Public disclosure policy
- Published operational risk and resilience disclosures
DOutsourcing Regulation for BanksThe separate rules for banks outsourcing activities (Regulation C 14/2021, Articles 2 to 9).5 article groups · 43 obligations
o2Governance and risk management (Article 2)Banks stay fully responsible for what they outsource.6 obligations
- OUT 2.1
Remain fully responsible for risks from any outsourced process or activity.
What you do
- State this in the outsourcing policy
- Keep ownership with a named senior manager
- OUT 2.2
Have a process to decide the materiality of each outsourced activity.
What you do
- Define materiality criteria
- Record the decision for each arrangement
- OUT 2.3
Include policies in the risk governance framework to assess proposed outsourcing and to identify, measure, monitor and report its risks.
What you do
- Add outsourcing to the risk framework
- Report on it regularly
- OUT 2.5
Provide at minimum a Board-approved materiality policy with Board or committee approval of material outsourcing, conflict of interest controls, clear roles, timely risk reporting to the Board, and coverage of critical outsourced functions in continuity plans.
What you do
- Use a checklist against the article
- Check provider continuity plans
- OUT 2.6
Make sure providers keep appropriate information security, risk management and service delivery levels.
What you do
- Add security requirements to contracts
- Check them during reviews
- OUT 2.7
Stay responsible for compliance with all laws and regulations that apply to the outsourced activities.
What you do
- Map laws to each outsourced service
- Monitor provider compliance
Evidence to keep
- Board-approved outsourcing policy
- Materiality assessments
- Conflict of interest controls
- Provider continuity plans
o3Outsourcing register and data protection (Articles 3 and 4)Keep a full register and protect data in outsourced arrangements.6 obligations
- OUT 3.1
Maintain a comprehensive, up-to-date register of all outsourcing arrangements, material and non-material, on a solo and group basis.
What you do
- Build the register
- Update it when contracts change
- OUT 3.2
Record in the register the provider details, start and end dates, a service description, whether confidential data is involved and whether the arrangement is material.
What you do
- Use a register template
- Review entries yearly
- OUT 4.1
Comply with all applicable UAE legislation and regulations when outsourcing involves managing and processing data.
What you do
- List applicable data rules
- Check each arrangement against them
- OUT 4.2
Retain ownership of all data given to a provider, and keep customers' ownership and ability to exercise their rights.
What you do
- Add data ownership clauses
- Test data return
- OUT 4.3
Make sure subcontractors that handle confidential data fully meet the same requirements.
What you do
- Require flow-down terms
- Verify subcontractor controls
- OUT 4.4
Secure your data from unauthorised access, including access by the provider or its staff.
What you do
- Limit provider access
- Log and review provider access
Evidence to keep
- Outsourcing register
- Data ownership and access clauses
- Subcontractor compliance evidence
o5Outsourcing agreements (Article 5)Contract terms every outsourcing agreement must contain.9 obligations
- OUT 5.1
Make sure agreements keep full ownership of data with the bank and customers, and let the Central Bank access it on request.
What you do
- Add data ownership and regulator access clauses
- Check each contract
- OUT 5.2
Give the bank unfettered access to its data for the whole agreement, including on termination.
What you do
- Add access and return clauses
- Test retrieval
- OUT 5.3
Include data protection terms such as non-disclosure and data destruction after termination.
What you do
- Require destruction certificates
- Keep them on file
- OUT 5.4
Set data protection standards in the agreement, including nationally recognised information assurance standards in the UAE.
What you do
- Name the standards
- Ask for evidence of conformity
- OUT 5.5
Prevent the provider or its subcontractors from giving anyone else access to confidential data without specific authorisation from the bank or customer.
What you do
- Add a no-onward-access clause
- Audit access logs
- OUT 5.6
Specify how far and under what conditions subcontracting is allowed.
What you do
- Require prior approval of subcontractors
- Keep a subcontractor list
- OUT 5.7
Give the Central Bank and its agents access to the provider, including on-site visits, and require the provider to supply data needed for supervision.
What you do
- Add a regulator access clause
- Confirm the provider accepts it
- OUT 5.8
Require the provider to notify the bank without undue delay of any breach of the bank's data, especially confidential data.
What you do
- Set a notification window
- Test the contact route
- OUT 5.9
Govern all outsourcing by formal contracts between the bank and the provider.
What you do
- Keep signed contracts in a central store
- Prevent work starting without one
Evidence to keep
- Standard outsourcing contract terms
- Signed outsourcing contracts
- Contract compliance checklist
o6Outsourcing outside the UAE (Article 6)Extra safeguards when data or services leave the UAE.14 obligations
- OUT 6.1
Keep the Master System of Record, including all confidential data, continuously in the UAE.
What you do
- Document where it is held
- Review after system changes
- OUT 6.2
If you are a branch of a foreign bank, keep a copy of the Master System of Record, updated at least daily, in the UAE, subject to Central Bank approval.
What you do
- Seek approval
- Check daily updates run
- OUT 6.3
Do not share customer confidential data outside the UAE without Central Bank approval, the customer's prior written consent and written acknowledgement that it may be accessed in legal proceedings abroad.
What you do
- Create a consent form
- Keep approvals on file
- OUT 6.4
Do not outsource in a way that shares confidential data with a provider in a jurisdiction that cannot protect it as well as if it were kept in the UAE.
What you do
- Assess each jurisdiction
- Record the conclusion
- OUT 6.5
Make sure agreements with providers outside the UAE keep data ownership with the bank and customer and allow Central Bank access to the data.
What you do
- Add clauses specific to foreign providers
- Confirm enforceability
- OUT 6.6
Do not store data in a jurisdiction where bank secrecy or other laws limit access needed for supervision.
What you do
- Check legal restrictions
- Avoid affected locations
- OUT 6.7
Consider how changes in economic, political, social, legal or regulatory conditions could affect a provider outside the UAE, and manage this through provider selection, contracts and continuity planning.
What you do
- Add country risk to due diligence
- Plan for changes
- OUT 6.8
Consider other risks from foreign providers such as weaker infrastructure, legal differences and reputational risk.
What you do
- Include these in risk assessments
- Record mitigations
- OUT 6.9
Comply with all relevant personal data protection legislation before entering an outsourcing agreement with a party outside the UAE.
What you do
- Run a data protection check first
- Keep the evidence
- OUT 6.10
Set policies and monitoring controls for relationships that involve sharing confidential data outside the UAE.
What you do
- Write the policy
- Monitor on a schedule
- OUT 6.11
Define concrete security requirements for each relationship that involves confidential data outside the UAE, and train staff on them.
What you do
- List requirements per provider
- Train relevant staff
- OUT 6.12
Make sure subcontractors involved in sharing confidential data outside the UAE meet the same obligations.
What you do
- Require flow-down terms
- Verify compliance
- OUT 6.13
Make sure third parties maintain an appropriate level of information security and service delivery.
What you do
- Request security reports
- Review service levels
- OUT 6.14
Accept that the Central Bank may use its powers with providers outside the UAE through cooperation with foreign authorities.
What you do
- Mention this in contracts
- Keep contacts for the provider's regulator
Evidence to keep
- Cross-border outsourcing risk assessment
- Customer consents and Central Bank approvals
- Data location evidence
o7Audit, non-objection and reporting (Articles 7 to 9)Keep outsourcing within audit and compliance, get approval first and report to the Central Bank.8 obligations
- OUT 7.1
Keep outsourced activities fully in scope of internal audit and compliance.
What you do
- Include providers in audit universe
- Plan provider audits
- OUT 7.2
Have internal audit regularly review and report to the Board or audit committee on compliance with and effectiveness of outsourcing policies.
What you do
- Schedule the review
- Report findings
- OUT 7.3
Have the compliance function regularly report on providers' compliance with applicable laws, regulations and policies.
What you do
- Set a monitoring plan
- Report to senior management
- OUT 8.1
Obtain the Central Bank's prior notice of non-objection before outsourcing any material activity, including to related parties.
What you do
- Identify material activities early
- Allow time for the request
- OUT 8.2
Expect that the Central Bank will generally not permit outsourcing of core banking activities or key management and control functions such as risk, compliance, internal audit and senior management oversight.
What you do
- Keep those functions in house
- Seek advice before exploring exceptions
- OUT 9.1
Report regularly on outsourcing arrangements to the Central Bank in the format and frequency it sets.
What you do
- Add reporting to the compliance calendar
- Keep the data ready
- OUT 9.3
Provide the outsourcing register to the Central Bank when it asks.
What you do
- Keep the register export-ready
- Control versions
- OUT 9.4
Notify the Central Bank immediately of a material breach of an outsourcing agreement or other development that could significantly affect operations, reputation or finances.
What you do
- Define internal triggers
- Test the escalation route
Evidence to keep
- Internal audit and compliance reports on outsourcing
- Central Bank non-objection notices
- Outsourcing reports to the Central Bank
Nothing matches. Clear the search or pick another part.
Outcomes and implementation examples are from CBUAE Rulebook: Operational Risk Management Regulation and Outsourcing Regulation for Banks, published by NIST. Descriptions of what to do and the evidence lists are our own plain-English guidance. Check the official source for the authoritative text.
Your path to getting started
Five steps from first look to ready. Effort depends on your size and starting point.
- 1
Confirm your scope
Check whether you are a licensed financial institution, and whether you are a bank covered by the outsourcing rules.
- 2
Map critical operations
Identify critical operations and the people, technology, data and providers behind them.
- 3
Set appetite and tolerance
Get the Board to approve appetite, tolerance for disruption and the ICT and cyber framework.
- 4
Review providers
Check contracts, register, data location and exit plans for each material provider.
- 5
Test and be ready to report
Run continuity and incident exercises and rehearse the 4, 24 and 72 hour notifications.
How Optimus GRC helps
Each area maps to a part of the platform, so the work and the evidence sit together.
| What it asks | What you do in Optimus GRC |
|---|---|
| Governance and risk framework | Policy approvals, risk reports and appetite statements |
| Operational resilience | Critical operations map, continuity and recovery plans |
| ICT and cybersecurity | Control library, test results, penetration test reports |
| Incident management | Incident register and lessons learned |
| Third parties and outsourcing | Outsourcing register, contracts and exit plans |
| Notification and disclosure | Notification log and disclosure drafts |
Free CBUAE readiness checklist
A one-page PDF you can print or share with your team. No sign-up needed.
Download the checklist (PDF)- Operational risk framework outline
- Critical operations map template
- Outsourcing register and contract checklist
- Central Bank notification template
Share or cite this page
Writing about CBUAE? You are welcome to link to this guide. Copy the link below.
<a href="/frameworks/cbuae-regulations/">CBUAE explained in plain English - Optimus CyberX</a>Common questions
Does the new regulation replace the 2018 rules?
Yes. The Operational Risk Management Regulation C 1/2026 cancels and replaces Circular 163/2018, the Operational Risk Regulation and Standards.
Where are the cybersecurity requirements?
Article 8 of the Operational Risk Management Regulation sets ICT and cybersecurity duties and also requires compliance with ICT, cyber and information security rules from other relevant UAE authorities.
How fast must we notify the Central Bank?
For events that significantly affect critical operations, within 4 hours, with a summary report within 24 hours. High-risk incidents must be notified within 72 hours.
Must data stay in the UAE?
The Master System of Record must be kept continuously in the UAE, including when outsourced. Branches of foreign institutions may keep an up-to-date copy in the UAE with Central Bank approval.
Related frameworks
See how ready you are for CBUAE
Answer questions across every area. We email you a report showing where you comply and where you do not.