Last reviewed: October 2026. Checked against the UAE IA Regulation v1.1, the UAE Cyber Security Council’s published material and the National Information Assurance Framework.
NESA compliance in the UAE now means compliance with the UAE Information Assurance (IA) Standard. The standard started life in the 2010s as the NESA Information Assurance Standards, was reissued as the UAE IA Regulation v1.1 in 2020, and was replaced in 2025 by version 2, issued by the UAE Cyber Security Council. Most organisations, tender documents and auditors still call it NESA, so this guide uses both names.
The standard is mandatory for UAE government entities and for organisations designated as critical information infrastructure. Many private companies adopt it voluntarily, or because a government or critical-sector client writes it into their contract.
This guide explains what version 2 changed, who has to comply, how the controls are organised, how compliance is assessed in practice, and what to check before a regulator or client asks for evidence. It also corrects some common claims, including the idea that there is a formal NESA certificate.
Table of Contents
From NESA to the UAE IA Standard
The National Electronic Security Authority (NESA) was established under Federal Decree-Law No. 3 of 2012 to lead the UAE’s information security efforts. It published the National Information Assurance Framework (NIAF) and the original Information Assurance Standards, which set out 188 security controls ranked in four priority levels, P1 to P4. NESA was later renamed the Signals Intelligence Agency.
In March 2020 the standard was reissued as the UAE IA Regulation v1.1 by the Telecommunications Regulatory Authority (TRA), now the Telecommunications and Digital Government Regulatory Authority (TDRA). The UAE Cyber Security Council, created by the Cabinet in November 2020, now leads national cybersecurity policy, including the Critical Information Infrastructure Protection (CIIP) Policy, and issued version 2 of the standard in 2025.
| Period | Name | Issued by | Key points |
|---|---|---|---|
| 2010s | NESA Information Assurance Standards | NESA | 188 controls, priorities P1 to P4, part of the National Information Assurance Framework |
| March 2020 | UAE IA Regulation v1.1 | TRA (now TDRA) | Same 188-control structure, 39 of them P1; self-assessment and reporting through sector regulators |
| 2025 | UAE IA Standard, version 2 | UAE Cyber Security Council | Reported 134 controls and 449 sub-controls; mapped to the 2025 national cybersecurity policies |
What changed in version 2 of the UAE IA Standard
The Cyber Security Council describes the UAE Information Assurance Standard as a national framework for the security and resilience of critical information infrastructure. Based on the Council’s published description and analyses from firms including KPMG, these are the main changes from v1.1:
- A smaller, restructured control set. Published analyses describe 15 control families (six management and nine technical) containing 134 controls and 449 sub-controls, compared with 188 controls in v1.1. The 188 figure still appears on many websites but refers to the earlier version.
- Always applicable and risk-based controls. Some controls apply to every in-scope entity. Others apply based on the entity’s own risk assessment, and any exclusion has to be justified through formal risk acceptance by authorised personnel.
- Performance indicators and automation guidance. The standard adds indicators for measuring control performance, and guidance on automation, threat identification and common vulnerabilities.
- Alignment with international frameworks. Controls are aligned with ISO/IEC 27001, NIST SP 800-53 and the CIS Controls, which makes it easier to reuse evidence from an existing ISO 27001 programme.
- New subject areas. Analyses of version 2 list added coverage for cloud, IoT, AI and machine learning, secure software development, threat intelligence and post-quantum cryptography.
- Links to the national policies. Controls are mapped to the national cybersecurity policies issued by the Council, such as the cloud security, encryption and third-party security policies.
The four priority levels (P1 to P4) are reported to remain in version 2, with P1 controls as the starting point that cannot be lowered by a risk assessment. A v2.1 revision was reported by KPMG in November 2025. Confirm the exact version your regulator expects before you start a gap assessment.
Who needs to comply with NESA in the UAE
Under v1.1, the standard was mandatory for all UAE government entities and for entities designated as critical under the UAE CIIP Policy, and the regulator strongly recommended it for everyone else. The Cyber Security Council describes version 2 as applying to government and non-government entities responsible for critical information systems.
Being in a critical sector does not automatically put an organisation in scope. Entities are designated under the CIIP Policy, which identifies critical information infrastructure, sets baseline requirements and defines oversight. Sectors covered by critical infrastructure policy include government services, financial services, energy, electricity and water, transport, healthcare, digital infrastructure and telecommunications, education, food and space.
Private companies that are not designated are not legally required to comply. In practice, many still need to show alignment because:
- government and critical-sector clients include IA controls in tenders and supplier contracts
- the national third-party security policy pushes requirements down the supply chain
- it gives a recognised structure for security governance that UAE regulators understand
Other UAE requirements often apply alongside it: the UAE data protection and data residency rules, the Dubai Electronic Security Center’s Information Security Regulation for Dubai government entities, ADHICS for Abu Dhabi healthcare, and Central Bank requirements for licensed financial institutions.
The control families
Version 1.1 organises its 188 controls into six management families and nine technical families. Published analyses of version 2 report the same 15-family structure. The family names below are from v1.1.
| Family | Name | What it covers |
|---|---|---|
| M1 | Strategy and Planning | Entity context, leadership, security policy and objectives |
| M2 | Information Security Risk Management | Risk assessment, risk treatment and risk acceptance |
| M3 | Awareness and Training | Security awareness for all staff and role-based training |
| M4 | Human Resources Security | Screening, terms of employment and leaving procedures |
| M5 | Compliance | Legal and regulatory requirements, compliance reviews and audits |
| M6 | Performance Evaluation and Improvement | Measuring the security programme and correcting non-conformities |
| T1 | Asset Management | Asset inventory, classification, labelling and removable media |
| T2 | Physical and Environmental Security | Secure areas, equipment protection and environmental controls |
| T3 | Operations Management | Change management, malware protection, backup, logging and monitoring |
| T4 | Communications | Network security, information transfer and electronic messaging |
| T5 | Access Control | User and privileged access management, authentication and network access |
| T6 | Third Party Security | Security requirements in supplier agreements and supplier monitoring |
| T7 | Information Systems Acquisition, Development and Maintenance | Secure development, cryptography and technical vulnerability management |
| T8 | Information Security Incident Management | Incident reporting, response and learning from incidents |
| T9 | Information Systems Continuity Management | Continuity planning, redundancy and testing |
Control numbers have three levels. For example, in v1.1 T3.4.1 is Controls Against Malware, T5.2.2 is Privilege Management and T7.7.1 is Control of Technical Vulnerabilities, all P1 controls. Two-level numbers such as T5.2 are sub-families, not individual controls.
Priority levels. In v1.1, 39 controls are P1, 69 are P2, 35 are P3 and 45 are P4. In-scope entities start with P1 and can raise or lower the priority of other controls based on their risk assessment, but P1 controls can only be strengthened, never reduced. Separately, v1.1 lists 34 management controls as always applicable.
How NESA compliance is assessed
There is no official NESA certificate. This is the most common misunderstanding about the standard. Neither v1.1 nor the Cyber Security Council’s published material describes a certification issued by accredited auditors or an annual certificate renewal.
Under v1.1, compliance works through self-assessment and reporting. In-scope entities assess themselves against the applicable controls and report periodically to their sector regulator, or to TDRA where there is no sector regulator. The regulator reviews the reports and can perform or commission compliance audits and tests. The National Information Assurance Framework describes an escalation path from reporting to auditing and testing.
For version 2, the Cyber Security Council has introduced the National Information Assurance Platform (NIAP), which provides monitoring, compliance evidence submission and a national dashboard for government entities and critical infrastructure, in line with the national policies and the IA Standard. The Council also runs the National Cyber Accreditation Program, which accredits government entities, cybersecurity service providers and training organisations. That programme is separate from IA Standard compliance.
Organisations that need to show compliance to a client often commission an independent assessment against the standard. The result is an assessment or attestation report, not a government certificate.
No published fines apply specifically to IA Standard non-compliance. Enforcement for designated entities runs through CIIP oversight and sector regulators. Do not confuse this with the Federal Decree-Law No. 34 of 2021 on combating rumours and cybercrimes, which penalises offenders, not organisations that fall short of the standard.
NESA compliance checklist
Use this checklist to prepare for a gap assessment. Answer each question with yes, no or partial, and note where the evidence is kept. It follows the 15 control families, so it applies whether your regulator assesses you against v1.1 or version 2.
Scope and governance
- Have you confirmed whether your organisation is designated under the CIIP Policy, and which regulator you report to?
- Do you know which version of the standard your regulator or client expects?
- Is there an approved information security policy and strategy, signed off by senior management (M1)?
- Are security roles assigned, including an owner for IA compliance?
Risk, people and compliance (M2 to M6)
- Is a documented risk assessment method applied, with a current risk register and treatment plans?
- Are control exclusions justified through formal risk acceptance by authorised personnel?
- Do all staff complete security awareness training, with role-based training for IT and security teams and records retained?
- Are screening, contract terms and leaving procedures, including access removal, in place?
- Are legal, regulatory and contractual security requirements documented, and reviewed through internal audit?
- Are security metrics reported to management, with corrective actions tracked to closure?
Technical controls (T1 to T9)
- Is there a complete asset inventory, with information classified and labelled (T1)?
- Are data centres and server rooms physically secured, with access logged (T2)?
- Are patching, malware protection, backup and restore testing, and log collection in place and evidenced (T3)?
- Is sensitive data encrypted in transit, and are network and email communications secured (T4)?
- Is multi-factor authentication enforced for privileged and remote access, with access reviews on a schedule (T5)?
- Do supplier contracts include security requirements, and are suppliers assessed (T6)?
- Are vulnerability assessments and penetration tests run regularly, with findings tracked (T7)?
- Is there an incident response plan with a trained team, and a process for reporting incidents to the regulator (T8)?
- Are continuity plans in place and tested for critical systems (T9)?
Evidence and ongoing reporting
- Is there one place where policies, risk assessments, test reports and logs are kept as evidence?
- Is compliance monitored continuously, not only before a review?
- Are non-conformities from audits tracked to closure with evidence?
Evidence a reviewer expects
Whether the review is a regulator audit, a client assessment or your own internal audit, the questions come down to evidence that each control is in place and operating. Typical evidence for each area:
| Area | Typical evidence |
|---|---|
| Governance (M1, M5, M6) | Approved security policy and strategy, assigned roles, compliance register, internal audit reports, management review minutes |
| Risk (M2) | Risk assessment method, current risk register, treatment plans, signed risk acceptances for excluded controls |
| People (M3, M4) | Training completion records, phishing simulation results, screening records, leaver access removal records |
| Assets (T1) | Asset inventory, data classification scheme, records of secure disposal |
| Operations (T3) | Patch reports, malware protection status, backup and restore test results, log retention settings, monitoring alerts |
| Access (T5) | Access control policy, MFA configuration, privileged account inventory, periodic access review sign-offs |
| Suppliers (T6) | Supplier security clauses, supplier risk assessments, third-party assurance reports |
| Development and vulnerabilities (T7) | Vulnerability scan and penetration test reports, remediation tracking, secure development standards |
| Incidents and continuity (T8, T9) | Incident response plan, incident log with root cause, exercise reports, continuity and recovery test results |
Evidence has to be current. A penetration test from two years ago or an access review that was never signed off counts as a gap, even when the policy behind it is sound.
Common challenges
Confirming scope. Designation, the regulator and the expected version of the standard are not always clear at the start, especially for groups with several entities or for suppliers asked to comply through a contract. Getting this in writing first avoids assessing against the wrong baseline.
Moving from v1.1 to version 2. Controls were restructured and renumbered between versions, so an existing v1.1 gap assessment needs to be mapped to the new control set before it can be reused.
Supplier evidence. The third-party family and the national third-party security policy require evidence about suppliers, which depends on suppliers responding to questionnaires and providing assurance reports.
Operational technology and legacy systems. Patching, access control and logging requirements are harder to meet on OT, IoT and medical devices and older systems, which often need compensating controls and documented risk acceptance.
Keeping evidence current. Compliance is assessed continuously through regulator reporting and, for version 2, through NIAP. Evidence gathered once for a review goes out of date quickly unless collection is part of normal operations.
How the IA Standard relates to other UAE requirements
Many organisations fall under more than one UAE framework. The IA Standard overlaps with each of them, so a single control set mapped to all applicable requirements saves duplicate work.
| Framework | Applies to | Overlap with the IA Standard |
|---|---|---|
| UAE IA Standard | UAE government entities and designated critical information infrastructure | The national baseline |
| DESC Information Security Regulation (ISR) | Dubai Government Entities, including their contractors and authorised third parties who handle government information | Similar control areas, assessed by the Dubai Electronic Security Center |
| ADHICS | Healthcare entities licensed in Abu Dhabi | Healthcare-specific information security controls |
| UAE PDPL (Federal Decree-Law No. 45 of 2021) | Organisations processing personal data in the UAE, outside the DIFC and ADGM | Security of personal data, breach notification and cross-border transfers |
| Central Bank of the UAE regulations | Licensed financial institutions | Operational risk, incident reporting and independent penetration testing |
How to approach compliance
1. Confirm scope and the expected version. Establish whether you are a designated entity, which regulator you report to, and whether you are being assessed against v1.1 or version 2. If compliance is a client requirement, get the exact wording from the contract.
2. Run a risk assessment. The standard is risk-based. Your risk assessment determines which controls beyond the always applicable set apply, and the evidence for any exclusions.
3. Carry out a gap assessment. Compare current controls against the applicable controls, starting with P1. Where you already hold ISO 27001 certification, map existing controls first to avoid duplicate work.
4. Implement and document controls. Typical gaps are privileged access management, centralised logging and monitoring, supplier security and tested incident response. Each control needs evidence that it operates, not only a policy.
5. Report and monitor. Submit self-assessments as your regulator requires, through NIAP where it applies, and keep monitoring controls between reporting cycles.
UAE IA Standard and ISO 27001 compared
Both are risk-based. The UAE IA Regulation v1.1 says so directly: applicable controls come from the entity’s risk assessment, and exclusions must be justified. The differences are in how much is prescribed and who you answer to.
| UAE IA Standard | ISO/IEC 27001 | |
|---|---|---|
| Who requires it | Mandatory for UAE government and designated critical entities | Voluntary, often required by clients |
| Control set | Prescribed national catalogue with always applicable controls and P1 to P4 priorities | Annex A controls selected through the risk assessment |
| Assessment | Self-assessment and reporting to the sector regulator, with audits and testing by the regulator | Certification audit by an accredited certification body |
| Outcome | Compliance status reported to the regulator | A certificate valid for three years, with annual surveillance audits |
Because version 2 is aligned with ISO 27001, an existing ISO programme covers much of the management system. The national requirements, the always applicable controls and the reporting to UAE authorities still need separate work.
Related national strategy and policies
The IA Standard sits within a wider national framework. The Cabinet approved the UAE National Cybersecurity Strategy 2025 to 2031 in February 2025, built on five pillars: governance, protection, innovation, building national capabilities and partnerships.
The Cyber Security Council has also issued national cybersecurity policies that the standard maps to. They include the Critical Information Infrastructure Protection Policy, the National Data Exchange Security Policy, the National Encryption Policy, the National Secure Remote Work Policy, the National Third Party Security Policy, the National Vulnerability Disclosure Policy, the National Cyber Security Policy for AI, the National Policy for IoT Security and the National Cloud Security Policy. The National Encryption Policy, approved in November 2025, requires government entities to plan their migration to post-quantum cryptography.
Frequently asked questions
What is NESA compliance?
NESA compliance means meeting the UAE Information Assurance Standard, originally published by the National Electronic Security Authority (NESA). The current version, version 2, was issued by the UAE Cyber Security Council in 2025. It sets security controls for UAE government entities and designated critical information infrastructure.
Is NESA still called NESA?
No. NESA was later renamed the Signals Intelligence Agency, and the standard is now the UAE IA Standard, issued by the UAE Cyber Security Council. Most organisations and tender documents still use the name NESA.
Who must be NESA compliant in the UAE?
UAE government entities and organisations designated as critical information infrastructure under the CIIP Policy. Other private companies are not legally required to comply, but many align with the standard because government and critical-sector clients require it in contracts.
Is there a NESA certification?
No official NESA certificate exists. In-scope entities self-assess against the standard and report to their sector regulator, which can audit and test them. Independent firms can assess an organisation against the standard and issue a report, but that is not a government certificate.
How many controls are in the UAE IA Standard?
The UAE IA Regulation v1.1 contains 188 controls in 15 families, 39 of them priority P1. Published analyses of version 2 report 134 controls and 449 sub-controls in the same 15-family structure.
What are P1 controls?
P1 controls are the highest-priority controls in the standard and the starting point for implementation. Other controls can be raised or lowered in priority based on a risk assessment, but P1 controls can only be strengthened, not reduced.
What is the penalty for not complying with NESA?
No published fines apply specifically to IA Standard non-compliance. For designated entities, enforcement runs through CIIP oversight and sector regulators, which can require reporting, audits and testing.
How does NESA compare to ISO 27001?
Both are risk-based. The UAE IA Standard adds a prescribed national control catalogue, always applicable controls, P1 to P4 priorities and reporting to UAE regulators, while ISO 27001 is a voluntary standard certified by accredited bodies. Version 2 is aligned with ISO 27001, so existing ISO work can be reused.
How long does NESA compliance take?
There is no official timeline. It depends on scope, the number of systems and entities involved, and how much of the control set is already in place. A gap assessment against the applicable controls is the usual first step and gives a realistic plan.
Does NESA apply to cloud services?
Yes. In-scope entities must apply the standard to systems hosted in the cloud, and the national Cloud Security Policy issued by the UAE Cyber Security Council sets requirements for both cloud consumers and cloud service providers.
Where can I download the UAE IA Standard PDF?
The UAE IA Regulation v1.1 is published on the TDRA website. Version 2 is distributed by the UAE Cyber Security Council, so check with the Council or your sector regulator for the current document.
This guide summarises publicly available information as of October 2026 and is not legal advice. Version 2 of the standard is distributed by the UAE Cyber Security Council, and figures for version 2 are from published analyses. Confirm your obligations with your sector regulator. The v1.1 text is available from TDRA.