TIME ZONESToronto --:--London --:--Dubai --:--Singapore --:--
Coverage of 50+ jurisdictionsCompliance feedv 2026.10
▸ VARA · Technology Rulebook

Dubai VASPs and the VARA technology rulebook: ready for licensing and review

VARA technology and information rulebook compliance for VASPs starts before the licence is issued: the cybersecurity policy goes to VARA as part of the application. We write that policy from your real systems and set up key and wallet management, the CISO role, the continuity plan and the evidence VARA may ask for at any time.

▸ Cybersecurity
Who it is for
VASPs licensed by VARA or applying
Rules
Technology and Information Rulebook
Version
19 May 2025
Sources
2
Sources checked
2026-10-23
Ask a partner · written reply within 24 hours
Book a paid consultation · USD 99 →

What the VARA technology rulebook covers and who it applies to

The Technology and Information Rulebook applies to every VASP licensed by VARA to carry out virtual asset activity in Dubai and forms part of the Virtual Assets and Related Activities Regulations 2023. Unless stated otherwise, its requirements are binding rules.

The rulebook has three parts: technology governance, controls and security; personal data protection; and confidential information. Schedule 1 is VARA guidance on the risk categories your technology governance and risk assessment framework should cover: organisational, technical, detection and response, customer virtual assets, and digital operational resilience.

It applies alongside the Company Rulebook, the Compliance and Risk Management Rulebook, the Market Conduct Rulebook and the activity-specific rulebooks. Our UAE VASP licensing team handles the application and those parts.

VARA cybersecurity policy for licensing

A VASP submits its cybersecurity policy to VARA for assessment during licensing and afterwards on request, and the CISO reviews it at least annually. Rule I.B.3 sets the minimum content.

Required topics include information security, data classification, access control, systems and network security with code and smart contract validation and audit, development and quality assurance, physical security, vendor management, incident response with root cause analysis, escalation for ransomware attacks, and sharing threat intelligence.

Client transaction controls

The policy sets out how the firm applies multi-factor authentication, or a stronger standard, to transactions above client limits and to transactions after a change of client details such as a wallet address, plus session controls: failed password attempts, time-outs and password validity.

We write the policy from your architecture so every clause can be shown in a configuration.

VARA CISO requirement and key management

A VASP appoints a CISO responsible for compliance with Parts I and III of the rulebook; the CISO must be a separate individual from the compliance officer and may also act as DPO. Keys and wallets are managed so there is no single point of failure.

The CISO must be of good standing and appropriately experienced. Senior management regularly reviews the effectiveness of processes and controls and allocates roles to prevent conflicts of interest. All staff must stay aware of current cyber risks, including those specific to virtual assets.

Keys and seed phrases

  • backups of keys and seed phrases are stored apart from the primary ones;
  • every change of access to keys is logged;
  • when staff with key access leave, the firm assesses whether a new key must be generated;
  • internal audits of access removal run quarterly (rule I.D.2(d)(ii)).

We review how this works in your firm today and document onboarding, offboarding and the granting and revoking of roles in the key management system.

VARA penetration testing and audits: who runs them and when

A VASP engages a qualified and independent third-party auditor for vulnerability assessments and penetration tests at least annually and before introducing new systems, applications and products. Results go to VARA on request.

Where relevant to the business, the scope includes smart contract audits. Evidence of tests and audits is documented and made immediately available to VARA on request (rule I.E.3). Independent auditors also review management processes and regulatory compliance on a regular basis (I.E.4), and VARA can require advanced testing in the form of TLPT (I.E.5).

Our role

An independent party runs the test and the audit, and one can be arranged on request. We prepare the firm: system descriptions and scope, fixes to known weaknesses before testing, taking the findings into the plan, and a re-check of what was closed.

VARA incident notification within 72 hours and the BCDR plan

A VASP reports a material cybersecurity event, or an event that triggers the BCDR plan and materially affects the business, to VARA as soon as reasonably practicable and no later than 72 hours from detection. The BCDR plan is tested and updated every year.

For an incident affecting personal data, the VASP notifies VARA within 24 hours of notifying a data regulator or a data subject (rule II.C.2). The BCDR plan addresses issues specific to virtual assets: network malfunction, loss or corruption of data, key storage.

How we work

  1. A paid 30-minute consultation and a scope letter: systems, dates, fixed price.
  2. Review against Parts I to III of the rulebook; a person checks every finding.
  3. Policy, procedures and BCDR plan built on your systems.
  4. Remediation by us or with your team, then a re-check.
  5. An evidence folder for VARA mapped to the rules.

Key rules of the VARA Technology and Information Rulebook

RequirementWhat it meansSource
Applies to every VASP licensed by VARA; requirements are binding rules unless stated otherwiseCompliance is needed from the first day of the licenceVARA, Technology and Information Rulebook, Introduction
Cybersecurity policy submitted to VARA during licensing and on request; reviewed annually by the CISO (I.B.1–2)The policy is part of the licence packVARA Rulebook, I.B
Appoint a CISO separate from the compliance officer; combining with the DPO role is allowed (I.I.1, II.B.2)A named, experienced person is neededVARA Rulebook, I.I and II.B
No single point of failure in access to virtual assets; quarterly internal audits of key access removal (I.D.2)Key procedures are checked every quarterVARA Rulebook, I.D
Independent third-party auditor: vulnerability assessment and penetration testing annually and before new systems (I.E.1)An independent party tests; VARA receives results on requestVARA Rulebook, I.E.1
BCDR plan implemented, tested and updated annually (I.H.1)A record of a real recovery test is neededVARA Rulebook, I.H
Material cybersecurity event reported to VARA no later than 72 hours from detection (I.K.1)Incident assessment and the report template are ready in advanceVARA Rulebook, I.K
Personal data incident: notify VARA within 24 hours of notifying a data regulator or data subject (II.C.2)Two deadlines for different events, handled in one procedureVARA Rulebook, II.C

What you receive

  • A cybersecurity policy covering the minimum content of rule I.B.3, written from your systems
  • A gap report against Parts I to III of the rulebook with priorities and dates
  • Procedures for key management, access, onboarding and offboarding
  • A BCDR plan, a recovery test record and a VARA notification procedure
  • An evidence folder mapped to the rules, and a re-check

What we need from you

  • A description of the business and architecture: wallets, custody, smart contracts, providers
  • Contacts for the current or future CISO and the technical lead
  • Read access to the agreed systems and logs
  • The licence application material, if the application is still in progress
  • A signed scope letter before any checks start

Boundaries

  • VARA is the regulator, and only VARA decides on the licence and on compliance
  • Penetration tests, smart contract audits and independent audits are run by an independent party; we prepare you and fix what they find
  • Your company approves and submits the policy to VARA, and files incident notifications
  • A legal opinion on compliance with VARA rulebooks comes from a lawyer
  • We give no guarantee on licensing or review outcomes

Risks of VARA readiness done alone, with a chatbot or a freelancer

Alone
The policy is written for the application and drifts from how keys are really stored. VARA can ask for evidence at any time after the licence.
Chatbot
Writes from general ideas about crypto firms and gets the rulebook's specific rules and deadlines wrong, such as the 72-hour and 24-hour limits.
Freelancer
Asks for access to wallets and keys without a scope letter. For a VASP that is a direct risk to client assets.

Frequently asked questions

Sources (checked 2026-10-23)

  1. Technology and Information RulebookVirtual Assets Regulatory Authority (VARA)
  2. Technology and Information Rulebook, 19 May 2025 (PDF)Virtual Assets Regulatory Authority (VARA)
Next step · written reply within 24 hours

Start with one line about your task

One line is enough. A partner reads it and replies in writing within 24 hours.

  • A partner replies in writing within 24 hours
  • A written quote follows your request
  • Nothing is paid before you accept the quote

Or write to hello@innovacg.com

Book a paid consultation · USD 99 →