Three sets of rules shape application security work in the United Arab Emirates. The federal Information Assurance (IA) Regulation covers secure development and vulnerability management for government and critical sectors. The Central Bank of the UAE (CBUAE) expects financial institutions to have critical functions tested independently. In Dubai, the Information Security Regulation (ISR) from the Dubai Electronic Security Center (DESC) applies to government entities and their contractors. None of them names a tool. All of them expect evidence.
This guide maps those expectations to practical testing activities. It is a working summary, not legal advice, and it relies on publicly available descriptions of the texts. Use the current official documents as the reference.
Who must comply
| Rule set | Applies to |
|---|---|
| UAE IA Regulation (originally issued by NESA) | Federal government entities and operators of critical information infrastructure |
| CBUAE regulations | Banks and other licensed financial institutions |
| Dubai ISR (DESC) | Dubai government and semi-government entities, and contractors working for them |
| Sector rules, for example in health care | Entities in that sector and emirate |
What the IA Regulation expects for software
The control family for acquisition, development and maintenance of information systems is the one development teams meet. In summary it covers:
- Security requirements and secure development practice for in-house systems.
- For outsourced development: review of the delivered source code, contract terms that give audit and secure coding rights, and an internal coding policy with quality assurance.
- Technical vulnerability management as a top-priority control, which in practice means regular scanning and manual application testing.
There is no fixed annual interval in the regulation. Most covered organisations test yearly and after significant change.
What CBUAE expects
Financial institutions are expected to test their control environment on a recurring basis and to have critical functions tested by an independent firm, with results reported at board level. Published mappings also link static analysis and component analysis to the central bank’s expectations for secure development and third-party risk.
What the Dubai ISR expects
The ISR includes secure development among its domains. Published guidance describes yearly testing of externally facing services and more frequent vulnerability assessments, and requires certified providers for penetration tests of government and critical infrastructure entities.
Evidence assessors ask for
- A secure development policy and an approved coding standard.
- Static and dynamic testing reports per release.
- Source code review records for outsourced development.
- Penetration test reports from an independent, suitably certified provider, with retest results.
- A remediation register with severity, owner, due date and closure evidence.
- Supplier contracts with secure coding and audit terms.
A testing programme that covers all three
| Stage | Activity | Output |
|---|---|---|
| Design | Threat modelling | Security requirements |
| Development | SAST and dependency analysis on each merge | Findings fixed before release |
| Supplier delivery | Source code review of delivered code | Acceptance record |
| Before release | Authenticated DAST and mobile app testing | Release security report |
| Yearly, and after major change | Independent penetration test with retest | Assurance report |
How Offensive360 supports this
Offensive360 provides SAST, DAST, mobile application testing and software composition analysis in one platform that runs on-premise, in Azure or in a disconnected network, with Arabic and English interfaces and reports. Static analysis of delivered source code supports the review of outsourced development, and findings can be exported as evidence.
See deployment options, compliance mapping and the Gulf overview, or book a demo.
This summary reflects publicly available descriptions of the rules as of November 2026. Confirm wording, numbering and provider requirements against the official documents.
Frequently asked questions
Does the UAE Information Assurance Regulation require application security testing?
In substance, yes. Its control family for the acquisition, development and maintenance of information systems covers secure development, review of outsourced code and technical vulnerability management. It does not name tools or set a fixed test interval, so organisations set a risk-based schedule and keep evidence.
How often must banks in the UAE run penetration tests?
Central Bank of the UAE rules expect independent testing of critical functions with results reported to the board. Published guidance describes the cadence as risk based, commonly yearly and after significant change. Confirm against the current CBUAE rulebook.
Who may perform penetration tests for Dubai government entities?
Published guidance states that since July 2024 penetration tests for Dubai government, semi-government and critical infrastructure entities must come from providers certified under the scheme run by the Dubai Electronic Security Center. Check the current DESC list before you appoint a tester.
Can the testing platform stay inside the UAE?
Yes. A self-hosted platform runs in your own data centre or in a cloud region in the UAE, so source code and findings stay inside your environment.