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.
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.
DIFC Amendment Law No. 1 of 2025 came into force on 15 July 2025. The changes that matter most for IT are:
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.
| Duty | What the law expects | What it means for your IT |
|---|---|---|
| Know your data | Records of processing, and notifying the Commissioner of what you process | A data map: where personal data lives (mailboxes, SharePoint, CRM, file shares, backups, personal devices) and who can reach it |
| Keep it secure | Appropriate 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 breaches | Notify 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 rights | Access, correction, erasure, portability and objection, among others | Being able to find and export one person’s data across email, files and systems, plus retention rules |
| Control transfers | A lawful basis for transfers outside the DIFC (Articles 26 and 27), now with a documented assessment | Knowing which country each cloud service stores data in, and a supplier list with locations and contract terms |
| Assess high-risk processing | A data protection impact assessment before high-risk processing | System diagrams, the controls in place and the remaining risk, supplied by IT |
| Appoint a DPO where required | A 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 |
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?
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.
| Rule | What it says about logs |
|---|---|
| DIFC Data Protection Law | No 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 2021 | No 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.
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.
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.
Last reviewed 9 November 2026. This guide explains the IT side of the law and is not legal advice. Check the current position with the regulator or your legal adviser.
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.
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.
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.
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).
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.
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.
