Across the Gulf and Jordan, the national cybersecurity frameworks and the central banks ask for the same three things from software teams: a secure development process, security testing before systems go live and at regular intervals, and evidence that findings are fixed. The frameworks differ in who they bind, how often they expect testing and who may perform it. This overview puts them side by side and links to the detailed guides.
It is a working summary, not legal advice. Use the current official texts as the reference.
At a glance
| Country | National framework | Financial regulator | Testing cadence as described | Detailed guide |
|---|---|---|---|---|
| Saudi Arabia | NCA Essential Cybersecurity Controls (ECC-2:2024) | SAMA Cyber Security Framework | Periodic, by criticality, and before go-live | Saudi guide |
| United Arab Emirates | UAE Information Assurance Regulation; Dubai ISR in Dubai | Central Bank of the UAE | Risk based, commonly yearly and after change | UAE guide |
| Qatar | National Information Assurance Standard (v2.1) | Qatar Central Bank technology risk regulations | Before and after implementation; twice a year for banks | Qatar guide |
| Kuwait | National basic cybersecurity controls | Central Bank of Kuwait resilience framework | Risk based, and after major change | This page |
| Jordan | Jordan National Cybersecurity Framework | Central Bank of Jordan cybersecurity framework | In every development phase; periodic for critical systems | Jordan guide |
Kuwait in brief
Banks in Kuwait follow the Central Bank of Kuwait’s cyber and operational resilience framework, which succeeded its earlier cybersecurity framework. Published descriptions list application security testing, penetration testing, vulnerability assessment and code review as expected activities on a risk-based schedule and after major changes. Kuwait’s national cybersecurity centre has also issued basic cybersecurity controls for in-scope entities, and the communications regulator has its own rules for telecom and cloud providers. Public detail is limited, so obtain the current texts from the regulators.
What the frameworks have in common
- Secure development life cycle. Security requirements at design and review during development.
- A coding standard. Usually tied to OWASP and CWE references.
- Testing before go-live. A recorded security test for each release.
- Regular assessment. Vulnerability assessment and penetration testing on a schedule and after significant change.
- Outsourced code. Review of delivered source code and security terms in contracts.
- Evidence. Reports, a remediation register and approval records.
One programme for all of them
| Stage | Activity | Evidence produced |
|---|---|---|
| Design | Threat modelling | Security requirements |
| Development | SAST and component analysis on each merge | Per-release static report, component inventory |
| Before release | Authenticated DAST and mobile app testing | Release security report |
| On a schedule and after change | Independent penetration test with retest | Assurance report |
| Continuous | Remediation tracking | Register with owners, dates and closure proof |
Where Offensive360 fits
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. The GRC platform carries control packs for NCA ECC, SAMA CSF and PDPL, and the services team performs manual code reviews and penetration tests.
See why teams choose Offensive360, the RFP checklist and deployment options, or book a demo.
This overview reflects publicly available texts and descriptions as of November 2026. Confirm against the official documents for your sector.
Frequently asked questions
Which Gulf regulations require application security testing?
Saudi Arabia's NCA Essential Cybersecurity Controls and the SAMA Cyber Security Framework, the UAE Information Assurance Regulation and central bank rules, Qatar's NIA Standard and central bank technology risk regulations, and Kuwait's central bank resilience framework all expect secure development and regular security testing. Jordan's central bank and national frameworks do the same.
Do these frameworks name specific tools?
No. They describe controls and outcomes. Organisations usually produce the evidence with static testing, dynamic testing, component analysis and independent penetration tests.
How often is testing expected?
It differs. Qatar's central bank rules are described as twice a year for banks, several others are risk based with yearly testing as common practice, and all expect testing after significant change.
Why do organisations in the region prefer self-hosted testing tools?
Public bodies and financial institutions often have to keep source code and findings inside their own environment or inside the country. A self-hosted platform, on-premise or in an in-country cloud region, meets that.