Bahriya Tersane

Convoys · Compliance and Assurance · UAE IA

UAE Information Assurance Standard.

Available now. United Arab Emirates. Regulator: UAE Cyber Security Council.

The convoy's regime for the UAE Information Assurance Standard. It holds every control of the standard under its own numbers, shows each control's applicability and priority, enforces and checks those a Kubernetes cluster can show, and lists the rest as the organisation's own evidence, in a dated report every day.

This regime is available in the Compliance and Assurance Convoy. The sample report on this page is written on a test cluster with sample workloads.

In brief

Who sets these requirements, and how the convoy evidences them.

UAE Cyber Security Council (UAE CSC). The Cyber Security Council is the federal authority for cybersecurity in the United Arab Emirates, and issues the UAE Information Assurance Standard.

UAE Information Assurance Standard (UAE IA). The Information Assurance Standard is the UAE's federal standard of security controls, binding on federal government entities and on critical information infrastructure, banks among them. Version 2.1 holds 134 controls in fifteen families, and maps each control to NIST SP 800-53 itself.

The convoy classes each requirement by how its evidence is obtained: enforced by an admission policy, checked in the cluster, provided by the platform, or the organisation's own evidence. An admission policy is a rule Kubernetes applies to each object as it is created or changed, before the object is stored. It can warn about the object and record the result, or refuse the object. How a regulator's requirement becomes evidence follows one requirement from the regulator's text to the result in the report.

Who it applies to

Federal government, critical infrastructure, and banks.

The UAE Information Assurance Standard, version 2.1 of November 2025, is issued by the Cyber Security Council of the United Arab Emirates. It applies to federal ministries and authorities, to critical information infrastructure entities outside government, and to Emirate government entities where no Emirate programme exists. Banks are critical information infrastructure.

A bank in the UAE also answers to the Central Bank of the UAE, whose Operational Risk Management Regulation is a regime of its own, licensed separately. With both selected, the convoy scans the cluster once and reports each regime from the same evidence, in its own numbering.

Structure

Fifteen families, 134 controls.

The standard has six management families and nine technical ones. Each control is either always applicable, so that omitting it is a non-conformity, or applicable on the strength of a risk assessment, and each carries a priority from 1 to 4. The report shows both beside each control, and lists first the objects that fail an always applicable control.

  1. M1 Strategy and planning 11
  2. M2 Risk management 10
  3. M3 Awareness and training 8
  4. M4 Human resources 6
  5. M5 Compliance 6
  6. M6 Performance evaluation and improvement 6
  7. T1 Information assets 12
  8. T2 Physical and environmental security 13
  9. T3 Operations management 18
  10. T4 Network security 5
  11. T5 Identity and access management 12
  12. T6 Third parties 6
  13. T7 Acquisition, development and maintenance 9
  14. T8 Incident management 9
  15. T9 Continuity 3
The Information Assurance Standard's fifteen families, with the number of controls in each: 47 management and 87 technical, 134 in all.

Evidence

What the cluster shows, and what remains yours.

  • Enforced, checked and platform. Twenty-three of the 134 controls: four enforced by an admission policy, nine checked in the cluster and ten provided by the platform. They sit in the families for information assets, operations management, network security and identity and access management, with one in third parties, on procured software, evidenced by the signatures of the images the cluster runs.
  • Your evidence. The other 111, among them every control of the six management families, physical security, acquisition and development, incident management and continuity, are your organisation's to evidence, and the report lists each as such.
  • Where the standard's mapping reaches further than the evidence. Where a control's NIST controls reach checks that do not evidence the control itself, the report names the checks it counted, and the OSCAL results mark the mapping as evidenced in part.

Sample report

A sample, written by the convoy on a test cluster with sample workloads, for the organisation "Example Bank". Its version numbers are placeholders, and its run date and regime version are those of the sample, not of a release.

The mapping

Mamluk's mapping, keyed to NIST.

Each requirement is mapped to the controls of NIST Special Publication 800-53, Revision 5 (SP 800-53), published by the National Institute of Standards and Technology (NIST), and each NIST control to the checks that evidence it in the cluster. NIST is the United States government's standards agency. Its security publications are free to use, and regulators and auditors outside the United States also use them as a common reference. SP 800-53 is a control catalogue: a numbered list of safeguards, each stating one thing an organisation should do, such as AC-6, least privilege, or AU-11, keeping audit records for a set period. Its controls are grouped in 20 families, and because the catalogue is detailed and open, it serves as a common language between regulations that are each written in their own terms.

The checks and their NIST mapping are shared by every regime, so a cluster is scanned once and each regime selected is reported from the same evidence, in its regulator's own numbering.

The UAE Information Assurance Standard is the one regime whose regulator maps every control to NIST SP 800-53 itself, and the convoy takes that mapping as published. Where it differs from what a cluster check evidences, the difference is recorded, not corrected silently.

The report states whose mapping it uses, in these words: β€œThe mapping of each control to NIST SP 800-53 Rev. 5 is the standard's own, from its Annex D, used unchanged.” It records the technical evidence the cluster provides; it does not make an organisation compliant, and compliance is determined by your assessor.

Regimes

One convoy, every regime.

Every regime runs in the same installation of the convoy. An organisation that answers to two regulators selects both, and each is licensed separately. The regimes not yet available are coming soon.

Glossary

The organisations, standards and tools the convoy's pages name.

NIST National Institute of Standards and Technology
NIST is the United States government's standards agency. Its security publications are free to use, and regulators and auditors outside the United States also use them as a common reference.
SP 800-53 NIST Special Publication 800-53, Revision 5
SP 800-53 is a control catalogue: a numbered list of safeguards, each stating one thing an organisation should do, such as AC-6, least privilege, or AU-11, keeping audit records for a set period. Its controls are grouped in 20 families, and because the catalogue is detailed and open, it serves as a common language between regulations that are each written in their own terms.
NCA National Cybersecurity Authority
NCA is Saudi Arabia's national authority for cybersecurity. It sets the cybersecurity requirements for government entities and the operators of critical national infrastructure, and assesses compliance with them.
ECC Essential Cybersecurity Controls
The ECC are NCA's minimum cybersecurity requirements, binding on government entities and critical national infrastructure in Saudi Arabia. The current edition, ECC-2:2024, holds 176 requirements in four domains.
SAMA Saudi Central Bank
SAMA regulates banks, insurers, financing companies and other financial institutions in Saudi Arabia. It keeps the abbreviation of its former name, the Saudi Arabian Monetary Authority.
SAMA CSF SAMA Cyber Security Framework
The Cyber Security Framework sets the cybersecurity requirements for the organisations SAMA regulates, as control considerations in four domains. It is distinct from NIST's Cybersecurity Framework, which is also abbreviated CSF.
QCB Qatar Central Bank
QCB is Qatar's central bank and the regulator of its banks. Its circular on technology risks, issued in January 2018, sets the technology and cybersecurity requirements for the banks it regulates, in 516 numbered statements.
CBUAE Central Bank of the UAE
The CBUAE licenses and regulates banks and other financial institutions in the United Arab Emirates. Its Operational Risk Management Regulation sets their requirements for information and communications technology and cybersecurity, and requires them to comply with the cybersecurity regulations of the other UAE authorities.
UAE CSC UAE Cyber Security Council
The Cyber Security Council is the federal authority for cybersecurity in the United Arab Emirates, and issues the UAE Information Assurance Standard.
UAE IA UAE Information Assurance Standard
The Information Assurance Standard is the UAE's federal standard of security controls, binding on federal government entities and on critical information infrastructure, banks among them. Version 2.1 holds 134 controls in fifteen families, and maps each control to NIST SP 800-53 itself.
GCC Gulf Cooperation Council
The GCC's six member states are Saudi Arabia, the United Arab Emirates, Qatar, Kuwait, Bahrain and Oman.
namespace
A namespace is a named partition of a Kubernetes cluster, which usually holds one application's or one team's workloads. Permissions and policies are commonly set per namespace.
admission policy
An admission policy is a rule Kubernetes applies to each object as it is created or changed, before the object is stored. It can warn about the object and record the result, or refuse the object.
Kyverno
Kyverno is an open-source policy engine for Kubernetes. The convoy uses it for what Kubernetes cannot do by itself, such as verifying an image's signature, and reads the results of its own policies from Kyverno's policy reports.
trivy-operator
trivy-operator is an open-source security scanner that runs inside the cluster. It scans every workload's images for known vulnerabilities, and audits each workload's configuration and the permissions granted in the cluster.
NetworkPolicy
A NetworkPolicy is the Kubernetes object that states which network traffic may reach a group of workloads. A workload that no NetworkPolicy selects accepts traffic from anywhere in the cluster.
Pod Security Kubernetes Pod Security Standards
The Pod Security Standards are three built-in levels, privileged, baseline and restricted, of what a workload may do to the server it runs on, such as running as root or reading the server's own files. Kubernetes enforces the level set for each namespace.
OSCAL Open Security Controls Assessment Language
OSCAL is NIST's machine-readable format for control catalogues and assessment results. Governance, risk and compliance tools import results in it, so findings need not be typed in again.
NSA and CISA National Security Agency and Cybersecurity and Infrastructure Security Agency
The two United States agencies publish joint guidance on hardening Kubernetes, which the convoy's checks also follow.

Price and availability

Each regime is licensed at USD 24,000 per organisation, per year, with the Tersane core licence; there is no base fee. The convoy needs a version of Kubernetes which BKE provides; the prerequisites give the requirement. See the Compliance and Assurance Convoy for how it works, and its documentation for installation. Activating a regime describes how a regime is added to the licence and to a running installation. Its reports can be read in your own cluster, by role, in the Compliance App.

Discuss UAE IA

To discuss the regimes your organisation must meet, or the convoy's licensing, contact Mamluk.

Contact Mamluk