Home
VAPT Web Application PentestAPI PentestMobile App PentestInfrastructure PentestAI & LLM PentestOT / ICS PentestIoT PentestPenetration TestingAll VAPT services
Red Team Red Team EngagementAdversary SimulationAssumed BreachPurple TeamingSocial Engineering
Sectors Banking & Financial ServicesGovernment & Public SectorHealthcareOil, Gas & EnergyAviation & LogisticsRetail & E-commerceManufacturing & IndustryTelecommunicationsTechnology & SaaS
CompanyResourcesBlogFree Consultation

UAE regulations that require assumed-breach testing

Four UAE regulatory regimes name advanced security testing. This article covers what each requires and what an assumed-breach exercise needs to show.

Joel Aviad OssiJoel Aviad OssiRed Team Lead, RedTeam Security
7 min read
Isometric network diagram showing a workstation connected by red flow lines through three servers to a data store, with document icons at the base representing the regulatory evidence package.

Key takeaways

  • CBUAE, NESA/IAS, DESC and ADHICS each frame an assumed-breach requirement, though only ADHICS and DESC use adversarial language explicitly.
  • Every regime expects evidence of detection, not only evidence of attack: dwell time, which controls fired and which were bypassed.
  • A DESC-regulated technology supplier to a Dubai government entity faces the same internal testing scope as the entity itself.
  • One well-structured report can satisfy multiple regimes with minor additions, because all four ask the same underlying questions.
  • An exercise run without a signed authorisation letter cannot be presented as regulatory evidence under UAE law.

What assumed breach means to a UAE regulator

An assumed-breach exercise skips the perimeter and starts from a credential or session your team grants on day one. For a regulator, that matters because a standard penetration test proves an attacker cannot get in but says nothing about what happens once they already have a foothold. Insider threat, credential theft and supply chain compromise all share the same starting point: the attacker is already inside. The question is what they can reach.

Four UAE regulatory regimes name security testing that covers internal threats. CBUAE covers licensed financial institutions. The UAE Information Assurance Regulation, published by NESA, sets a federal baseline for government entities. DESC governs Dubai government bodies and the technology suppliers that serve them. ADHICS covers healthcare providers in Abu Dhabi. The framing differs across regimes, but the underlying test is the same: given a foothold, how far can an attacker move, and what does your monitoring see while they do it?

The three phases of an assumed-breach exercise and what must be completed in each before a regulator reads the report.

CBUAE requirements for licensed financial institutions

The Central Bank of the UAE's IT governance standards apply to every UAE-licensed bank, exchange house, finance company and payment service provider. They require testing of internal response capability, not only perimeter controls, which a standard penetration test does not cover. An assumed-breach exercise addresses this by granting a foothold that matches the access a compromised staff credential or insider would have, then measuring how far the attacker can move before monitoring fires.

CBUAE expects the exercise to produce evidence of detection, not only evidence of attack. A report that records the full attack chain but names no detection events is incomplete under the standard. Dwell time before first alert, which controls triggered, which were bypassed, and what the attacker reached before the exercise closed: those are what the standard requires. See what your SIEM should catch during an assumed-breach exercise for the specific signals that should appear in that record. The Central Bank of the UAE publishes the standard and updates it periodically.

NESA and the federal Information Assurance Regulation

The UAE Information Assurance Regulation establishes security controls for federal government entities. Its technical control tier covers periodic penetration testing at a depth vulnerability scanning does not reach. The regulation does not use the label assumed breach, but the control language requires testing of lateral movement paths and internal privilege escalation, not only external access attempts. That scope is what distinguishes an assumed-breach exercise from a standard external test.

Federal entities that have run external tests and found little should note that the external surface is only part of what the IAS control set covers. An assumed-breach engagement that tests lateral movement from a granted workstation foothold to a domain controller or file repository addresses the internal control tier directly. The UAE Information Assurance Regulation is published in full by TDRA.

DESC and Dubai government entities

The Dubai Electronic Security Centre sets cybersecurity requirements for Dubai government entities and the third-party technology suppliers that connect to their systems. The supply chain scope matters: a supplier that holds a persistent authenticated session into a government network is treated as an internal actor, and testing the reach of that session is part of satisfying the advanced testing control. A red team engagement or an assumed-breach exercise starting from the supplier's granted access covers that requirement directly.

DESC's control set distinguishes a vulnerability assessment from an adversarial simulation. The first finds missing patches and misconfigured services. The second starts from a foothold and measures how far an attacker can go. The distinction is explicit in the standard. An organisation that submits only vulnerability scan results when DESC expects simulation evidence will have the gap noted on review. See DESC's cybersecurity standards for the full control language.

ADHICS and Abu Dhabi healthcare providers

ADHICS, the Abu Dhabi Healthcare Information and Cyber Security standard, requires healthcare providers to validate that internal controls hold against a threat actor who has already passed the perimeter. The Department of Health Abu Dhabi publishes it and applies it to hospitals, clinics and health data processors across the emirate. The assumed-breach model fits this framing directly: it grants a foothold that mirrors the access a compromised clinical workstation or stolen staff credential would provide. The article on cloud token theft in an assumed-breach exercise shows the kind of lateral path ADHICS segmentation controls are intended to stop.

ADHICS places particular weight on the boundary between clinical systems and administrative networks. An assumed-breach exercise scoped to test that boundary produces the evidence the standard requires: which segmentation controls were tested, which blocked the simulated attacker and which did not. The Department of Health Abu Dhabi publishes the ADHICS framework and sets the evidence format healthcare providers must follow.

The four layers an assumed-breach report must carry to satisfy any of the four UAE regulatory regimes.

What the report must carry for each regime

A report written for one UAE regulatory regime can usually satisfy another with minor additions: all four ask the same underlying questions. What objective did the attacker reach? How long did they operate before detection controls triggered? What remediation is planned and by when? The table below maps each regime to the evidence it prioritises, so the team writing the report knows what not to leave out.

The weakest assumed-breach reports record the attack chain in detail but map no detections against it. A chain that ran for three days without triggering a single SIEM alert is a finding. A report that does not state the dwell time, the detection gap and the specific controls that did not fire is incomplete evidence under any of the four regimes. For the specific attack paths that produce those detection gaps, see LSASS memory dumping and lateral movement in an assumed-breach exercise.

How the four UAE regulatory regimes map to assumed-breach exercise scope and evidence requirements.
RegimeApplies toTesting languagePriority evidence
CBUAELicensed banks, exchange houses, payment providersAdvanced security testing, response capabilityDetection log, dwell time, controls bypassed, objective reached
NESA / IASFederal government entitiesPeriodic penetration testing, internal control coverageLateral movement paths tested, privilege escalation evidence
DESCDubai government entities and technology suppliersAdversarial simulation, supply chain scopeAttack chain, supplier access scope, findings by control
ADHICSAbu Dhabi healthcare providersInternal control validation, segmentation testingSegmentation boundary test, clinical vs administrative evidence

Assumed-breach testing in Abu Dhabi and Dubai: what procurement looks like

Procurement of assumed-breach exercises in the UAE follows different paths in Dubai and Abu Dhabi. In Dubai, DESC-regulated entities typically procure through a formal tender or a framework agreement with a licensed provider. The authorisation letter names the entity, the systems in scope and the objectives the exercise tests. That letter is not optional: a test run without written authorisation from the entity's security officer is not an authorised exercise under UAE law.

In Abu Dhabi, healthcare organisations procuring ADHICS-required testing operate under the Department of Health's vendor qualification requirements. A provider must map the engagement scope and report format to ADHICS control language, not to a generic penetration testing standard. CBUAE-regulated institutions in both emirates follow the bank's own IT governance procurement policy, which typically requires a scope agreement and a data processing addendum covering the credentials and artefacts the exercise produces.

Financial institutions in Abu Dhabi and Dubai that have satisfied CBUAE requirements through a standard penetration test should check whether that test covered lateral movement from an internal foothold. The standard expects evidence across both the external and internal control tiers. A test that covers only the external surface leaves the internal tier untested. See how to buy an assumed-breach exercise in the UAE for the specific questions to put to a prospective provider, and how the engagement is scoped for what the foothold definition and objectives agreement should cover.

Frequently asked questions

What is an assumed-breach exercise?

An assumed-breach exercise starts from a credential or network session your team grants on day one. It skips the question of whether an attacker can get in and asks instead how far they can go once they have a foothold. The exercise tests lateral movement, privilege escalation and the detection controls that should fire while both happen. It differs from a standard penetration test, which starts outside the perimeter and focuses on initial access.

Which UAE regulators require assumed-breach or advanced internal security testing?

Four regimes cover it. CBUAE requires licensed financial institutions to test response capability as well as perimeter controls. The UAE Information Assurance Regulation covers federal government entities and requires internal control testing in depth, not only external access testing. DESC governs Dubai government entities and their technology suppliers, with an explicit distinction between vulnerability assessment and adversarial simulation. ADHICS requires Abu Dhabi healthcare providers to validate internal segmentation controls.

How does an assumed-breach exercise differ from a standard penetration test?

A standard penetration test begins outside the network and tests whether an attacker can gain initial access. An assumed-breach exercise begins with a granted internal foothold and tests what an attacker can do once they are already in. A standard test shows whether your perimeter holds. An assumed-breach exercise shows whether your internal controls, monitoring and segmentation hold once the perimeter has been crossed.

What evidence does CBUAE expect from an assumed-breach engagement?

CBUAE's IT governance standards expect evidence of detection capability, not only evidence of attack. The report should record which monitoring controls triggered, which were bypassed, the dwell time before the first alert, and what the attacker reached before the exercise closed. A report that records only the attack chain without naming detection events does not meet the evidence standard.

Does the UAE Information Assurance Regulation specifically require assumed-breach testing?

The regulation does not use the label assumed breach, but its technical control tier requires testing of lateral movement paths and internal privilege escalation, not only external access. That scope is what distinguishes an assumed-breach exercise from an external penetration test. Federal entities that have only run external tests have not satisfied the full depth the regulation requires.

What does DESC require from technology suppliers to Dubai government entities?

DESC's scope extends to third-party technology suppliers that hold persistent authenticated sessions into government networks. A supplier in that position is treated as an internal actor. The standard requires evidence that the reach of that access has been tested adversarially. A penetration test that covers only the supplier's external surface does not satisfy the internal testing control.

How does ADHICS frame assumed-breach testing for Abu Dhabi healthcare providers?

ADHICS requires healthcare providers to validate that internal controls hold against a threat actor who has already bypassed the perimeter. The standard places particular weight on the boundary between clinical and administrative networks. An assumed-breach exercise scoped to test that boundary produces the segmentation evidence the standard requires, with a report that names which controls held and which did not.

What should an assumed-breach report contain to satisfy UAE regulators?

The report should cover four areas: the authorisation letter and agreed scope, the full attack chain with timestamps and tools, the detection record naming which controls fired and which did not, and remediation steps ranked by risk with owners and target dates. The detection record is the most frequently missing element and the first thing regulators across all four regimes look for.

Can one assumed-breach exercise satisfy multiple UAE regulatory regimes?

It can, with minor additions to the report. All four regimes ask the same underlying questions: what objective did the attacker reach, how long did they operate undetected, and what remediation is planned. A report written against CBUAE requirements can usually be adapted for NESA or DESC with additions that address each regime's specific control language.

How is an assumed-breach exercise authorised under UAE law?

The exercise is authorised by a letter signed by the entity's designated security officer, naming the systems in scope, the objectives and the rules of engagement. That letter is required regardless of which regulatory regime applies. A test run without it is not an authorised security exercise under UAE law, and the results cannot be presented as regulatory evidence to any of the four regimes.

The engagements this applies to

Joel Aviad Ossi, Red Team Lead at RedTeam Security
Joel Aviad OssiRed Team Lead, RedTeam Security

Joel Aviad Ossi is Red Team Lead at RedTeam Security, the Dubai-licensed trading brand of WebSec FZCO. He scopes and runs objective-based engagements across the UAE.

Let's talk about your security

Tell us the objective you want tested. We will come back with a scope, a timeline and a quote, under NDA from the first conversation.

Email [email protected]
IFZA Business Park, Building A2
Nadd Hessa, Dubai Silicon Oasis
Dubai, United Arab Emirates