Skip to main content

Free 30-min security demo Book Now

Application Security

GCC AppSec Testing Rules by Country

Application security testing requirements in Saudi Arabia, the UAE, Qatar, Kuwait and Jordan at a glance: frameworks, regulators and expected evidence.

Offensive360 Security Research Team 3 min read
GCC cybersecurity compliance application security testing NCA ECC SAMA CSF UAE IA Qatar NIA CBK Central Bank of Jordan

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

CountryNational frameworkFinancial regulatorTesting cadence as describedDetailed guide
Saudi ArabiaNCA Essential Cybersecurity Controls (ECC-2:2024)SAMA Cyber Security FrameworkPeriodic, by criticality, and before go-liveSaudi guide
United Arab EmiratesUAE Information Assurance Regulation; Dubai ISR in DubaiCentral Bank of the UAERisk based, commonly yearly and after changeUAE guide
QatarNational Information Assurance Standard (v2.1)Qatar Central Bank technology risk regulationsBefore and after implementation; twice a year for banksQatar guide
KuwaitNational basic cybersecurity controlsCentral Bank of Kuwait resilience frameworkRisk based, and after major changeThis page
JordanJordan National Cybersecurity FrameworkCentral Bank of Jordan cybersecurity frameworkIn every development phase; periodic for critical systemsJordan 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

StageActivityEvidence produced
DesignThreat modellingSecurity requirements
DevelopmentSAST and component analysis on each mergePer-release static report, component inventory
Before releaseAuthenticated DAST and mobile app testingRelease security report
On a schedule and after changeIndependent penetration test with retestAssurance report
ContinuousRemediation trackingRegister 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.

Governance, risk & compliance

Evaluate your risk and evidence workflows

Explore Offensive360 GRC in Arabic or English. Bring your frameworks, evidence requirements and deployment constraints to an early-access walkthrough.

Also see: GRC for Saudi Arabia

Evaluate your risk and evidence workflows

Book a GRC demo