What Is NESA Compliance? The UAE IA Regulation Explained
Short answerNESA compliance is the name still used for meeting the UAE Information Assurance (IA) Regulation, which TDRA publishes as part of the National Information Assurance Framework. It is mandatory for UAE government entities and for critical entities TDRA designates under the CIIP policy, and voluntary for everyone else. Its 15 control families hold 188 controls, applied through a risk assessment and four priority levels.

What is NESA compliance?
NESA compliance is the name still used for meeting the UAE's national information assurance controls. The National Electronic Security Authority (NESA) developed the UAE Information Assurance (IA) Standards, which the National Information Assurance Framework (NIAF) describes. The document TDRA publishes today is the UAE IA Regulation, version 1.1, issued by TRA (now TDRA) in March 2020 as part of the same framework. It is mandatory for UAE government entities and for organisations designated as critical under the UAE Critical Information Infrastructure Protection (CIIP) policy, and TDRA recommends it to every other UAE organisation on a voluntary basis.
Need help applying this to your business? See NESA compliance services, or describe your requirements to GR IT.
A newer document also exists. In November 2025 the UAE Cyber Security Council published the UAE Information Assurance Standard, version 2.1, with 134 controls, 70 of them Always Applicable. The Council's standard does not say whether it replaces the IA Regulation, so ask your sector regulator which version you will be assessed against. This guide explains the IA Regulation; our comparison of NESA and ISO 27001 covers version 2.1.
Who has to comply with the UAE IA Regulation?
UAE government entities and the critical entities TDRA designates under the CIIP policy have to comply. For every other organisation it is voluntary.
- Government entities. The regulation says all UAE government entities are obligated to implement it.
- Designated critical entities. TDRA designates them under the CIIP policy. That policy identifies critical sectors and national services, assesses risks, defines sector-specific cybersecurity requirements and monitors the implementation of sector plans.
- Everyone else. TDRA highly recommends that all UAE entities adopt the regulation voluntarily, as applicable.
The regulation leaves designation to TDRA, and the CIIP policy sets out the process for identifying critical entities. If unsure, ask your sector regulator or TDRA rather than trusting a list of company names found online.
Suppliers can be drawn in as well. The T6 Third Party Security family requires entities to make sure third parties implement and maintain the appropriate level of information security.
In Dubai, the Dubai Electronic Security Center (DESC) monitors government entities to make sure they comply with information security requirements; see DESC ISR compliance. For healthcare organisations in Abu Dhabi, see ADHICS compliance.
How is the IA Regulation organised?
The regulation has 15 control families holding 188 controls: six management families and nine technical families.
- Management, M1 to M6: Strategy and Planning; Information Security Risk Management; Awareness and Training; Human Resources Security; Compliance; Performance Evaluation and Improvement.
- Technical, T1 to T9: Asset Management; Physical and Environmental Security; Operations Management; Communications; Access Control; Third Party Security; Information Systems Acquisition, Development and Maintenance; Information Security Incident Management; Information Systems Continuity Management.
Three ideas decide what you actually implement.
- Risk-based applicability. Before the risk assessment, every control counts as applicable. You may exclude controls on the basis of the risk assessment, with adequate justification submitted to TDRA. With no risk assessment at all, every control is mandatory.
- Always Applicable controls. These apply whatever the risk assessment says. Annex A puts the total at 34, all management controls, covering areas such as the security policy, risk assessment, training, screening, removal of access rights and internal audit.
- Priority levels P1 to P4. Annex B places 39 controls at P1, 69 at P2, 35 at P3 and 45 at P4. Critical entities must implement every applicable control but begin with P1. They may promote or demote suggested priorities after their risk assessment, but an applicable P1 control can be augmented, never reduced.
The regulation was developed from sources including ISO/IEC 27001 and 27002, NIST SP 800-53 and the Abu Dhabi Information Security Standards, and Annex C maps its controls against them. An existing ISO 27001 programme is a head start, not a substitute: Annex C shows some IA controls, such as T8.2.2 Computer Security Incident Response Team, with no ISO 27001 equivalent.
How does a NESA gap analysis work?
A gap analysis compares each applicable control with what you can evidence today, then turns the differences into a prioritised remediation plan. That mirrors the regulation's own definition of compliance: the requirements set against the actual state of implementation.
- Scope. Agree which entity, services, systems and sites are covered. The regulation applies to information in physical or electronic form, so paper records and offices can be in scope as well as cloud systems.
- Risk assessment. Run or refresh it. The result decides which controls apply and, for critical entities, the order of work.
- Control owners. Name an owner for each applicable control. Owners explain how the control works today and where its evidence lives.
- Evidence. Collect policies, configuration exports, logs and records for each sub-control. Sub-controls of Always Applicable controls cannot be omitted; any other deviation needs a justification and evidence that accountable people accepted the risk.
- Gap list. Mark each control as met, partly met or not met. Record every exclusion with the risk acceptance behind it.
- Remediation plan. Order the gaps by Always Applicable status, priority level and risk. Give each one an owner and a date, and agree the performance indicators that will show the control works.
Our gap assessment service works the same way: the current position is established from evidence, and every gap gets an agreed owner.
Which Microsoft 365 controls map to IA families?
Microsoft 365 and Microsoft Entra features can produce evidence for several technical controls, but no product makes you compliant. The regulation calls itself the sole point of reference for compliance, measured by the criteria attached to each control. Three families show how the mapping works.
T5 Access Control
- T5.2.3 User Security Credentials Management (P1) requires multi-factor authentication for access to critical resources. Conditional Access policies can enforce it; Microsoft's own example is a user who must perform multifactor authentication to reach Microsoft 365.
- T5.2.4 Review of User Access Rights (P1) requires periodic reviews. Microsoft Entra access reviews let you review user access regularly so only the right people keep it.
- T5.2.2 Privilege Management (P1) requires two-factor authentication and logging for all administrative access. Privileged Identity Management gives just-in-time, approval-based admin roles, enforces multifactor authentication on activation and keeps audit history.
T8 Information Security Incident Management
- T8.2.1 Incident Response Plan requires documented, tested procedures, a communication plan and senior management approval. That is a written plan your management signs off; no tool supplies it.
- T8.2.9 Collection of Evidence requires procedures that cover chain of custody. In the Microsoft Defender portal, an incident groups related alerts and holds the timeline and evidence behind an attack, which feeds those records.
- T8.3.2 Reporting Information Security Events requires a named point of contact and a reporting route to stakeholders, including the appropriate authority. At GR, Defender alerts are triaged by our own SOC; see SOC as a service.
T9 Continuity, with T3.5 backup
- T9.2.1 and T9.3.1 require continuity plans with escalation criteria, named roles and contact details, then periodic tests and updates. These are business plans and exercises.
- T3.5.1 Information Backup (P1) requires backups that are routinely tested for reliability. Microsoft 365 Backup can back up all or selected SharePoint sites, OneDrive accounts and Exchange mailboxes. Running and recording restore tests is still your job.
Microsoft Purview Compliance Manager also lists a regulatory template named "UAE - NESA Information Assurance Standards", showing its controls and improvement actions. Which templates you can use by default depends on your licensing agreement, and a template score is a working aid, not a compliance finding.
What drives the effort and cost of NESA compliance work?
Scope and your starting point drive the effort, not company size alone. The main drivers are:
- How many entities, services, systems and sites are in scope, including paper records and physical premises under T2 Physical and Environmental Security.
- Whether a current risk assessment exists, since it decides which controls apply.
- How many of the Always Applicable controls already have evidence. They are mostly policy, risk, training and HR processes.
- Whether logging, monitoring and incident response already run, or have to be built.
- Your licensing position, because some features used as evidence, such as Privileged Identity Management, need licences.
- Whether you are a designated critical entity working through P1 to P4 with sector-specific requirements, or a voluntary adopter deciding what applies.
- Whether you need support through a compliance audit or test performed or commissioned by TDRA.
A written scope after the gap analysis is the sound basis for any estimate.
How is compliance evaluated?
Chapter 4, "Compliance with the UAE IA Regulation", defines compliance as the comparison between what the regulation requires and what an entity has actually implemented, measured per control and for the entity overall. The main elements are:
- Controls. Always Applicable controls must be implemented; omitting one is non-conformity. Excluding a risk-based control needs justification and evidence that accountable people accepted the risk.
- Sub-controls. All sub-controls of Always Applicable controls must be met. Deviations elsewhere need the same justification and evidence.
- Performance indicators. Entities must use them to measure the quality and effectiveness of implemented controls. You may set your own, with a stated reason.
Implementation guidance in the regulation is for information only. Implementing entities update their sector regulator on progress, or TDRA where there is no sector regulator. Sector regulators consolidate those reports for TDRA, and TDRA reviews the self-assessment reports and, where appropriate, performs or commissions compliance audits and tests. The NIAF also notes that entities required to demonstrate compliance with its Common Standards may not need certification, so if a supplier or product claims a NESA certification, ask which scheme it refers to. For a security audit before that point, see cybersecurity audit and compliance.
Need NESA compliance delivered rather than explained? Our NESA compliance services cover readiness audit, foundation build, and ongoing operations.
Sources
- UAE Information Assurance Regulation, Version 1.1, Telecommunications and Digital Government Regulatory Authority (TDRA). Checked 2026-11-03.
- The National Information Assurance Framework, Supreme Council for National Security, National Electronic Security Authority (NESA). Checked 2026-11-03.
- Critical Information Infrastructure Protection Policy, u.ae, The Official Platform of the UAE Government. Checked 2026-11-03.
- Cyber safety and digital security, u.ae, The Official Platform of the UAE Government. Checked 2026-11-03.
- Microsoft Purview Compliance Manager regulations list, Microsoft Learn. Checked 2026-11-03.
- Microsoft Entra Conditional Access: Zero Trust Policy Engine, Microsoft Learn. Checked 2026-11-03.
- What are access reviews?, Microsoft Learn. Checked 2026-11-03.
- What is Privileged Identity Management?, Microsoft Learn. Checked 2026-11-03.
- Incidents and alerts in the Microsoft Defender portal, Microsoft Learn. Checked 2026-11-03.
- Overview of Microsoft 365 Backup, Microsoft Learn. Checked 2026-11-03.
- UAE Information Assurance Standard, Version 2.1 (PDF), UAE Cyber Security Council. Checked 2026-11-03.
Related Articles
Microsoft Defender for Business in the UAE: Endpoint Protection and XDR for SMBs
Microsoft Defender for Business is endpoint security for organisations of up to 300 users: next-generation protection, endpoint detection and response, automated investigation and core vulnerability management. It is sold standalone and included in Microsoft 365 Business Premium, and protects only onboarded devices.
Microsoft 365 Security in Dubai: What Each Plan Includes and What to Switch On First
Which Microsoft 365 security features come with Business Premium, E3 and E5, and the order a UAE business should switch them on: Entra ID MFA and Conditional Access, Defender for Office 365, Intune, Defender for Endpoint, Purview and Defender for Cloud Apps.
Network Security for UAE Businesses: Firewall, VPN and Threat Protection
Comprehensive network security guide for UAE businesses. Learn next-gen firewalls, VPN, network segmentation, IDS/IPS, zero trust network access, DDoS protection, and advanced threat prevention strategies.