← All insights
UAE & Gulf

The Gulf is tightening. Are firms ready or just compliant?

Mubarak Ahmed, Founder February 2026

The DIFC and ADGM have raised supervisory intensity since the UAE came off the FATF grey list in early 2024. Firms that built their compliance frameworks during the previous environment are running standards that no longer match what their regulators expect. Retrofitted compliance is rarely as defensible as compliance built from the ground up.

In February 2024, the UAE was removed from the FATF grey list after two years of enhanced monitoring. It was a significant moment, not just symbolically but structurally. The conditions for removal required the UAE to demonstrate that it had addressed the technical deficiencies that landed it on the list in the first place: weak beneficial ownership frameworks, inconsistent supervision of designated non-financial businesses, and inadequate risk-based approaches to AML supervision across its financial free zones.

The DFSA and the FSRA at ADGM did not wait for the grey list designation to start moving. Both regulators had been tightening their expectations well before February 2024, and they have continued to tighten them since. The question for firms operating in or from DIFC and ADGM is not whether the regulatory environment has changed. It clearly has. The question is whether their compliance functions have changed with it, or whether they are operating on frameworks that were built for the regulatory environment of five years ago.

The regulatory shift across the GCC has a particular character. It is not a single reform or a new rulebook. It is a cumulative tightening across multiple dimensions simultaneously: enhanced CDD requirements, more prescriptive source of wealth and source of funds expectations, closer alignment with FATF standards on beneficial ownership, and a materially different supervisory posture from the DFSA and FSRA in terms of willingness to ask hard questions and follow up on the answers.

DIFC in particular has moved from a principles-heavy approach, where firms had significant latitude to design their own frameworks, toward something closer to the FCA's output-focused model. The regulator is less interested in whether you have a policy and more interested in whether the policy produces defensible decisions. That is a meaningful shift for firms whose compliance infrastructure was designed around demonstrating process rather than demonstrating outcome.

ADGM has followed a similar trajectory, with the FSRA publishing increasingly detailed expectations around CDD, risk classification, and ongoing monitoring. For wealth managers and asset managers operating within ADGM, the gap between what a compliant CDD process looked like in 2020 and what a defensible one looks like in 2026 is significant.

The honest answer to whether this is good is: it depends on how the adjustment is made. The direction of travel is clearly right. A regulatory environment that demands defensible decisions, proper beneficial ownership verification, and genuine risk-based differentiation rather than checkbox compliance is a better environment for legitimate business than one that allows weak frameworks to persist. That is not in question.

What is in question is whether the firms being asked to meet these standards are making genuine structural changes or whether they are retrofitting. Retrofitted compliance has a particular shape. It produces updated policies, new form templates, revised risk appetite statements, and a training record showing that everyone attended the refreshed AML session. What it does not always produce is the underlying infrastructure change that makes those policies real: the workflow that actually captures the beneficial ownership chain, the risk rating process that actually differentiates between clients rather than defaulting to medium, the ongoing monitoring framework that actually catches the trigger events that should prompt a review.

The firms that will hold up under DFSA or FSRA scrutiny are the ones that built their compliance functions around the question of how a decision would be defended, not around the question of how an audit would be passed. Those are different design questions and they produce different systems.

For wealth managers and independent asset managers operating across the GCC, the specific pressure points are consistent. Source of wealth verification remains the area where the gap between policy and practice is widest. The policy says verify. The practice, in many cases, is to accept a narrative without corroborating it. That is not verification. It is documentation that the question was asked.

Beneficial ownership is the second consistent pressure point. Cross-border structures, family holding companies, and trust arrangements are common features of the GCC client base, and each one creates complexity that a standard onboarding form was not designed to handle. Firms that have not invested in a structured process for mapping and verifying these structures will find that their files look complete at the surface and do not hold up one level below.

Ongoing monitoring is the third. The grey list period put significant pressure on firms to improve their onboarding. The monitoring that happens after onboarding received less attention, and the gap is visible. Periodic reviews that happen because the calendar says so rather than because something changed are not what the DFSA or FSRA are looking for. A trigger-based approach to ongoing monitoring, which is what both regulators increasingly expect, requires a different kind of infrastructure.

The Gulf tightening is real and it is continuing. Verigrade Gulf was built specifically for this environment, with six jurisdiction-specific regulatory content bundles covering DIFC, ADGM, SAMA, CBK, QCB, and QFCRA. The methodology reflects what these regulators are actually looking for, not what compliance looked like before the grey list.

Whether individual firms are ready depends less on the quality of their policy documents and more on whether the decisions being made every day in their compliance function are the kind that can be explained when someone asks how they were reached. That is the standard the regulators are moving toward. The firms that are there already have a structural advantage over the ones still closing the gap.

Verigrade Gulf

Compliance built for the Gulf, not retrofitted.

Verigrade Gulf is a CDD risk engine purpose-built for DIFC, ADGM, SAMA, CBK, QCB, and QFCRA. One codebase, six regulatory content bundles, jurisdiction-aware methodology.

Request a Verigrade Gulf demo ← All insights