Bahriya Tersane

Convoys · Compliance and Assurance · Qatar NIA

Qatar: National Information Assurance Standard.

Available now. Qatar. Regulator: National Cyber Security Agency (NCSA).

The convoy's regime for the National Information Assurance Standard, version 2.1, issued by the National Cyber Security Agency. It holds every control statement of the standard under its own identifiers, shows whether each is a baseline or an additional control, 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.

In brief

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

National Cyber Security Agency (NCSA). The National Cyber Security Agency is Qatar's national authority for cybersecurity. Its national standards include the National Information Assurance Standard, version 2.1, issued by the National Cyber Security Agency.

National Information Assurance Standard (Qatar NIA). The National Information Assurance Standard, version 2.1, issued by the National Cyber Security Agency in May 2023, applies to all organisations, which it defines as businesses operating within the State of Qatar, and to their information assets. It holds 356 control statements in 26 domains, and marks each as a baseline or an additional control.

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

Businesses operating within Qatar.

The National Information Assurance Standard, version 2.1, issued by the National Cyber Security Agency of the State of Qatar in May 2023, applies to all organisations, which it defines as businesses operating within the State of Qatar, and to their information assets. Where an organisation outsources or subcontracts a process or activity, the standard expects it to ensure that the process or activity also complies.

A bank in Qatar also answers to the Qatar Central Bank, whose Technology Risks circular is a regime of its own, licensed separately. With both selected, the convoy collects evidence for each regime every day from the same cluster and the same scanner and policy reports, and reports each regime in its own numbering.

Structure

Twenty-six domains, 356 control statements.

The standard has two sections of controls: security governance and processes, in thirteen domains, and security controls, in thirteen more. It marks 166 statements as baseline controls, which an organisation implements for every information asset above the lowest security rating, and the other 190 as additional controls, chosen by risk assessment for assets rated higher. The report shows beside each requirement which of the two it is, and lists the objects that fail a baseline control ahead of the others.

  1. IG Security governance 10
  2. RM Risk management 5
  3. TM Third-party security management 5
  4. DL Data labelling 5
  5. CM Change management 6
  6. PS Personnel security 12
  7. SA Security awareness 8
  8. IM Incident management 9
  9. BC Business continuity management 9
  10. SM Logging and security monitoring 9
  11. DR Data retention and archival 6
  12. DC Documentation 5
  13. AC Audit and certification 8
  14. CS Communications security 12
  15. NS Network security 66
  16. IE Information exchange 13
  17. GS Gateway security 17
  18. PR Product security 9
  19. SS Software security 32
  20. SU System usage security 11
  21. MS Media security 21
  22. AM Access control security 41
  23. CY Cryptographic security 12
  24. OS Portable devices and working off site 10
  25. PH Physical security 7
  26. VL Virtualisation 8
The standard's twenty-six domains, with the number of control statements in each: 97 in security governance and processes, from IG to AC, and 259 in security controls, from CS to VL, 356 in all.

Evidence

What the cluster shows, and what remains yours.

  • Enforced, checked and platform. Thirty-six of the 356 statements: seven enforced by an admission policy, eight checked in the cluster and eighteen provided by the platform. They sit in the domains for access control, software, network, cryptographic and product security, logging and security monitoring, information exchange, data labelling, data retention and personnel security. The API server's own audit log is judged against the standard's retention of at least 120 days; a central log store, and the retention of other logs, remain the organisation's to evidence.
  • Your evidence. The other 323, among them every statement on governance, risk management, incident management, business continuity, audit, gateways, media, physical security and virtualisation, are your organisation's to evidence, and the report lists each as such.
  • Where the cluster shows part of a statement. Where a statement asks for more than the cluster can show, the report states what the checks evidence and what remains the organisation's, beside the verdict.

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. For each regime selected, the convoy collects evidence every day from the same cluster and the same scanner and policy reports, and reports it in its regulator's own numbering.

The standard maps none of its control statements to NIST SP 800-53 or to ISO/IEC 27001. NCSA is the source and owner of the standard: the report uses its identifiers, its sections and its domain headings, and each requirement's summary is Mamluk's paraphrase, not the standard's text, whose authoritative wording is NCSA's.

The regulator publishes no official crosswalk to NIST, so the mapping is Mamluk's own. Before the regime was released, it was checked against the regulator's text a second time, statement by statement, by a reviewer other than its author.

The report states whose mapping it uses, in these words: “NCSA publishes no mapping of these requirements to NIST SP 800-53. The mapping in this report is Mamluk's own.” 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.
NCSA National Cyber Security Agency
The National Cyber Security Agency is Qatar's national authority for cybersecurity. Its national standards include the National Information Assurance Standard, version 2.1, issued by the National Cyber Security Agency.
Qatar NIA National Information Assurance Standard
The National Information Assurance Standard, version 2.1, issued by the National Cyber Security Agency in May 2023, applies to all organisations, which it defines as businesses operating within the State of Qatar, and to their information assets. It holds 356 control statements in 26 domains, and marks each as a baseline or an additional control.
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 Qatar NIA

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

Contact Mamluk