IT audit services, Dubai and the UAE

IT Audit and Assessment Services in Dubai

An assessment against a framework, a technical penetration test, and a formal certification are three separate pieces of work with different costs, different durations and different outputs. Buyers routinely ask for one and are sold another, then discover at the deadline that what they hold does not answer the question they were asked. We start by establishing which of the three you actually need, and reasonably often the honest answer is a narrower and cheaper piece of work than the one being proposed elsewhere.

IT audit and compliance assessment for UAE businesses
  • Scope firstBefore anyone quotes
  • In-houseTesting, not subcontracted
  • RetestIncluded, closure evidenced
  • OngoingEvidence kept current
What we actually do

Six audit disciplines, and the difference between them.

These are genuinely different engagements. If a provider quotes the same price and duration regardless of which one you ask for, they have not understood the request.

Framework gap assessment

A structured review of your current state against a named framework, whether ISO 27001, NIST CSF, CIS Controls, DESC ISR or a sector regulation. The output is a gap register with severity, effort and a named owner per gap, plus a costed remediation plan. This is what you need when somebody has told you to comply with something and you do not yet know how far away you are.

Technical testing

Penetration testing and vulnerability assessment against your actual systems. This finds exploitable weaknesses rather than missing documentation, and it answers a completely different question from a framework assessment. Both are often required and they are not substitutes for one another, which is the confusion we most frequently unpick.

Access and privilege review

Who has access to what, who granted it, whether it is still needed, and who signed off the review. The most common finding across every audit we run is access nobody can justify: dormant accounts, standing administrative rights, forgotten guests, and service accounts with more privilege than the task requires.

Cloud and tenant posture review

Microsoft 365 and Azure configuration against benchmark, covering identity, conditional access, data protection, logging and retention. Cloud misconfiguration is now a larger practical exposure than unpatched servers for most UAE mid-market businesses, and it is the area least often audited.

Operational resilience review

Backup verified by an actual restore rather than a green job report, disaster recovery tested against stated objectives, and business continuity arrangements exercised rather than documented. Restore testing is the most commonly faked control in UAE IT, and it is trivially easy to verify.

Evidence production and audit support

Assembling the pack an assessor, bank, insurer or enterprise customer will ask for, and sitting with you through the questions. The distinction that matters is between evidence a control exists and evidence it operated over a period, and it is the second one that assessors want.

Audit and compliance services

Find the engagement you actually need.

Grouped by what is driving the requirement, because that determines the scope far more than the technology does. Pages we hold are linked below. This cluster is expanding, so if your framework is not listed yet, ask and you will get a direct answer rather than a holding page.

Someone has asked us for evidence

A bank running enhanced due diligence, an enterprise customer with a supplier assessment, an insurer at renewal, or an investor in diligence. Usually the most urgent trigger and usually with a deadline attached.

A UAE regulator applies to us

Sector supervision drives the scope and the cadence. Getting the applicability right is the single most valuable early step, because over-scoping wastes a year of budget and under-scoping produces a finding.

We need something tested, not reviewed

A framework assessment tells you whether a control exists. A test tells you whether it holds. Regulated firms usually need both, on a cadence.

We need somebody to own this ongoing

An assessment produces findings. Somebody still has to decide what is accepted, what is funded, and who answers the board and the regulator afterwards.

The underlying controls we assess

An audit finding is only useful if somebody can close it. These are the practice areas we remediate against, which is why our audits do not end at the report.

How we approach audit work

Four things that shape our engagements.

We scope you down when the evidence supports it

The applicability review comes first and it regularly concludes that a narrower obligation applies than the client had been told. That reduces the engagement we could have sold. Over-scoping compliance is a genuine and expensive problem in this market, usually because the vendor scoped the work rather than the regulation.

Testing is ours, so the cadence holds

Vulnerability assessment and penetration testing are delivered in-house rather than subcontracted. When testing is a regulatory cadence rather than a one-off, a missed quarter is a finding regardless of whose diary caused it, and coordinating through a third party introduces delay you do not control.

We close findings, not just list them

The common failure is an excellent report handed over by a consultancy who then leaves. Twelve months later the same findings recur because nobody had the remit or the skills to fix them. We can both identify and remediate, which is why the finding count falls between assessments rather than staying constant.

Evidence maintained continuously

Compliance is an operating state rather than a project. Testing calendars, access reviews, restore tests and policy reviews run on a rhythm and the pack stays current, so a request becomes an export rather than a fortnight of archaeology.

What triggers an audit

Six situations that bring UAE businesses to us.

Bank enhanced due diligence

A banking partner asks for evidence of IT controls as part of a review, usually with a short deadline and no guidance on format. Among the most common triggers we see.

Enterprise customer supplier assessment

A large client sends a security questionnaire and makes the contract conditional on the answers. Frequently the first time a growing business discovers what it cannot evidence.

Tender requiring a framework

A public or corporate tender names ISO 27001 or DESC ISR alignment. The realistic answer is often a documented position with a dated plan rather than full compliance by the deadline.

Cyber insurance renewal

Insurers now ask specific, verifiable questions about MFA coverage, privileged access, EDR and backup immutability, and price on the answers.

After an incident

Something happened, and the board wants independent assurance about what else is exposed. The scope here is usually broader and the timeline shorter.

Investor or acquirer diligence

IT and security diligence during a transaction, where an inability to evidence controls affects valuation rather than merely causing inconvenience.

Three different things

Assessment, test, or certification: which do you actually need?

This table exists because the confusion between these three is the most expensive misunderstanding in the UAE compliance market. Read the row that matches what you were asked for, not what you were quoted.
Gap assessmentTechnical testFormal certification
Answers the questionHow far are we from the standardCan this actually be broken intoCan we prove it to a third party
Typical triggerA regulator or contract names a frameworkA regulator sets a testing cadence, or a customer asksA customer or tender requires the certificate
OutputGap register and costed remediation planFindings by severity, plus a retest letterCertificate from an accredited body
Typical duration2 to 4 weeks1 to 3 weeks per scope6 to 12 months including remediation
Who performs itUsUs, in-houseAn accredited certification body, we prepare you
RepeatsAnnually or on major changeOn the cadence your regime setsSurveillance audits, then recertification
Common mistakeBuying this when a test was asked forBuying the cheapest scope and presenting it as comprehensiveStarting this before the gap assessment
How an audit engagement runs

Four steps, and the first one changes the price.

  1. 1

    Applicability and scoping

    Week 1

    What has actually been asked of you, by whom, in what words, and by when. Which framework genuinely applies at your classification, and what you already hold that transfers. Output is a written applicability statement, and it frequently shrinks the engagement.

  2. 2

    Assessment or testing

    Weeks 2 to 4

    Evidence gathered directly rather than a questionnaire filled in by the client, because self-assessment produces the answers people believe rather than the ones that are true. For technical scopes, testing against the agreed boundary with findings ranked by exploitability and impact.

  3. 3

    Remediation

    Weeks 3 to 12

    Findings closed in severity order with a named owner each, and a retest confirming closure rather than a claim of it. Where a finding will not be closed, it gets a documented risk acceptance signed at the right level, which assessors accept and silence they do not.

  4. 4

    Evidence pack and ongoing rhythm

    Ongoing

    The pack assembled, validated against what the requester actually asked for, and then maintained: testing calendar diarised, access reviews scheduled, restore tests evidenced, policies reviewed annually. The transition from project to operating state is where most programmes quietly fail.

“Our bank gave us three weeks to evidence our IT controls and two firms quoted us for a nine-month ISO 27001 programme, which was not what the bank had asked for. GR read the actual request, told us it was a control questionnaire rather than a certification requirement, ran a two-week assessment, closed the critical items and produced the pack. The bank accepted it. The difference was that somebody read the question first.”
Chief Financial Officer
Finance leadership · Dubai trading group
Bank review passed in three weeks, no certification needed
IT audit FAQ

What UAE businesses ask before commissioning an audit.

Before you commission anything

Twelve questions to settle before an audit is quoted.

Take these to us and to anyone else quoting. The first group determines what you are actually buying. Getting it wrong is how organisations end up holding a report that does not answer the question they were asked.

What are you actually being asked for

  • Who is asking, and can you show us their exact wording?
    The clause matters. "Security assessment" means different things to a bank and a regulator.
  • Is a named framework specified, or is it open?
    A named framework sets the scope. Open wording usually means less work than feared.
  • Is there a deadline, and is it real?
    It changes sequencing entirely. We will tell you honestly if it is not achievable.
  • Do they want an assessment, a test, or a certificate?
    Three different engagements. Ask them directly rather than guessing.

What do you already have

  • Do you hold any current certification?
    ISO 27001 often transfers a substantial proportion of the work to another framework.
  • When was the last technical test, and were findings closed?
    A report with open findings evidences the opposite of what you need.
  • Can you produce access review evidence for the last quarter?
    Not a user list. Evidence somebody reviewed and signed it off.
  • Has a backup restore been performed and documented?
    The single easiest control to verify and the most commonly assumed.

What happens after the report

  • Who will close the findings?
    An audit that produces findings nobody can action is an expensive document.
  • Is a retest included, or quoted separately?
    Closure evidence is usually what the requester actually wants.
  • Will the evidence be maintained, or rebuilt next year?
    Continuous is cheaper than annual reconstruction, and always current.
  • Does the same provider assess and remediate, and is that a conflict?
    Fair question. Ask it of us too, and see the answer in the FAQ below.
Audit scoping

Send us the exact wording of what you have been asked for.

Tell us about the audit purpose, systems, required criteria and intended recipients of the report. We will confirm the requirements and proposed scope with you.