Insights · Data protection

DIFC data protection law: what it means for your IT, and a 2026 checklist

DIFC Law No. 5 of 2020 sets out how firms in the DIFC must handle personal data, and since July 2025 individuals can take you to the DIFC Courts if it goes wrong. Here’s what the law expects from your systems, written by an IT team rather than a law firm. See also our IT support for DIFC firms.
The short answer

The DIFC Data Protection Law (DIFC Law No. 5 of 2020) applies to any business that processes personal data in the DIFC as part of a stable arrangement, wherever that business is incorporated. It expects you to know what personal data you hold, protect it with appropriate security, notify the DIFC Commissioner of Data Protection as soon as practicable when a breach compromises it, and be able to prove all of this. Since 15 July 2025 individuals can also bring claims in the DIFC Courts, so your records, logs and evidence matter more than ever.

Key points
  • The law applies to processing in the DIFC, whether or not the controller, processor or sub-processor is incorporated there.
  • Breaches that compromise confidentiality, security or privacy go to the Commissioner as soon as practicable (Article 41), and to affected people too when the risk to them is high (Article 42).
  • You must notify (register) your processing with the Commissioner and renew it every year.
  • Transfers outside the DIFC now need a documented assessment of the protections in the recipient country.
  • Since July 2025, evidence of your controls is also your defence in a private claim.

Who does the DIFC data protection law apply to?

The law is run by the DIFC Commissioner of Data Protection. According to the Commissioner, it applies to a controller or processor, wherever it is incorporated, that processes personal data in the DIFC as part of stable arrangements rather than occasionally. Processing happens in the DIFC when the means or the people used to do it are physically there.

The July 2025 amendments widened this further, so the law covers processing in the DIFC regardless of whether the controller, processor or sub-processor is incorporated in the centre.

For IT, that means the picture is bigger than your office. Your Microsoft 365 tenant, your laptops and phones, your backups, your SaaS tools and the people at your IT provider who can reach your data are all part of it.

What changed in July 2025?

DIFC Amendment Law No. 1 of 2025 came into force on 15 July 2025. The changes that matter most for IT are:

  • Private claims. Individuals can bring a claim in the DIFC Courts for financial and non-financial damage. Controllers and processors need to be able to show they were not responsible for the incident.
  • Wider reach. Processing in the DIFC is covered regardless of where the controller, processor or sub-processor is incorporated.
  • Documented transfer assessments. Before sending personal data outside the DIFC, you must assess and record whether people will have adequate protection and effective remedies in the receiving country.
  • New fixed fines. Law firm summaries of the amendments report new administrative fines of roughly USD 25,000 to 50,000 for failures such as not notifying the Commissioner of processing or not carrying out a mandatory data protection impact assessment.

The common thread is evidence. Access reviews, audit logs, incident records and impact assessments are no longer just good practice; they are what you will rely on if a regulator or a court asks questions.

The core duties, translated into IT

DutyWhat the law expectsWhat it means for your IT
Know your dataRecords of processing, and notifying the Commissioner of what you processA data map: where personal data lives (mailboxes, SharePoint, CRM, file shares, backups, personal devices) and who can reach it
Keep it secureAppropriate technical and organisational measures (the accountability duties in Articles 14 to 22)Multi-factor authentication, encryption on devices and in transit, patching, endpoint protection and least-privilege access
Report breachesNotify the Commissioner as soon as practicable (Article 41) and affected people if the risk is high (Article 42)24/7 monitoring, alerting, an incident plan and logs kept long enough to investigate
Respect people’s rightsAccess, correction, erasure, portability and objection, among othersBeing able to find and export one person’s data across email, files and systems, plus retention rules
Control transfersA lawful basis for transfers outside the DIFC (Articles 26 and 27), now with a documented assessmentKnowing which country each cloud service stores data in, and a supplier list with locations and contract terms
Assess high-risk processingA data protection impact assessment before high-risk processingSystem diagrams, the controls in place and the remaining risk, supplied by IT
Appoint a DPO where requiredA Data Protection Officer for high-risk processing or when the Commissioner directs (Article 16); DPOs file an annual assessment (Article 19)Regular reports for your DPO: access reviews, incidents, patching and test results

What to do in the first hours of a data breach

  1. Contain it. Disable the compromised account, isolate the device, revoke sessions and tokens.
  2. Preserve evidence. Keep the logs: sign-ins, mailbox audit, file access and firewall records. Don’t wipe a laptop before it has been examined.
  3. Assess it. Does it compromise anyone’s confidentiality, security or privacy? Whose data, how much, and how sensitive?
  4. Notify the Commissioner as soon as practicable if it does.
  5. Tell the people affected as soon as practicable if the risk to them is high.
  6. Record everything: what happened, what you decided and why. That record is your evidence later.

Unlike ADGM, which sets a 72-hour target, the DIFC law does not set a fixed number of hours. “As soon as practicable” still means quickly, so the real question is operational: who gets the alert at 2am, and who can make the call?

A 12-point IT checklist for DIFC firms

  1. A data map showing where personal data is stored, including backups and personal devices.
  2. Multi-factor authentication on every account, starting with email and admin accounts.
  3. Encryption on all laptops and phones, with devices managed centrally.
  4. Least-privilege access, with access reviews at least every quarter.
  5. Audit logging switched on in Microsoft 365 and other key systems. We recommend keeping logs for at least 12 months (see why).
  6. 24/7 monitoring, with a named person who responds to alerts.
  7. A written incident response plan, tested at least once a year.
  8. Backups that are tested by actually restoring from them.
  9. Retention policies, so personal data is not kept for ever.
  10. A way to find and export everything you hold about one person.
  11. A supplier list showing where each provider stores your data, and on what terms.
  12. An evidence pack (policies, access reviews, test results, incident records) ready for the Commissioner, an auditor or a court.

How long should you keep audit logs?

There is no fixed legal minimum for log retention in the DIFC law, the PDPL or the ADGM regulations. What they require is that you can investigate a breach, report it quickly and prove your security, and logs are how you do that. Breaches are often found weeks or months after they start, so a short retention period can leave you unable to answer the regulator’s questions.

RuleWhat it says about logs
DIFC Data Protection LawNo set period. You must be able to investigate and report breaches as soon as practicable, and evidence matters for private claims since July 2025
UAE PDPL (onshore)No set period. Article 20 requires appropriate security and regular testing
ADGM Data Protection Regulations 2021No set period. The 72-hour breach notification target means logs must be readily available
DFSA cyber risk rules (GEN 5.5)Firms are expected to review system logs and security events regularly. Check wider DFSA record-keeping duties with your compliance officer
Saudi NCA Essential Cybersecurity Controls (2-12-3-5)At least 12 months for cybersecurity event logs, for organisations in scope in Saudi Arabia
PCI DSS (if you take card payments)12 months, with the most recent 3 months immediately available

Our recommendation is at least 12 months. It matches the strictest common standards, covers groups with offices in both the UAE and Saudi Arabia, and gives you time to investigate late-discovered incidents.

Two things to watch. First, logs contain personal data, so set a defined retention period rather than keeping them for ever. Second, the default audit log retention in Microsoft 365 is shorter than 12 months on many licences, so a full year usually needs a premium audit licence, a retention add-on or a separate log store.

DIFC, ADGM or onshore UAE: which law applies?

Firms in the DIFC follow the DIFC law. Firms in ADGM follow the ADGM Data Protection Regulations 2021. Most businesses onshore and in other free zones fall under the federal Personal Data Protection Law (PDPL). Many groups have entities in more than one, so it pays to build one set of controls to the strictest standard.

Our guide to the UAE data protection law (PDPL) has a side-by-side table of all three, and our guide to AI at work in the DIFC covers Regulation 10.

The bit where we mention ourselves

Cre8 IT supports DIFC and ADGM firms with managed IT and cyber security. We’re ISO 27001:2022 certified, we run 24/7 monitoring, and we set up and evidence the controls in this guide: Microsoft 365 security, device encryption, logging, backups and incident response. We work alongside your Data Protection Officer and lawyers rather than replacing them, and we don’t give legal advice.

Want to know where you stand? Book a free review and we’ll check your systems against this checklist.

Sources and further reading

Written by
CEO, Cre8 IT
Rob Crossley is CEO of Cre8 IT, a Dubai-born managed IT and cyber security company that has supported businesses across the UAE, Saudi Arabia and the UK since 2012. Cre8 IT is certified to ISO 27001:2022 and ISO 9001 and is a certified Microsoft Partner.
FAQ

Frequently asked questions

Does the DIFC data protection law apply if we are not incorporated in the DIFC?

Yes, if you process personal data in the DIFC as part of a stable arrangement. Since the July 2025 amendments the law covers processing in the DIFC regardless of where the controller, processor or sub-processor is incorporated.

How quickly must we report a data breach in the DIFC?

As soon as practicable in the circumstances, to the Commissioner of Data Protection, when the breach compromises someone’s confidentiality, security or privacy (Article 41). If it is likely to result in a high risk to them, you must also tell the affected people (Article 42). There is no fixed number of hours, unlike ADGM’s 72-hour target.

How long do we need to keep audit logs in the DIFC?

The DIFC Data Protection Law does not set a fixed period. It requires you to investigate and report breaches as soon as practicable and to evidence your security, which is hard to do without logs. We recommend keeping security and audit logs for at least 12 months, which matches Saudi Arabia’s NCA controls and PCI DSS, and setting a defined retention period because logs contain personal data.

Do we need a Data Protection Officer in the DIFC?

Not always. Under Article 16 a DPO is mandatory in specific cases, most commonly when you carry out high-risk processing or when the Commissioner directs you to appoint one. DIFC Bodies must always appoint one. Firms with a DPO file an annual assessment with the Commissioner (Article 19).

Can individuals sue us for a data breach in the DIFC?

Yes. Since 15 July 2025 individuals can bring a claim in the DIFC Courts for financial and non-financial damage. Good records, logs and evidence of your security controls are the best way to defend one.

Is Microsoft 365 compliant with the DIFC data protection law?

No tool is compliant on its own. Microsoft 365 has the features you need, such as encryption, audit logs, retention and data loss prevention, but they have to be configured, monitored and evidenced. You also need to know where your data is stored, because transfers outside the DIFC need a documented assessment.

Related guides

Keep reading

Each guide links to the regulator’s own text and shows when it was last reviewed.
UAE data protection

UAE data protection law (PDPL): what it means for your IT, and which law applies to you

UAE data protection law explained for IT: PDPL vs DIFC and ADGM rules, breach reporting, DPOs, security, transfers and what to do while regulations are pending.
5 min read · Reviewed 9 November 2026
AI regulation

AI at work in the DIFC: Regulation 10, Copilot and ChatGPT explained for IT

DIFC Regulation 10 explained: AI notices, the register, high-risk processing and the Autonomous Systems Officer, plus the IT controls for Copilot and ChatGPT.
5 min read · Reviewed 9 November 2026
DFSA

DFSA cyber security and technology risk requirements: what DIFC firms need to evidence

A plain-English guide to the DFSA’s cyber risk rules (GEN 5.5), its outsourcing expectations (GEN 5.3.21) and the evidence a DIFC firm should be able to show.
6 min read · Reviewed 19 September 2026

Is your IT ready for the DIFC Commissioner?

We’ll review your Microsoft 365, devices and logging against the DIFC data protection law and give you a prioritised list of fixes.