On 17 November 2026, Dubai International Financial Centre announced that it is the first financial centre to be certified against ISO/IEC 42001:2023, the international standard for AI management systems. According to DIFC, the certificate covers all three recognised scopes, AI User, AI Producer and AI Provider, and followed an independent third-party audit.
The word that matters for every other organisation is "scope". ISO/IEC 42001 certifies how an organisation governs AI. It does not certify a model or a product. Before an auditor looks at a single control, you decide which of your AI activities the management system covers. That decision starts with the role you play.
Three roles, three sets of evidence
DIFC describes its own roles in plain terms: it uses AI in its operations, it builds AI-enabled tools and platforms, and it provides AI services and infrastructure to others. Most organisations hold at least one of these roles, and many hold two.
- User. You use AI products or services built by someone else. Evidence centres on approved tools, acceptable use, supplier checks and staff training.
- Producer. You design, build, test or deploy products that use AI, even one internal agent. Evidence centres on data, testing, change control and human oversight.
- Provider. You make AI-enabled products or services available to others. Evidence centres on what you tell customers, how you support them and how you handle incidents.
Where scope goes wrong
- Too narrow. The certificate covers one team or one tool, and it does not answer what clients and regulators ask about the rest.
- Too wide. The audit takes in systems you do not run, and the evidence takes months longer to collect.
- Wrong role. A firm that builds one internal agent on a bought model is a producer for that agent as well as a user. It is an easy gap to leave.
Build a one-page inventory
You cannot choose a scope for systems you have not listed. One page with five columns is enough to start.
- System. Each AI tool, model or agent in use, including those staff adopted on their own.
- Role. User, producer or provider, one per row.
- Owner. One named person who answers for it.
- Data. What it reads and writes, and where that data sits.
- Impact. Who is affected if it is wrong, on a scale of 1 to 3.
Make three decisions before the audit
- Which roles. Start with the roles clients or regulators ask about first.
- Which units. Name the business units and locations inside the boundary.
- Which date. Set a target audit date and work back from it in 30-day steps.
Reuse the evidence
The inventory and the controls behind it serve more than one framework. The same evidence base supports ISO/IEC 42001, DIFC Regulation 10, the EU AI Act and the NIST AI RMF, as we set out in build once, certify many.
A plan for the first 30 days
- Week 1. List every AI system in use, including tools nobody approved.
- Week 2. Tag each system with a role and a named owner.
- Week 3. Draft the scope statement: roles, units and locations.
- Week 4. Compare current controls with the standard and list the gaps by owner.
