Activity CZ 231
How to Start a Cyber Security Consultancy Business in Dubai
A security consultancy sells judgement compressed into a document, and fails in two directions at once. What the cyber security advisory line covers, and why most of the work lands on the mainland.
ConsultZone licensing desk
- Activity code
- CZ 231
- Category
- Information Technology
- Reviewed
- Read
- 7 min
Listen instead
52 seconds
An audio summary of this guide.
Topic summary
How to Start a Cyber Security Consultancy Business in Dubai
The product is a document, and it can fail in two directions. Advice that is acted on and turns out to be wrong is the obvious exposure. The commoner one, and the one that quietly kills a practice, is advice that was correct, well argued, read once and shelved — because the consultant wrote for a reader who could not authorise anything. A security consultancy is therefore not really in the business of knowing things. It is in the business of putting what it knows in front of the one person able to act, in a form that survives being disagreed with.
That is what separates a good report from a competent one. Finding the gap is technical work and most capable practitioners can do it. Writing it so that a chief financial officer understands why it matters, a technology lead cannot dismiss it as theatre, and a lawyer can see what was recommended and when, is the part clients pay a premium for and the part that is hardest to hire.
What the activity actually covers, and the line it draws at advising
Cyber Security Consultancy covers advisory work on the security of a client's systems, data and people: assessing an existing environment, designing an architecture or an access model, writing the policies and the response plan, reviewing a supplier or an acquisition target, testing defences with the owner's authority, advising during and after an incident, and training staff to recognise what reaches them.
The constraint on all of it is in the word consultancy. A consultancy licence is permission to advise, and several of the things a security firm is asked to do next are regulated when performed rather than when advised on. Advising a client on which network equipment suits his site is advice; operating a public network or selling connectivity is a separately licensed undertaking in the federal telecoms regulator's remit. Recommending how a client should handle a compromised mailbox is advice; reaching into a third party's systems is not something a trade licence confers on anybody.
Testing a system is a contractual gate, not a licensing one, and it is the sharpest edge on the page
Offensive testing deserves its own paragraph because the risk is misread so often. The authority to probe a system comes from the party that owns it, in writing, scoped and dated — not from an activity recorded on a licence. A practice testing a client's cloud tenancy is frequently also touching infrastructure belonging to a hosting provider who has not agreed to anything, and consent from the client does not extend to the client's suppliers. Any practice intending to offer this work builds its authorisation paperwork before its tooling, and declines engagements where the scope cannot be bounded on paper. The sentence a client least wants to read is that the test was lawful but out of scope.
Discretion is the marketing problem nobody plans for
A consultancy is handed the client's worst secrets in the first week, and is bought substantially on the confidence that they go no further. The commercial consequence is awkward: the better the engagement, the less likely the client is to be named. No company wants to be the reference that proves it needed help, so the ordinary machinery of professional-services marketing is unavailable here.
What works instead is a referral channel of people who meet the problem before the client does — insurance brokers placing a policy, lawyers handling a contract dispute, auditors who found something they cannot evaluate, and larger consultancies that need a specialist for one workstream. Building those relationships is slower than publishing case studies and it is the only route this line reliably has.

The client arrives after an event, not on a schedule
Almost nobody buys security consultancy because the calendar said so. The buyer arrives because something happened: an incident, a near miss at a competitor, a failed supplier assessment that cost a contract, an acquisition where somebody has to look inside the target, a new market with rules the client has not met before, or a new technology lead who will not sign for what he inherited.
Where the client has a chief information security officer, he is the buyer and the conversation is technical and fast. Where there is no such role — which is most mid-sized companies — the buyer is the owner or the managing director, the conversation is about consequence rather than architecture, and the sale is decided by whether the consultant can explain the exposure without jargon.
Event-driven demand makes the pipeline lumpy, and that is the thing to engineer against
Project fees staged on deliverables are good revenue and bad cash rhythm, because the work arrives when other people's bad weeks arrive. Two responses are standard and both are worth putting in place early. The first is a fixed-scope assessment sold at a published shape, so a hesitant buyer has something small to say yes to. The second is a standing arrangement for incident support — capacity reserved, a known rate, an agreed first hour — which a client buys precisely because he cannot predict the day he needs it.
The adjacent activity is cyber risk management, CZ 230, and the boundary is worth stating from this side. That line runs continuously, reports upward to people who will authorise rather than implement, and is renewed because governance requires a current position. This one is commissioned at a decision point, finishes, and is judged on whether somebody did the thing it recommended. A practice that sells the second as though it were the first ends up with a retainer it cannot fill.
Where the licence sits, and why most of this work lands on the mainland
The trade licence with the activity recorded on it comes from the economic department of the emirate. The structural choice is the ordinary one — mainland or free zone — and for advisory work it is decided less by cost than by who the clients are and where the advice is delivered.
six kinds of client, two destinations
- UAE companies advised at their own premisesThe work is performed for local clients on local soil
- Government and semi-government buyersPublic procurement generally contracts with mainland suppliers
- A client's supervised subsidiary needing an assessment in its own nameThe supervised entity sits in the local market whatever the adviser's address
- Formal training delivered to a client's staffDelivered in person here, and structured training can attract an education-side approval of its own
Mainland licence
- Clients inside one free zone, advised within itThe zone is both the market and the address
- Overseas clients advised from a UAE deskNothing is being sold into the local market
Free zone licence
Four of the six land on the mainland, which is the practical answer for most new practices: the clients are UAE companies, the advice is delivered at their offices, and the public sector is a buyer worth keeping reachable. A free zone licence can hold the activity and suits a practice whose clients sit inside its own zone or outside the country. What a given licence permits, and to whom, is settled by the authority issuing it rather than assumed from the activity name, and whether the line is cut as a professional or a commercial licence changes the shareholding question rather than the work.
One condition is contractual rather than procedural and belongs in the first engagement letter: what the practice may see, what it may keep, how long it keeps it, who inside the client may be told, and what happens to the material at the end. A consultancy holding another company's vulnerabilities is holding something with a market value to somebody else, and the file showing how it was handled protects the practice as much as the client.
What the licence costs to hold, which form it takes, what the premises must satisfy and what additional standing is needed for the work this line excludes all depend on the emirate and the licensing authority. ConsultZone establishes those for the specific practice before anything is applied for.
References
- Telecommunications and Digital Government Regulatory Authority — type approval for telecoms and radio apparatus, and the boundary between advising on a network and operating one. TDRA
- Ministry of Economy — intellectual property and company matters, which is where a practice's own methodology and tooling are protected. Ministry of Economy
- UAE Government portal — federal law and national strategy, including the UAE's position on personal data and on lawful access to systems. UAE Government portal
- Knowledge and Human Development Authority — education and training providers in Dubai, which is the approval structured staff training can attract. KHDA
- Federal Tax Authority — VAT and corporate tax enrolment on project and retainer fee income. Federal Tax Authority
- Ministry of Human Resources and Emiratisation — work permits and labour contracts for consultants and testers. MoHRE
Elsewhere in Information Technology
Activities that sit beside this one
Most licences carry more than one activity. Adding a neighbouring line at the application stage costs a fraction of amending the licence afterwards.
Begin with a clear conversation
Tell us what you intend to build.
A consultant will map the structure, jurisdiction, approvals and likely cost against what you actually described — not against a package.