Framework overlap

Does API 1164 cover UAE Virtual Asset Regulatory Authority (VARA) Regulations?

You hold API 1164 and have been told to do UAE Virtual Asset Regulatory Authority (VARA) Regulations. Here is how much overlaps, control by control.

20% of UAE Virtual Asset Regulatory Authority (VARA) Regulations you already have

API 1164 already covers about 20% of UAE Virtual Asset Regulatory Authority (VARA) Regulations, leaving 4 of 5 controls as genuinely new work.

Already covered 1 Likely covered 0 New work 4

What is genuinely new work

Nothing in API 1164 reaches these. This is the list to scope.

UAEVARA-2
Market Conduct, Customer Protection, Marketing Rules
UAEVARA-3
AML/CFT and FATF Travel Rule
UAEVARA-4
Technology Risk and Cybersecurity
UAEVARA-5
Reporting, Governance, Enforcement
Show the 1 you already have
UAEVARA-1
Activity Licensing (Advisory, Exchange, Custody, Broker-Dealer, etc.)

How this is calculated

Already covered means a mapping runs from a control in API 1164 to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition