Regulation · Information assurance · United Arab Emirates
UAE IAS compliance: the Information Assurance Regulation explained
UAE IAS compliance means meeting the UAE Information Assurance Regulation, formerly known as the NESA standards. It sets 188 controls in 6 management and 9 technical families, prioritised from P1 to P4 and selected by risk, for government entities and critical infrastructure in the UAE and the organisations that serve them.
What you need to know about UAE IAS
Who must comply with UAE IAS?
UAE government entities, critical infrastructure and the organisations that serve them.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does the UAE Information Assurance Regulation require?
The UAE Information Assurance Regulation requires in-scope entities to run a risk-based information assurance programme: management controls for strategy, risk, people and compliance, and technical controls from assets to continuity, implemented in priority order.
Management controls
Strategy, risk, awareness, HR, compliance, improvement.
In QULDEX: Management evidence mappedTechnical controls
Assets through continuity.
In QULDEX: Controls mapped to ISO 27001Priority tiers
P1 first, then by risk.
In QULDEX: Priority tags on every controlRisk-based selection
Risk assessment decides applicability.
In QULDEX: Risk registerEvaluation
Internal audit and improvement.
In QULDEX: Audit workspaceWhat are the UAE IAS control families?
The 15 control families plus the priority model. Select any family to see what it covers, typical evidence and the matching ISO 27001 controls.
Showing up to 6 per group. Search, filter, or open a group to see all 16.
Management controls 6
M1Strategy and planningInformation security strategy, policy and the organisation's security management structure.
In QULDEXQULDEX tracks this control family with owners, priority tags (P1–P4) and evidence, mapped to ISO 27001.
- Typical evidence
- Strategy, policy
- Maps to
- ISO 27001 5.1–5.3
M2Information security risk managementRisk assessment and treatment, and threat-driven control selection.
In QULDEXThe risk register drives which controls apply.
- Typical evidence
- Risk register
- Maps to
- ISO 27001 6.1
M3Awareness and trainingSecurity awareness and role-based training.
In QULDEXQULDEX tracks this control family with owners, priority tags (P1–P4) and evidence, mapped to ISO 27001.
- Typical evidence
- Training records
- Maps to
- ISO 27001 A.6.3
M4Human resources securitySecurity before, during and after employment.
In QULDEXQULDEX tracks this control family with owners, priority tags (P1–P4) and evidence, mapped to ISO 27001.
- Typical evidence
- Screening, NDAs
- Maps to
- ISO 27001 A.6.1–A.6.5
M5ComplianceCompliance with legal and regulatory requirements and the IA Regulation itself.
In QULDEXQULDEX tracks this control family with owners, priority tags (P1–P4) and evidence, mapped to ISO 27001.
- Typical evidence
- Compliance register
- Maps to
- ISO 27001 A.5.31
M6Performance evaluation and improvementMonitoring, internal audit and continual improvement of information assurance.
In QULDEXAudits and findings run in the audit workspace.
- Typical evidence
- Audit reports
- Maps to
- ISO 27001 9.2, 10
Technical controls 9
T1Asset managementInventory, ownership, classification and handling of information assets.
In QULDEXQULDEX tracks this control family with owners, priority tags (P1–P4) and evidence, mapped to ISO 27001.
- Typical evidence
- Asset inventory
- Maps to
- ISO 27001 A.5.9–A.5.13
T2Physical and environmental securitySecure areas, equipment protection and environmental controls.
In QULDEXQULDEX tracks this control family with owners, priority tags (P1–P4) and evidence, mapped to ISO 27001.
- Typical evidence
- Physical access logs
- Maps to
- ISO 27001 A.7
T3Operations managementOperating procedures, change, capacity, malware protection, backup, logging and monitoring.
In QULDEXQULDEX tracks this control family with owners, priority tags (P1–P4) and evidence, mapped to ISO 27001.
- Typical evidence
- Operational records
- Maps to
- ISO 27001 A.8.6–A.8.16
T4CommunicationsNetwork security, information transfer and electronic messaging.
In QULDEXQULDEX tracks this control family with owners, priority tags (P1–P4) and evidence, mapped to ISO 27001.
- Typical evidence
- Network diagrams
- Maps to
- ISO 27001 A.8.20–A.8.22
T5Access controlAccess policy, user access management, privileged access and authentication.
In QULDEXAccess reviews run as recurring tasks.
- Typical evidence
- Access reviews
- Maps to
- ISO 27001 A.5.15–A.5.18
T6Third-party securitySecurity requirements for suppliers and outsourced services.
In QULDEXEach supplier is assessed and linked to its services.
- Typical evidence
- Supplier assessments
- Maps to
- ISO 27001 A.5.19–A.5.22
T7Information systems acquisition, development and maintenanceSecurity in system requirements, development and testing.
In QULDEXQULDEX tracks this control family with owners, priority tags (P1–P4) and evidence, mapped to ISO 27001.
- Typical evidence
- SDLC evidence
- Maps to
- ISO 27001 A.8.25–A.8.29
T8Incident managementIncident detection, response, reporting and learning.
In QULDEXIncidents run with timers and reporting records.
- Typical evidence
- Incident reports
- Maps to
- ISO 27001 A.5.24–A.5.27
T9Information systems continuity managementContinuity of information systems and recovery planning.
In QULDEXContinuity evidence is reused from ISO 22301.
- Typical evidence
- DR tests
- Maps to
- ISO 22301
Priorities 1
P1–P4Control prioritiesPriority modelControls carry a priority from P1 to P4. P1 controls are the foundation every in-scope entity implements first; the rest follow from the risk assessment.
In QULDEXPriority tags drive the implementation plan and the dashboard.
Nothing matches that search.
Family codes follow the UAE Information Assurance Regulation. Summaries are QULDEX paraphrases; the regulation is the authority.
How do you comply with UAE IAS?
Run a risk assessment, implement the P1 controls first, then the controls your risk profile selects, and evidence them for the sector regulator. Most entities need 6 to 12 months, less with ISO 27001.
Confirm scope and regulator
Check whether you are in a critical sector or supply one, and who supervises you.
Risk assessment
Assess risks and select applicable controls (M2).
Implement P1 controls
The foundation controls, first.
Implement risk-selected controls
P2 to P4 controls your risk assessment requires.
Audit and evaluate
Internal audit and management review (M6).
Keep improving
YearlyRisk assessmentPeriodicInternal auditOn changeRe-assess controls
Durations are QULDEX planning ranges.
Which documents does UAE IAS need?
Sector regulators and auditors ask for these records.
| Document | Family | Where it lives in QULDEX |
|---|---|---|
| Information security strategy and policy | M1 | Policy library |
| Risk assessment and control selection | M2 | Risk register |
| Training records | M3 | Evidence vault |
| Compliance register | M5 | Policy library |
| Internal audit reports | M6 | Audit workspace |
| Asset inventory | T1 | Risk register |
| Access reviews | T5 | Evidence vault |
| Supplier assessments | T6 | Vendor register |
| Incident reports | T8 | CAPA automation |
| Continuity and DR tests | T9 | Evidence vault |
Family codes follow the UAE IA Regulation.
How long does UAE IAS take and what drives the effort?
Most entities need 6 to 12 months. P1 coverage, supplier controls and the risk-based selection drive the effort.
Where the time goes
Bars show the upper end of each range on one scale (12 months = full width).
What changes the effort
- Existing ISO 27001: maps closely to most families
- Sector: regulators may add requirements
- Suppliers: third-party controls take time
- Risk profile: decides how many P2–P4 controls apply
- Data location: cloud hosting rules may apply
How ready are you for UAE IAS?
Check these eight things first. Nothing you enter leaves this page.
How UAE IAS maps to ISO 27001, NCA ECC and the UAE PDPL
The IA Regulation was modelled closely on ISO 27001. Organisations operating in both the UAE and Saudi Arabia can reuse most evidence for NCA ECC.
UAE crosswalk
| UAE IAS | ISO 27001:2022 | NCA ECC-2:2024 | UAE PDPL | Shared evidence |
|---|---|---|---|---|
| M1 Strategy | 5.1–5.3 | 1-1, 1-2 | — | Strategy |
| M2 Risk | 6.1 | 1-5 | Security measures | Risk register |
| T1 Assets | A.5.9 | 2-1 | Records of processing | Inventory |
| T5 Access | A.5.15–A.5.18 | 2-2 | — | Access reviews |
| T6 Third parties | A.5.19–A.5.22 | 4-1 | Processor duties | Vendor register |
| T8 Incidents | A.5.24–A.5.27 | 2-13 | Breach notification | Incident reports |
| T9 Continuity | A.5.29–A.5.30 | 3-1 | — | DR tests |
Indicative mapping for planning. The full crosswalk is in the QULDEX control library.
How QULDEX runs UAE IAS from risk assessment to audit
QULDEX is UAE IAS compliance and audit management software built from EGV Group's audit delivery, used by in-scope entities, their advisors and auditors. Pick your role to see who does what.
For government entities, critical sectors and suppliers.
- ScopeConfirm scopeScope and regulator recorded
- RiskAssess riskRisk register drives selection
- P1Implement P1P1 controls tracked first
- ControlsImplement the restControls mapped to ISO 27001
- SuppliersAssess suppliersVendor register
- AuditHost the auditControlled evidence sharing
For information assurance consultants and internal audit.
- ScopeRun the gap assessmentA reusable IAS gap template
- RiskReview the assessmentComments per risk
- P1Track progressPriority dashboard
- ControlsReview evidenceReview states
- SuppliersCheck contractsStatus per supplier
- AuditPrepare the packAn audit-ready pack
For independent and sector auditors.
- ScopePlanScope in a standard format
- RiskReviewView-only access
- P1SampleView-only evidence with download control and an access log
- ControlsTestFindings per family
- SuppliersTestSupplier evidence
- AuditAuditFindings into CAPA
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →UAE IAS questions people ask
What is UAE IAS?
The UAE Information Assurance Regulation and its standards, originally issued by NESA and now published by the TDRA. It sets 188 controls for government entities and critical sectors.
Is NESA the same as UAE IAS?
Yes. "NESA standards" is the older name; the same Information Assurance Standards now sit under the UAE IA Regulation, with the Signals Intelligence Agency as the successor to NESA.
What are P1 controls?
The highest-priority controls that every in-scope entity implements first. P2 to P4 controls follow based on the risk assessment.
Who must comply with UAE IAS?
UAE government entities and organisations in critical sectors, plus suppliers that handle their information. Sector regulators can require it.
Does ISO 27001 cover UAE IAS?
Most of it, because the regulation was modelled on ISO 27001, but UAE IAS adds priority tiers and UAE-specific requirements.
Go deeper on UAE IAS
GCC compliance topic hub
NCA ECC, SAMA CSF, UAE IAS and Gulf data protection laws.
blog.quldex.comAudit evidence naming convention
A file-naming scheme auditors can follow.
blog.quldex.comAudit sampling size for compliance
How many samples auditors look at.
blog.quldex.comISO 27001:2022 transition: what changed
The control set UAE IAS maps to.
References
- UAE Information Assurance Regulation, Telecommunications and Digital Government Regulatory Authority (TDRA). tdra.gov.ae
- UAE Information Assurance Standards (originally NESA). tdra.gov.ae
- ISO/IEC 27001:2022. iso.org
Reviewed by
Page history
- : Page first built: control family explorer, priority model and readiness check
Know your P1 coverage before the next review
Answer a short readiness check and get a gap summary by family. No sales call needed to see the result.