- ClassificationCategoryCybersecurityDomainCybersecurityFramework FamilyOther
- Regulatory ContextTypeFrameworkLegal InstrumentFrameworkSectorCross-SectorIndustryCross-Industry
- Region / PublisherRegionMiddle EastRegion DetailUnited Arab EmiratesPublisherNational Electronic Security Authority (NESA) for the NIAF; Telecommunications and Digital Government Regulatory Authority (TDRA) for IA Regulation v1.1
- VersioningVersionNIAF with UAE Information Assurance Regulation v1.1Effective DateMandatory for UAE government and designated critical entities; no commencement date is stated in the documentsIssue DateMarch 2020 (IA Regulation v1.1); the NIAF text is undated
- AdoptionAdoption ModelRegulatory ComplianceImplementation ComplexityHigh
- Official ReferenceOpen Link in New TabSource
License included / downloadable: Yes
The NIAF and the UAE Information Assurance Regulation v1.1 are published free by the UAE Government on u.ae and by TDRA. The platform links to the official pages and does not reproduce the text.
Framework text is licensed by its publisher and is included only where stated above.
- The UAE National Information Assurance Framework (NIAF), issued by NESA, sets how information assurance is achieved at entity, sector, and national levels.
- Compliance is mandatory for all UAE government entities and for entities NESA identifies as critical; others are urged to follow it voluntarily.
- The NIAF itself contains no control list; the UAE Information Assurance Regulation v1.1 (March 2020) is the control instrument.
- That Regulation has six management and nine technical control families, an Always Applicable set, and four priority levels, P1 to P4.
- Entities report implementation to sector regulators, who report to the national authority.
Overview
The UAE National Information Assurance Framework (NIAF) is the national policy framework that sets out how information assurance is achieved at the entity, sector and national levels in the United Arab Emirates. It was issued by the National Electronic Security Authority (NESA), and under section 1.5 compliance is mandatory for all UAE government entities and for other entities that NESA identifies as critical under the Critical Information Infrastructure Protection (CIIP) Policy; other UAE entities are urged to follow it voluntarily.
The NIAF itself contains no control list. It defines the building blocks (entity capabilities, sector and national contexts, information sharing, UAE standards and national governance) and relies on the UAE Information Assurance Standards for the controls. The TDRA-published UAE Information Assurance Regulation, version 1.1 of March 2020, is the control instrument in the NIAF family: six management and nine technical control families, an Always Applicable set and four priority levels, P1 to P4. The NIAF text carries no publication date.
The organizations that apply it are UAE federal and local government entities and designated critical infrastructure operators, which report implementation to sector regulators and to the national authority. TDRA's pages present the IA Regulation, and the UAE Cyber Security Council's site now presents a UAE Information Assurance Standard, so confirm the current control set with the regulator before planning an assessment.
Why does it matter?
The NIAF is the reason a UAE government entity or a designated critical operator has to treat information assurance as a national obligation, not an internal choice. It asks each entity to report its implementation to its sector regulator, who reports to the national authority, and it gives that authority four escalating levels of monitoring, up to direct intervention. An entity that cannot show its risk assessment, its integrated security controls and an incident escalation path to the sector level has little to show when monitoring moves from reporting to auditing.
Key benefits include:
- A national baseline
Compliance is mandatory for all UAE government entities and entities identified as critical (section 1.5), which sets the minimum for the sectors in the CIIP Policy.
- Entity, sector and national views
Entity results roll up through sector regulators to the national level, so each entity's report feeds a national picture of risk.
- Five assurance principles
Confidentiality, integrity, availability, authentication and non-repudiation (section 1.2) define what information assurance must deliver.
- Risk-based control selection
The IA Regulation lets an entity exclude a control only with a justification submitted to the regulator, except for the Always Applicable controls.
- Defined consequences
Section 7.2 sets four monitoring levels: reporting, auditing, testing and national security intervention.
How does it work?
Chapter 3 sets the entity context, four capabilities every entity must build in a life cycle: risk assessment (asset inventory, business impact analysis, vulnerability assessment), integrated security (logical, physical and personnel controls selected from the risk assessment), incident management (situational awareness, entity incident response and escalation to the sector and national levels) and business continuity (continuity planning, disaster recovery and return to steady state).
Chapter 4 extends this beyond the entity: sector and national risk assessment, access to national cybersecurity capabilities, sector and national situational awareness, and continuity of critical national services. Chapter 5 adds information sharing between entities, sectors and the national level. NESA defines the detailed requirements in common, sector-specific and service and product-specific UAE standards (chapter 6), with certification where NESA requires it (section 6.4).
The IA Regulation turns the entity context into controls. An entity first performs a risk assessment, treats all controls as applicable, then excludes a control only with a justification sent to the regulator. Always Applicable controls cannot be excluded, and omitting one is a non-conformity (IA Regulation chapter 4). Controls carry priority levels P1 to P4, and critical entities start with P1.
Key Elements
- Principles of information assurance
Confidentiality, integrity, availability, authentication and non-repudiation (section 1.2).
- Entity context (chapter 3)
Risk assessment, integrated security, incident management and business continuity.
- Sector and national contexts (chapter 4)
Sector and national risk assessment, national capabilities, situational awareness and continuity of critical national services.
- Information sharing (chapter 5)
Exchange of threat information and best practices across the entity, sector and national levels.
- UAE standards (chapter 6)
Common, sector-specific and service and product-specific standards, certification and the Information Assurance Technical Forums.
- National IA governance (chapter 7)
Liaison Officers named by each entity and four escalating levels of compliance monitoring.
- IA Regulation controls
Management families M1 to M6 and technical families T1 to T9, with P1 to P4 priorities and an Always Applicable set.
What does it cover?
The NIAF applies to all UAE government entities and to other entities that NESA identifies as critical in the sectors the CIIP Policy lists. The CIIP Policy outlines the process for designating an entity as critical, and the IA Regulation states that the regulator designates the critical entities that must implement it, covering information and systems used for processing, storage and transmission, in physical or electronic form. Other UAE entities are encouraged to follow the framework on a voluntary basis. Each entity names a Liaison Officer for contact with the national authority (section 7.1).
What are its objectives?
The NIAF has two core objectives, set out in section 1.1.
Raise the minimum cybersecurity level across all UAE entities by building a common understanding of information assurance requirements at the entity level.
Raise the security of the information infrastructure that supports critical national services, by integrating individual entities into a sector and national context.
Framework in Context
The NIAF supports the UAE National Cyber Security Strategy, with supporting instruments listed in Annex 1: the National Risk Management Framework, the National Cyber Response Framework, the CIIP Policy, the National Cybersecurity Information-Sharing Policy, the UAE Information Assurance Standards, the National Framework for Compliance, Certification and Accreditation and the NIAF Governance Model. The IA Regulation v1.1 states that its development drew on ISO/IEC 27001, 27002, 27005, 27010 and 27032 (2005 and 2012 editions), NIST SP 800-53 Revision 4, the Abu Dhabi Information Security Standards and the SANS 20 Critical Security Controls, so evidence for those frameworks can be reused.
Common Framework Mappings
Organizations map the NIAF and IA Regulation controls to the frameworks below so that one set of evidence serves the regulator, auditors and other standards.
Mapped frameworks include:
CIS Controls v8.1
COBIT 2019
ISO 27001:2022
NIST CSF 2.0
NIST 800-53 Rev.5
PCI DSS 4.0.1
SOC 2
How SmartSuite Supports the UAE NIAF
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
Use Compliance Management to hold the IA Regulation's management and technical controls as requirements with their P1 to P4 priority and Always Applicable status, record each risk-based exclusion with its justification, and use Cyber & IT Risk to keep the asset inventory, vulnerabilities and security controls that the entity context asks for.
Entity Context Register
Keep the asset inventory, business impact analysis and vulnerability assessments required by section 3.1 with owners and review dates.
IA Regulation Control Library
Load management families M1 to M6 and technical families T1 to T9 with priority level, Always Applicable status and implementation state.
Applicability and Exclusions
Record each control excluded after the risk assessment with its justification and the risk acceptance by the accountable person.
Incident Escalation and Continuity
Track incidents with their escalation to sector and national levels, and link critical services, business impact analysis records and recovery plans in Operational Resilience & Business Continuity.
Regulator Reporting
Assemble self-assessment reports, audit evidence and test results for the sector regulator, and record the Liaison Officer and reporting dates.
Third Party Security
Track contractors and service providers against the third-party family T6 with Third Party Risk Management, including due diligence and review dates.
Related frameworks

CIS Controls v8.1 is a prioritized set of 18 Controls and 153 Safeguards, in three Implementation Groups, with a new Govern function.

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

ISO/IEC 27701:2025 specifies requirements for a stand-alone privacy information management system (PIMS) for PII controllers and processors, replacing the 2019 edition.

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.
Frequently Asked Questions For UAE NIAF (National Information Assurance Framework)
The NIAF is the national framework for information assurance in the UAE, issued by the National Electronic Security Authority (NESA) to support the UAE National Cyber Security Strategy. It sets out how entities, sectors and the national level share responsibility for information assurance. It names the controls only by reference to the UAE Information Assurance Standards, which are separate documents.
Section 1.5 makes compliance mandatory for all UAE government entities and for other entities that NESA identifies as critical, under the process in the CIIP Policy. For all other UAE entities the framework is recommended on a voluntary basis. The IA Regulation adds that the regulator designates the critical entities that must implement it.
The entity context (chapter 3) is the four capabilities each entity builds: risk assessment, integrated security, incident management and business continuity. The sector and national contexts (chapter 4) connect entities through sector and national risk assessment, national cybersecurity capabilities, situational awareness and continuity of critical national services. Information sharing (chapter 5) links the three levels.
Under the IA Regulation v1.1, section 3.3, an entity treats all controls as applicable until its risk assessment justifies excluding some, but the Always Applicable controls must be implemented regardless. Section 3.4 groups controls into four priority levels, P1 to P4, and critical entities begin with P1. P1 controls that apply may be augmented but never reduced.
Section 7.2 describes four escalating levels: reporting, where NESA consolidates maturity-based self-assessments; auditing, where it may ask for evidence behind them; testing, where it can commission tests of security measures; and national security intervention in extreme cases. Each entity names a Liaison Officer for this contact under section 7.1.

Put this framework to work in SmartSuite
Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.


