I'll be blunt. In most businesses, a serious security failure is expensive and embarrassing. In a crypto business, it can be the end. Funds move in minutes, transactions can't be reversed, and your customers will read about it on social media before you've finished your first call.

I spent ten years as COO of a Central Bank-regulated business, so I understand why founders can see regulators as a cost. But VARA cybersecurity requirements read like a list of the ways crypto companies actually get hurt. Here's why they matter, and what they ask for.

Does this apply to you?

If you carry out virtual asset activities in or from Dubai, excluding DIFC, you're in VARA's territory under Dubai Law No. 4 of 2022. Firms in DIFC fall under the DFSA, and firms in ADGM under the FSRA. If you're a licence applicant, you'll be asked about these controls before you go live, so they're worth planning for from the start.

What the Technology and Information Rulebook actually asks for

Area What the rulebook expects Why it matters
Leadership A CISO, separate from the Compliance Officer, and a Data Protection Officer Someone senior owns security, and it can’t be an afterthought
Testing Independent VAPT at least yearly and before launching new products, including smart contract audits. Threat-led testing when VARA requires Attackers read your contracts too, as soon as you deploy
Private keys No single point of failure. Quarterly reviews to confirm removed access is really gone Keys are the business. One lost or stolen key can end it
Continuity A business continuity plan, tested at least yearly An exchange that goes down during volatility loses trust quickly
Reporting Material cybersecurity events reported within 72 hours You need to know what is happening and who decides
Personal data Personal data incidents reported to VARA within 24 hours of notifying the relevant parties KYC files are a prime target

Please read the rulebook itself before making decisions, since this is a summary and VARA can update its rules. The VARA rulebook site has the current versions.

Why these rules are good business, not only compliance

Bitcoin coin, representing VARA compliance for Dubai crypto businesses

Picture a growing Dubai exchange. The smart contracts were audited and the wallets are well designed. Then a support agent, who can reset customer security settings, gets a very convincing message and hands over their session. Within an hour, withdrawals are going out of customer accounts.

That's a scenario, but it's a common pattern. Founders tend to worry about exotic attacks on the protocol, when everyday access control is often the easier way in. The rulebook's focus on access reviews exists for a reason.

Banks and partners will look at this

Your banking relationships, institutional clients and liquidity partners all want evidence that you're well run. A credible security programme makes those conversations shorter. A weak one can end them.

Regulators remember how you behaved

From my time in a regulated business, I can tell you that how you handle the bad day matters. If you detect quickly, report on time and show your records, you're in a far better position than a firm scrambling to work out what happened.

Mistakes I'd warn you about

  • Giving your Compliance Officer the CISO role as well. The rulebook separates them.

  • Assuming a part-time arrangement satisfies the CISO rule. A virtual CISO can build and run the programme, but ask VARA how the named role must be held before you rely on it.

  • Testing once, then launching more products. Testing is also expected before new products.

  • Leaving ex-staff on key access. Do the quarterly review, and keep the record.

  • Keeping the incident plan in someone's head. Decide now who calls VARA and when.

Where to start

  1. Map your activities to the rulebooks, including the Technology and Information Rulebook.

  2. Review who can touch keys and customer funds, including support and admin tools.

  3. Book independent testing, including smart contract audits, before your next launch. Our penetration testing team can cover the application and infrastructure side.

  4. Write and rehearse a 72-hour reporting plan. Run it as a tabletop exercise.

  5. Assign the roles and confirm with VARA where there's doubt.

We help crypto businesses with VARA compliance in Dubai. We aren't a licensing consultancy, and we don't give legal advice, so your legal adviser should stay involved. What we do is make the security side real.

Comparing providers? See the Top 10 VARA Cybersecurity Compliance Consultants in Dubai.

See our VARA services or talk to our team.

Frequently asked questions

What are the VARA cybersecurity requirements?

VARA's Technology and Information Rulebook covers areas such as a CISO separate from the Compliance Officer, independent VAPT at least yearly and before new products, private key controls, tested continuity plans and reporting of material cybersecurity events within 72 hours.

Who has to follow VARA's rules?

Firms carrying out virtual asset activities in or from Dubai, excluding DIFC. Firms in DIFC fall under the DFSA, and firms in ADGM under the FSRA.

Does VARA require a CISO?

Yes. The rulebook requires a CISO, separate from the Compliance Officer. A virtual CISO can support the programme, but check with VARA how the named role must be held.

How often does VARA require penetration testing?

Independent vulnerability assessment and penetration testing is expected at least yearly and before new products launch, including smart contract audits. VARA may also require threat-led testing.

How quickly must a cyber incident be reported to VARA?

Material cybersecurity events are generally reported within 72 hours. Personal data incidents have their own rule, reporting to VARA within 24 hours of notifying the relevant parties.