A DFSA-authorised firm must run adequate systems and controls (GEN 5.3) and a cyber risk management framework (GEN 5.5) from the day it starts operating. In practice that means: Microsoft 365 and devices set up securely in the firm’s own name, a framework approved by your governing body, due diligence and clear contracts with any IT provider (including your group), tested backup and business continuity, an incident response plan that can meet the DFSA’s 72-hour notification deadline, and records kept for at least six years. Plan it alongside your application, not after approval.
Firms applying for DFSA authorisation to operate in or from the DIFC, including start-ups coming through the DIFC Innovation Hub or the DFSA’s Innovation Testing Licence, and international firms opening a DIFC branch or subsidiary.
If your DIFC entity isn’t DFSA-authorised, for example a single family office or a non-financial company, the DFSA’s cyber rules won’t apply to it directly. The DIFC Data Protection Law still does, so most of this checklist is still good practice.
There isn’t a separate IT licence. Technology sits inside the general systems and controls rules, and the DFSA expects them to be proportionate to the size and complexity of your business. These are the areas that matter most for IT:
| Area | Rule | What it means for IT |
|---|---|---|
| Systems and controls | GEN 5.3 | Controls that let you manage the business effectively and responsibly, with breaches identified and acted on. |
| Cyber risk management | GEN 5.5 | A framework approved by your governing body, covering risk assessment, third parties, access, patching, encryption, monitoring, testing and incident response. |
| Third parties and outsourcing | GEN 5.3 and 5.5.3 | Due diligence on providers, including group companies, and contracts that set out who does what. Material outsourcing must be notified to the DFSA. |
| Incident reporting | GEN 5.5.19 | Material cyber incidents reported as soon as reasonably practicable and within 72 hours at the latest. |
| Business continuity | GEN 5.3 | A continuity plan that has actually been tested. |
| Records | GEN 5.3 | Policies, procedures, key discussions and decisions kept for at least six years. |
For the detail on each GEN 5.5 area, see our guide to DFSA cyber risk management requirements.
Aim to have these in place, and evidenced, before you start operating:
Many new DIFC firms start on their parent company’s systems. That can work, but the DFSA has listed over-reliance on group entities and outsourced providers, and service agreements that don’t define who is responsible for what, among the common weaknesses in newly authorised firms.
If you rely on group IT, document it like any other outsourcing: what the group provides, the service levels, how incidents reach the DIFC firm in time to meet the 72-hour deadline, who can access your data, and how you would exit. Make sure someone in the DIFC firm understands the set-up and can answer the regulator’s questions about it.
In its 2025 engagement sessions for newly authorised firms, the DFSA highlighted these weaknesses. Each has an IT side:
| Weakness flagged | How to avoid it |
|---|---|
| Over-reliance on group entities and outsourced providers | Keep oversight in the DIFC firm: a named owner, regular reporting and the right to audit. |
| SLAs that don’t define responsibilities | Spell out who handles security monitoring, patching, backups and incident notification. |
| Business continuity plan not tested | Run a restore test and a short tabletop exercise before go-live, then yearly. |
| Inadequate record keeping | Retention policies in Microsoft 365, and decisions and policies stored where they can be found. |
| Policies not tailored to the business | Write policies around how your firm actually works, not a generic template. |
| When | IT tasks |
|---|---|
| While preparing the application | Choose your IT approach (own, group or managed provider), draft the cyber risk framework and policies, and map providers. |
| Before go-live | Set up Microsoft 365, devices, email security, backups and logging; sign provider agreements; test continuity and incident response; train staff. |
| First 90 days | Review access, check backups and alerts are working, and fix anything found during set-up. |
| Every year | Refresh the risk assessment, test continuity and incident response again, review providers and run a penetration test or vulnerability assessment. |
Cre8 IT sets up and runs IT for DIFC and ADGM regulated firms, from day one. We’re ISO 27001:2022 certified, we run 24/7 monitoring, and we put the controls in this guide in place with the evidence to show the regulator: Microsoft 365 security, managed devices, backups, logging and incident response. We work alongside your compliance adviser; we don’t give legal or regulatory advice.
Setting up a new DIFC firm? Talk to us early and we’ll make sure your IT is ready when you are.
Last reviewed 16 November 2026. This guide explains the IT side of the DFSA’s rules and is not legal or regulatory advice. Check the current Rulebook and confirm your obligations with your compliance adviser.
No. What matters is that you’ve done due diligence on the provider, have a contract that sets out responsibilities and incident notification, and keep oversight of the service. Cre8 IT’s Dubai office is in Jumeirah Lake Towers.
As soon as reasonably practicable, and in any event within 72 hours of becoming aware of a material cyber incident, using the form on the DFSA electronic portal (GEN 5.5.19).
The DFSA expects records of policies, procedures, key discussions and decisions to be kept for at least six years. Make sure your email and file retention settings match.
Yes, but treat it as outsourcing: carry out due diligence, agree service levels and responsibilities in writing, and make sure incidents reach the DIFC firm fast enough to meet the DFSA’s 72-hour deadline.
While you’re preparing your application. Choosing providers, drafting the cyber risk framework and setting up Microsoft 365 and devices takes weeks, and it’s much easier to build it right than to fix it after approval.
