How to choose VAPT services in Dubai
Choose VAPT services in Dubai by first identifying who requires the test. Since 31 July 2024, penetration testing for Dubai government, semi-government and critical infrastructure entities must come from a provider accredited under DESC’s Cyber Force programme. Virtual-asset firms under VARA need independent testing at least yearly. Card-payment environments follow PCI DSS. Customers and ISO 27001 or SOC 2 auditors usually accept any competent manual test with a retest.
In the UAE, the wrong tester can make a good report worthless
Page one for VAPT services in Dubai is a mix of local specialists and cost guides. Few of them start where a UAE buyer should: with the rule or contract that requires the test. That matters more here than in most markets, because some UAE schemes decide who may perform the test, not just what it covers. A thorough report from a provider your regulator does not recognise can still fail the requirement.
So here is the plain position. Radiatus is not accredited under DESC’s Cyber Force programme, is not a CREST member, and has no office, entity or licence in the UAE. That rules us out of formal penetration tests for Dubai government, semi-government and critical-infrastructure entities. It does not rule us out of most private-sector testing: customer security reviews, ISO 27001 and SOC 2 evidence, pre-audit testing, and work for companies whose rules ask for a qualified, independent tester without naming a scheme.
Our testing methods are on our VAPT services page. This page covers the UAE drivers, how remote testing from India works in practice, and what Arabic and right-to-left interfaces add to an application test.
Which rule is driving your penetration test?
Identify the driver before you ask for quotes. The last column is the question most UAE buyers forget to ask.
| Driver | Applies to | What it expects | Can a remote, non-accredited tester satisfy it? |
|---|---|---|---|
| DESC Information Security Regulation and Cyber Force | Dubai government, semi-government and critical information infrastructure entities | Testing under the Dubai ISR; since 31 July 2024, penetration testing and incident response must come from providers accredited under DESC Cyber Force, run with CREST | No. Use an accredited provider |
| UAE Information Assurance standards | Federal government entities and critical sectors under the UAE Cyber Security Council’s framework | Regular vulnerability assessment and penetration testing of critical systems | Often not; check the entity’s own procurement and approval rules |
| VARA Technology and Information Rulebook | Virtual-asset service providers licensed in Dubai | Independent, qualified third-party vulnerability assessment and penetration testing at least yearly and before new systems or products launch | Possibly; the rule asks for qualified and independent testers. Confirm with your compliance officer |
| PCI DSS v4 (requirement 11.4) | Merchants and service providers handling card data | Internal and external penetration tests at least every 12 months and after significant changes, plus segmentation testing | Yes, if the tester is qualified and organisationally independent; your assessor will review the method |
| Financial regulators (Central Bank of the UAE, DFSA, FSRA) | Licensed banks, insurers and financial firms | Testing as set by each regulator’s rules and your licence conditions | Depends on the rule; read it with your compliance team |
| Customer contract or security questionnaire | Any supplier selling to larger organisations | A recent manual test, findings fixed, an attestation letter | Usually yes, unless the contract names a scheme |
| ISO 27001 or SOC 2 audit | Any organisation seeking certification or a report | Evidence of testing and of findings being managed | Yes |
Sources: DESC’s Cyber Force programme with CREST; VARA’s rulebook section on testing and audit; and the UAE Information Assurance Regulation published by the federal government, now overseen through the UAE Cyber Security Council. Rules change; check the current text before you scope, and keep a copy of the clause that applies to you with the test records.
How remote penetration testing from India works for UAE companies
Almost everything internet-facing can be tested remotely, and internal networks can be reached through controlled access. What makes it safe and acceptable is the paperwork and the plumbing:
- Written authorisation. A signed letter naming the systems, the dates, the source addresses and the people involved. For cloud-hosted systems, check your provider’s testing policy too.
- Fixed source addresses. Testing comes from agreed IPs so your monitoring team or managed SOC can recognise it and still spot a real attack.
- Internal access. For internal network or Active Directory testing, a VPN account or a jump host you control, switched off after the window.
- Testing windows in UAE time. India is 1.5 hours ahead, so windows are agreed in Gulf Standard Time around your peak hours and change freezes.
- Data handling. Screenshots and evidence are kept to the minimum needed, stored encrypted and deleted after the agreed period, under a data processing agreement that fits the UAE PDPL or your free-zone rules.
- Emergency contacts. A named person on each side who can stop testing immediately.
Testing Arabic and bilingual applications
Applications built for the UAE often serve Arabic and English users, and that creates test cases a single-language checklist misses:
- Bidirectional text. Right-to-left override characters in names, file names or messages can disguise links and file extensions, or make audit logs misleading.
- Unicode handling. Arabic, Latin and look-alike characters in usernames and email addresses can allow impersonation or duplicate accounts if inputs are not normalised.
- Validation gaps between languages. The Arabic version of a form or app sometimes calls an older API or skips a check that the English version enforces.
- Search and filters. Mixed-script queries can break input handling in search, reporting and export features.
- Generated documents. Invoices, contracts and PDFs rendered in Arabic go through different libraries, with their own injection and access-control risks.
What a VAPT engagement for a UAE company includes
| Scope | Typical focus |
|---|---|
| Web application and API | Authorisation between users and tenants, business logic, authentication, payment and booking flows |
| Mobile apps | Android and iOS builds, local storage, secrets, certificate pinning, deep links and the APIs behind them |
| Cloud accounts | Identity and roles, public exposure, storage permissions, logging, paths to sensitive data in UAE or other regions |
| External network | Internet-facing services, remote access, email security and exposed management interfaces |
| Internal network | Active Directory paths, segmentation between networks, and privilege escalation, through VPN or a jump host |
Reporting for UAE customers, auditors and boards
The same test often has three readers in a UAE organisation, and each needs something different from the report.
- Your engineers need each finding with evidence, steps to reproduce, the affected endpoint or screen in both language versions where relevant, and a fix written for your stack. Findings go straight into your tracker with severity-based target dates.
- Your customers and partners need an attestation letter: what was tested, when, by whom, the method and the fact that high-risk findings were fixed and retested. They should not receive the full report with exploit details.
- Your board, compliance officer or auditor needs the executive summary, the scope statement (including what was deliberately left out and why), the retest results, and how findings are tracked to closure in your risk register.
Ask for all three formats at scoping, not after the test. If your ISO 27001 or SOC 2 programme keeps evidence in a GRC tool, agree the export format too, so the test feeds the audit trail without anyone retyping it. And keep the reports: VARA and PCI DSS both expect testing to be repeated, and the previous report is the baseline the next one is measured against.
What drives the cost of VAPT in Dubai?
We quote a fixed price after scoping and do not publish rates. Effort depends on the number of applications, roles, API endpoints and mobile platforms, cloud accounts and internal network size, testing windows outside normal hours, report language and the number of retests. If an accredited provider is mandatory for your test, the comparison is between accredited firms; our quote is relevant only where the rule allows a qualified independent tester.
Questions to ask any VAPT provider in the UAE
- Does the rule or contract behind this test require a specific accreditation, and do you hold it? Where can we verify it?
- Which named testers will do the work, and how much of it is manual?
- Will you provide a redacted sample report?
- Is the retest of fixed findings included, and for how long?
- How will evidence containing our data be stored and deleted?
- From which IP addresses will you test, and how do you avoid disrupting production?
- Will the report and attestation letter satisfy our customer, auditor or regulator? Have they accepted your reports before?
Typical UAE testing scenarios
Illustrative, not client case studies.
| Organisation | What drives the test | Who should test |
|---|---|---|
| Dubai government department or semi-government company | DESC Information Security Regulation | A DESC Cyber Force accredited provider; not us |
| Free-zone SaaS company selling to banks | Customer security review and ISO 27001 certification | Any qualified independent tester, including us |
| Licensed virtual-asset service provider | VARA rulebook: yearly independent testing and before new products | A qualified, independent tester your compliance officer accepts |
| E-commerce company taking card payments | PCI DSS requirement 11.4 | A qualified, organisationally independent tester; your assessor reviews the method |
| Hotel group launching a booking app | Brand and partner requirements, protection of guest data | Any qualified tester; Arabic and English interfaces in scope |
VAPT services for UAE companies
For private-sector testing where the rule or contract allows a qualified, independent tester.
Application and API penetration test
The problem
A customer, partner or auditor wants evidence that your product has been tested by someone independent.
How we do it
Manual testing of the application and API with accounts for each role, including Arabic and English interfaces, focused on authorisation, business logic and authentication, then a retest of fixes.
What you get
- Manual testing across roles and languages
- Evidence and specific fixes per finding
- Retest of fixed findings
- Report and attestation letter
Mobile app testing
The problem
Your app handles payments, bookings or identity documents for UAE users, and the app is the front door.
How we do it
Android and iOS builds tested together with the APIs behind them: storage, secrets, pinning, deep links, payment and OTP flows.
What you get
- Android and iOS
- Backend API coverage
- Payment and OTP flows
- Developer-ready remediation
Cloud and external network review
The problem
Your estate spans UAE and overseas cloud regions, and nobody has mapped what is exposed or who can reach the data.
How we do it
A review of identities and roles, public exposure, storage, logging and network paths, plus an external test of internet-facing services, with fixes ranked by risk.
What you get
- Identity and exposure review
- External network test
- Attack paths to data
- Prioritised fix list
Pre-assessment testing
The problem
A formal assessment by an accredited provider, or a PCI DSS or VARA review, is coming and you want fewer surprises.
How we do it
We test against the scope of the coming assessment, help your engineers fix what we find and retest, so the formal assessment starts from a cleaner position. We do not replace the accredited provider.
What you get
- Test against the formal scope
- Remediation support
- Retest
- Clear statement of what we are not accredited for
How a remote test for a UAE company runs
Typical for one application and its API. We confirm in the first call whether the rule behind your test allows us to perform it.
Check the driver
Which rule or contract requires the test, and whether it names an accreditation. If it does and we do not hold it, we say so and stop there.
Scope and authorisation
Systems, roles, languages, windows in UAE time, source IPs, data handling and emergency contacts, in writing.
Manual testing
Daily updates and an immediate call for anything critical.
Report, debrief and retest
Findings with evidence and fixes, a debrief with your engineers, a retest of fixes and an attestation letter.
Security platforms in our group
Both are run by us and our group and are used in real testing work.
SemperWise
AI-first cybersecurity: VAPT, pentesting & compliance on SemperWise One™ The group’s AI-first cybersecurity platform for VAPT across web, API, mobile, cloud and network, with findings tracked to closure. Visit semperwise.com
Sentinel — ReconLab
Ethical-hacking command library & live recon lab Our recon lab and ethical-hacking command library, built for authorised testing and used in the reconnaissance stage. Visit sentinel.radiatus.com
GRC Platform
Governance, Risk & Compliance, automated Our GRC Platform keeps risks, controls and test evidence in one place for ISO 27001 and SOC 2 programmes. Visit grc.radiatus.comGuides and related pages
Guides
Glossary
Where we work
Questions about VAPT services in Dubai and the UAE
Since 31 July 2024, penetration testing and incident response for Dubai government, semi-government and critical information infrastructure entities must come from providers accredited under the Dubai Electronic Security Center’s Cyber Force programme, which runs with CREST. Radiatus is not accredited and does not perform these tests.
VARA’s Technology and Information Rulebook requires licensed virtual-asset service providers to have qualified, independent third parties carry out vulnerability assessments and penetration testing at least once a year and before introducing new systems, applications or products. Confirm with your compliance officer which testers your licence conditions accept.
For many private-sector tests, yes: customer reviews, ISO 27001 and SOC 2 evidence, and rules that ask for a qualified independent tester without naming a scheme. For Dubai government and critical-infrastructure entities, or contracts naming DESC, CREST or another scheme, you need a provider holding that accreditation.
At least once a year and after significant changes for most organisations. PCI DSS requires internal and external tests at least every 12 months and after significant changes. VARA requires yearly testing and testing before new products. Products that change often benefit from targeted tests of new features between annual tests.
Yes. We test Arabic and English interfaces, including right-to-left layouts, bidirectional text tricks, Unicode normalisation in usernames and emails, differences in validation between language versions, and Arabic document generation. Reports are written in English.
Internet-facing systems are tested over the internet from agreed source addresses with written authorisation. Internal networks are reached through a VPN account or a jump host you control. Testing windows are set in Gulf Standard Time, and evidence is stored encrypted and deleted after the agreed period.
It depends on scope: applications, roles, API endpoints, mobile platforms, cloud accounts, internal network size, testing hours and retests. We send a fixed quote after scoping and do not publish rates. Where an accredited provider is mandatory, compare accredited firms only.
No. Radiatus has no UAE office, entity or licence. We test remotely from India, 1.5 hours ahead of the UAE, with written authorisation, and visit by agreement when on-site work is genuinely needed.
Not sure which rule your test falls under?
Tell us who is asking for the test and what they named in the request. We will tell you honestly whether we can perform it, and what to look for if we cannot.






Compliance-first delivery