Bahriya Tersane

Convoys · Compliance and Assurance · NCA ECC

NCA Essential Cybersecurity Controls, ECC-2:2024.

Saudi Arabia. Regulator: National Cybersecurity Authority (NCA).

The convoy's first regime. It holds every requirement of the Saudi National Cybersecurity Authority's Essential Cybersecurity Controls under NCA's own identifiers, enforces and checks those a Kubernetes cluster can show, and lists the rest as your organisation's evidence, in a dated report every day.

The screenshots on this page are taken on a test cluster with sample workloads.

Neither Mamluk LLC-FZ nor its products are affiliated with or endorsed by the National Cybersecurity Authority (Saudi Arabia).

In brief

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

National Cybersecurity Authority (NCA). 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.

Essential Cybersecurity Controls (ECC). 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.

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

Government entities and critical national infrastructure in Saudi Arabia.

The Essential Cybersecurity Controls are issued by the National Cybersecurity Authority of Saudi Arabia. They bind government agencies and their affiliated companies and entities, inside and outside the Kingdom, and private-sector organisations that own, operate or host critical national infrastructure; NCA encourages other organisations to apply them. NCA assesses compliance through self-assessment, its assessment and compliance tool, and field audits.

ECC-2:2024 replaced ECC-1:2018. NCA publishes it openly, and its Arabic text is the binding one.

Structure and evidence

Four domains, 176 requirements, each with exactly one result.

The convoy holds all 176 requirements of ECC-2:2024, across its four domains and 28 subdomains, under NCA's own identifiers, with a short description of what each asks written by Mamluk; NCA's text is not reproduced, and the authoritative wording remains NCA's publication. Each requirement is classed by how its evidence is obtained:

Domain Enforced Checked Platform Your evidence Total
1 Governance1404550
2 Defence6131079108
3 Resilience00066
4 Third parties and cloud computing0001212
All requirements71710142176
  • Enforced (7). An admission policy of the convoy flags, and once you choose blocks, what the requirement forbids: software only from trusted sources (1-6-3-2), asset classification labels (2-1-5), network segmentation and the separation of production from test and development (2-5-3-1, 2-5-3-2), restricted network services (2-5-3-5), and secure protocols for external web applications (2-15-2, 2-15-3-3). The report shows the policy's result for every object it applies to.
  • Checked (17). The convoy observes the requirement in the cluster and reports it: vulnerability assessment, classification by severity and remediation (2-10), patching (2-3-3-3), least privilege, privileged access and access review (2-2-3-3 to 2-2-3-5), the role bindings recorded for the review of a leaver's rights (1-9-5), backups of the cluster's volumes (2-9-2, 2-9-3-1), the asset inventory (2-1-2), the network security requirements in effect (2-5-2), and vulnerabilities and secure configuration reviewed before launch (1-6-2-1, 1-6-2-2, 1-6-3-5).
  • Platform (10). The platform provides the control and the convoy reports it: identity and authentication for access to the cluster (2-2-2 to 2-2-3-2), the protection of the systems themselves (2-3-2), a trusted time source (2-3-3-4), the key that protects Kubernetes Secrets at rest (2-8-3-2), and audit logging, including privileged access, kept for the twelve months 2-12-3-5 requires (2-12). The Bahriya Kubernetes Engine (BKE) declares these facts from 2.3.0; on earlier BKE versions and on other distributions, these requirements are reported as not evidenced by the cluster, and the report asks for your evidence of them.
  • Your evidence (142). Strategy, governance, risk, awareness, human resources, physical security, the protection of data by its classification, resilience and third parties are your organisation's to evidence. So are the cryptography requirements that NCA's National Cryptographic Standards govern (2-8-2, 2-8-3-1 and 2-8-3-3): a cluster check cannot confirm that only the algorithms those standards approve are negotiated, in transit and at rest. The report lists each one as organisational evidence, technical or non-technical, so the record of the regime is complete and nothing is presented as covered that is not.

Thirty-three of the 34 technical requirements are partly technical: the cluster evidences its own part, and the report also asks for your evidence of the rest, for example the documented procedure behind a vulnerability management requirement. Where a regime sets a threshold, the convoy uses the regime's value: ECC's twelve months of event log retention is the value the audit log rotation check is judged against.

The report

In NCA's numbering, from the cluster itself.

Each run writes the report in HTML and PDF, with assessment results in Open Security Controls Assessment Language (OSCAL) and a signed manifest, to a volume in your cluster, and delivers it to the email addresses and storage you configure. 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. Each image opens at full size when selected.

The regime report for NCA ECC-2:2024: the run's date and cluster, the statement that the report records technical evidence and does not state compliance, and a summary of the 176 requirements by result.
The report's opening: the regime, the run, what the report is and is not, and the 176 requirements counted by result.
Requirement 1-6-3-2 of NCA ECC-2:2024 in the report: the checks for authorised registries, fixed image tags and image signatures, and the one workload whose image is not signed.
Requirement 1-6-3-2 in detail: authorised registries and fixed tags pass; the signature check names the one workload whose image is not signed.

Sample report

A sample, written by the convoy on a test cluster with sample workloads, for the organisation "Example Bank". Its image versions and cluster name 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. 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.

NCA's requirements are mapped to NIST by Mamluk, requirement by requirement; the mapping and the classes on this page are Mamluk's reading of ECC-2:2024, and the authoritative wording remains NCA's publication.

The report states whose mapping it uses, in these words: “NCA publishes no mapping of these controls 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 convoy's regimes

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.
MAS Monetary Authority of Singapore
The Monetary Authority of Singapore is Singapore's central bank and the regulator of its financial sector. It issues binding notices to banks, insurers and capital markets intermediaries, and guidelines that set out the good practice it expects them to adopt.
MAS TRM MAS Technology Risk Management
MAS's Notices FSM-N05, on technology risk management, and FSM-N06, on cyber hygiene, in force from 10 May 2024, and its Technology Risk Management Guidelines of January 2021. The notices are binding; the Guidelines are guidance, adopted in proportion to an institution's risks. The convoy holds them in one regime of 259 requirements and marks each as binding or guidance.
CBI Central Bank of Iraq
The Central Bank of Iraq licenses and regulates Iraq's banks and payment service providers. It issues the Cyber Resilience Controls for the financial and banking sector, and the Banking Reform Standards assessed for private banks.
CBI regime CBI Cyber Resilience Controls and Banking Reform Standards
The CBI's Cyber Resilience Controls (June 2024), published in Arabic, which apply to every bank and payment provider, and standards B2, B3, B7 and B9 of its Banking Reform Standards 2025, which apply to private banks. The convoy holds them in one regime of 524 requirements and marks each as Controls or Standards.
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 NCA ECC

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

Contact Mamluk