Insights · New DIFC firms

Setting up IT for a new DIFC firm: what the DFSA expects before you go live

Getting a DFSA licence is mostly about your business plan, people and capital, but your technology is part of the systems and controls the regulator expects you to run from day one. This guide sets out what to put in place, in what order, and the gaps the DFSA has highlighted in newly authorised firms. See also our IT support for DIFC firms.
The short answer

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.

Key points
  • GEN 5.5 covers governance, third-party risk, access, patching, encryption, monitoring, testing and incident response.
  • Material cyber incidents must be reported to the DFSA within 72 hours at the latest (GEN 5.5.19).
  • The DFSA has flagged over-reliance on group entities and outsourced providers, and SLAs that don’t define responsibilities, as common weaknesses in new firms.
  • Business continuity plans must be tested, not just written.
  • Records must be kept for at least six years, and the DIFC Data Protection Law applies to the personal data you hold.

Who this guide is for

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.

What the DFSA looks at on technology

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:

AreaRuleWhat it means for IT
Systems and controlsGEN 5.3Controls that let you manage the business effectively and responsibly, with breaches identified and acted on.
Cyber risk managementGEN 5.5A framework approved by your governing body, covering risk assessment, third parties, access, patching, encryption, monitoring, testing and incident response.
Third parties and outsourcingGEN 5.3 and 5.5.3Due diligence on providers, including group companies, and contracts that set out who does what. Material outsourcing must be notified to the DFSA.
Incident reportingGEN 5.5.19Material cyber incidents reported as soon as reasonably practicable and within 72 hours at the latest.
Business continuityGEN 5.3A continuity plan that has actually been tested.
RecordsGEN 5.3Policies, 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.

Your IT go-live checklist

Aim to have these in place, and evidenced, before you start operating:

  1. Microsoft 365 (or Google Workspace) set up in the firm’s own name, with multi-factor authentication for everyone and admin accounts kept separate.
  2. Company laptops and phones managed centrally, encrypted, patched automatically and able to be wiped remotely.
  3. Email security: SPF, DKIM and DMARC on your domain, plus phishing and impersonation protection.
  4. A cyber risk management framework and information security policy, approved by your governing body.
  5. An asset register: devices, systems, cloud services and who owns each.
  6. Joiner, mover and leaver procedures, with access reviewed regularly.
  7. Backups of servers and Microsoft 365, with a restore test you can show.
  8. A business continuity and disaster recovery plan that has been tested.
  9. An incident response plan that names who decides whether an incident is material and how the DFSA is told within 72 hours.
  10. Logging switched on and kept long enough to investigate, with records retained for at least six years.
  11. Due diligence and a written agreement with every IT provider, including your group, that defines responsibilities.
  12. Data protection notification with the DIFC Commissioner of Data Protection, and short security awareness training for all staff.

Using your group's IT: what to watch

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.

Gaps the DFSA has seen in new firms

In its 2025 engagement sessions for newly authorised firms, the DFSA highlighted these weaknesses. Each has an IT side:

Weakness flaggedHow to avoid it
Over-reliance on group entities and outsourced providersKeep oversight in the DIFC firm: a named owner, regular reporting and the right to audit.
SLAs that don’t define responsibilitiesSpell out who handles security monitoring, patching, backups and incident notification.
Business continuity plan not testedRun a restore test and a short tabletop exercise before go-live, then yearly.
Inadequate record keepingRetention policies in Microsoft 365, and decisions and policies stored where they can be found.
Policies not tailored to the businessWrite policies around how your firm actually works, not a generic template.

A practical timeline

WhenIT tasks
While preparing the applicationChoose your IT approach (own, group or managed provider), draft the cyber risk framework and policies, and map providers.
Before go-liveSet up Microsoft 365, devices, email security, backups and logging; sign provider agreements; test continuity and incident response; train staff.
First 90 daysReview access, check backups and alerts are working, and fix anything found during set-up.
Every yearRefresh the risk assessment, test continuity and incident response again, review providers and run a penetration test or vulnerability assessment.

The bit where we mention ourselves

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.

Sources and further reading

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.

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 our IT provider need to be based in the DIFC?

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.

How quickly must a DFSA-authorised firm report a cyber incident?

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).

How long must a DIFC firm keep records?

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.

Can a new DIFC firm use its parent company's IT?

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.

When should we start on IT for a new DIFC firm?

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.

Related guides

Keep reading

Each guide links to the regulator’s own text and shows when it was last reviewed.
DFSA cyber rules

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
Outsourcing

IT vendor and outsourcing management for DFSA and FSRA firms

How to manage IT providers when you are regulated in DIFC or ADGM: a register, tiering, due diligence, contract terms and ongoing oversight.
4 min read · Reviewed 19 September 2026
DIFC data protection

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

DIFC data protection law (DIFC Law No. 5 of 2020) explained for IT: the 2025 amendments, breach reporting, DPO rules, transfers and a 12-point checklist.
7 min read · Reviewed 9 November 2026

Setting up a new DIFC firm?

Tell us your timeline and we’ll plan your IT, security and evidence so you’re ready to go live.