Buyer guide C of 7
UAE Penetration Testing Requirements by Regulation
Few UAE rules name penetration testing outright. PCI DSS Requirement 11.4 does, for entities handling card data. The Dubai Cyber Force programme sets who may supply penetration testing and incident response to Dubai government bodies. The UAE IA Regulation, PDPL, DIFC and ADGM data protection rules set general security duties. Read each source's full text before you treat a rule as a testing requirement.
Last updated: November 2026
Requirement map: framework, scope and testing implication
"No explicit pentest clause found" means the primary page we reviewed does not mention penetration testing. It does not prove the full regulation lacks one. Status as reviewed in November 2026.
How to read a regulation for testing clauses: look for the words penetration test, vulnerability assessment, security testing, technical assessment and independent assessment, then read the surrounding control. Note who must perform the test, how often, and what evidence must be kept. A clause that says "regularly test" without a frequency leaves the interval to your own risk assessment, which you should document.
Explicit testing clause
- PCI DSS v4.0.1, Req. 11.4
Rule on who may test
- Dubai Cyber Force programme
General security duty, no testing clause found
- UAE IA Regulation
- UAE PDPL
- DIFC and ADGM data protection
Text not public or not verified
- DESC ISR
- CBUAE
- VARA
| Framework | Applies to | Testing implication | Primary source |
|---|---|---|---|
| Dubai Cyber Force programme (DESC with CREST) | Providers of penetration testing and incident response to Dubai government, semi-government and critical information infrastructure | The programme assures penetration testing and incident response services. A provider needs a current UAE trade licence that includes cyber security activities, CREST accreditation, and consultants who can obtain a Dubai Police clearance certificate. A CREST page from July 2024 says Dubai government, semi-government and critical information infrastructure entities must buy these services from Cyber Force certified companies. Another CREST page still calls the programme expected to become mandatory from 31 July 2024, so the two pages differ on the date; confirm with DESC. | CREST: Dubai Cyber Force and CREST: certified companies |
| DESC Information Security Regulation (ISR) | Entities within DESC's remit | DESC lists the ISR among documents available on request, and its homepage does not state scope or version. Request the current text from DESC and read its testing and assessment controls. | DESC |
| UAE Information Assurance (IA) Regulation | Entities that TDRA designates as critical under the UAE CIIP Policy | The portal describes management and technical information security controls and does not list specific controls. No explicit pentest clause found on the portal page; read the full regulation. | UAE Government portal: IA Regulation |
| UAE PDPL (Federal Decree-Law 45 of 2021) | Processing of personal data in or outside the country | In force since 2 January 2022. The portal describes general duties to secure personal data and does not describe specific technical measures. No explicit pentest clause found on the portal page. The UAE Data Office is the federal regulator. | UAE Government portal: data protection laws |
| DIFC data protection (DIFC Law No. 5 of 2020) and ADGM Data Protection Regulations 2021 | Firms operating in the Dubai International Financial Centre and Abu Dhabi Global Market | Each free zone runs its own regime, with its own regulator. Both set security-of-processing duties. The UAE portal lists the DIFC law, and the ADGM regulations are published by ADGM's Office of Data Protection. Check the security provisions of the regime that applies to you. | UAE Government portal: data protection laws |
| PCI DSS v4.0.1, Requirement 11.4 | Entities that store, process or transmit payment card data | Explicit. Requirement 11.4 calls for internal and external penetration testing at least once every 12 months and after significant change, segmentation testing, and retesting of exploitable findings. | PCI Security Standards Council: document library |
| CBUAE requirements for licensed financial institutions | Banks, finance companies and other CBUAE-licensed firms | No explicit pentest clause verified in the primary pages reviewed. Ask your CBUAE supervisor or read the current CBUAE rulebook for technology and operational risk requirements. | CBUAE Rulebook |
| VARA virtual asset regulation | Virtual asset service providers in Dubai, outside the DIFC | VARA is the sole authority for virtual assets in Dubai's free zones and mainland except the DIFC and publishes a register of licensed providers. The pages reviewed do not set out technical security controls. No explicit pentest clause found; read the VARA rulebook. | VARA |
Who is triggered
Match your company type to the likely testing driver. Then confirm in the source.
- Dubai government supplier or critical infrastructure operator. Check the Dubai Cyber Force programme and the DESC ISR. If you buy penetration testing or incident response for a Dubai government entity, verify the provider is registered.
- Card-data processor, merchant or service provider. PCI DSS Requirement 11.4 applies, with annual and change-based penetration testing.
- Bank or fintech. Check CBUAE rules and your supervisor's technology risk requirements. Card products bring PCI DSS in as well.
- Virtual asset firm. Check the VARA rulebook for your licence category. Guide G covers testing and forensics for these firms.
- Free zone firm in the DIFC or ADGM. Read the security provisions of the free zone's data protection regime.
- Data-heavy SME outside these groups. The PDPL sets a general duty to secure personal data. A penetration test is a practical way to evidence that duty, even where no clause names it.
A practical sequence for a buyer: identify the regimes that apply to your licence, sector and contracts; list each testing-related clause with its frequency and evidence requirement; scope one test programme that satisfies the strictest of them; then keep one set of reports and retest letters that you can show to every assessor.
Evidence an auditor expects from a test report
Auditors look for proof that the test was scoped, performed and followed up. A report should show:
- the scope, dates and test type, such as internal, external or application;
- the methodology followed;
- each finding with severity, a CVSS score and proof of concept;
- the remediation steps and the retest result showing which findings were closed;
- who performed the test and their independence from the team that built the system.
Common reasons a test report fails to satisfy an assessor: the scope does not match the in-scope environment, the report lists tool output with no exploitation, findings have no severity or proof of concept, no retest shows closure, or the tester was not independent of the team that built the system.
Keep the signed scope and rules of engagement with the report. Auditors often ask for them together.
Next step
Once you know which rule applies, compare providers on testing scope, report contents and accreditation. The ranking of offensive security companies in the UAE lists ten providers by tier with stated accreditations.
Frequently asked questions
Does UAE law require every company to run penetration tests?
No source reviewed sets a blanket requirement. PCI DSS Requirement 11.4 requires testing for entities handling card data, and the Dubai Cyber Force programme governs providers to Dubai government bodies. The PDPL, the UAE IA Regulation and free zone regimes set general security duties. Your sector regulator, contracts and customers may add requirements, so check each one.
Do I need a Dubai Cyber Force provider for private-sector work?
CREST describes the programme as covering penetration testing and incident response for Dubai government, semi-government and critical information infrastructure entities, and says those entities must use certified providers. Private-sector buyers outside those groups are not described as covered. A private buyer may still choose a registered provider as a quality signal. Confirm current status and scope with DESC.
Is PCI DSS penetration testing different from a normal pentest?
The method is similar, but the scope is defined by the cardholder data environment. Requirement 11.4 calls for internal and external testing at least annually and after significant change, plus segmentation testing. The report should show scope, method, findings, and retest of any exploitable finding, so an assessor can follow the evidence.
How often should penetration tests be repeated?
Where a rule sets a frequency, follow it. PCI DSS sets at least every 12 months and after significant change. For other organisations the sources reviewed set no fixed interval. A sensible trigger is each major release, infrastructure change or new integration, plus a periodic baseline test. State the frequency in your security policy.
Related guides
How to choose an offensive security company in the UAE · Offensive security certifications explained · Crypto security testing and forensics in the UAE