Cybersecurity & Compliance

NCA ECC Compliance: A Practical Checklist for Saudi Companies

Asem Alkamel 11 min read
In this article
  1. Who the NCA ECC applies to, and what changed for private companies
  2. How ECC-2:2024 is structured
  3. How the NCA measures compliance
  4. The NCA ECC checklist: a phased roadmap for a private company
  5. Where to start if you only have ninety days
  6. Mistakes that make NCA ECC compliance fail
  7. Key takeaways
  8. Frequently asked questions
  9. Is NCA ECC compliance mandatory for private companies in Saudi Arabia?
  10. How many controls are in the NCA ECC?
  11. What is the difference between the ECC and the OTCC?
  12. What changed between ECC-1:2018 and ECC-2:2024?
  13. Does the ECC require a CISO?
NCA ECC Compliance: A Practical Checklist for Saudi Companies

NCA ECC compliance means implementing the Essential Cybersecurity Controls issued by Saudi Arabia’s National Cybersecurity Authority, currently version ECC-2:2024. The controls are binding on government agencies, their affiliated companies, and private entities that own, operate or host Critical National Infrastructure; every other company in the Kingdom is “strongly encouraged” to adopt them. In practice, the ECC has become the default yardstick that boards, auditors, insurers and large customers in Saudi Arabia use when they ask whether your cybersecurity is in order, so a private company that treats it as optional usually ends up implementing most of it anyway, just later and under pressure.

I came to the ECC from the company’s side, not the consultant’s. When I joined NAF Company as IT Manager in October 2023 there was no central infrastructure, no ERP and no IT team, and the governance, data protection and cybersecurity policies I later wrote had to be understood by a CEO, a board chairman and a vendor at the same time. The ECC’s domain structure is the most recognizable map of cybersecurity in the Saudi market, which is why this checklist follows it rather than a generic international framework.

Who the NCA ECC applies to, and what changed for private companies

The official scope statement in ECC-2:2024 names three groups: government agencies in the Kingdom (ministries, authorities, establishments and others), their affiliated companies and entities inside and outside the Kingdom, and all private sector entities owning, operating or hosting Critical National Infrastructure (CNI). The same document says the NCA “strongly encourages all other entities in the Kingdom to leverage these Controls.” The NCA’s statute also states that no public or private entity is relieved of responsibility for its own cybersecurity.

Two developments matter if you are a private company outside the CNI list:

  • Operational technology moved out of the ECC. ECC-1:2018 had a fifth domain for industrial control systems. ECC-2:2024 deleted it and moved those controls to the separate Operational Technology Cybersecurity Controls (OTCC). If you run a factory with PLCs and SCADA, the ECC covers your business network and the OTCC covers the plant floor.
  • A separate control set for the non-CNI private sector. According to policy trackers and law-firm summaries, the NCA adopted Non-CNI Private Sector Entities Cybersecurity Controls (NCNICC-1:2025) in late December 2025, with a lighter subset for small and medium entities and a fuller set for large ones. I could not verify the thresholds and control counts against the NCA’s own publication, so treat any numbers you read in vendor blogs as unconfirmed and check the NCA website before you plan around them.

For most mid-sized Saudi companies the practical reading is this: the ECC is the reference your regulators, customers and auditors recognize; the non-CNI controls are the floor you will be measured against; and the ECC roadmap below gets you to both.

How ECC-2:2024 is structured

The current version consists of 4 main domains, 28 subdomains, 108 main controls and 92 subcontrols (ECC-1:2018 had 5 domains, 29 subdomains and 114 controls). Control codes read domain-subdomain-control, so 2-9-3 is the third main control of Backup and Recovery Management in the Defense domain. The table below lists every subdomain, because the subdomain is the right unit for planning a gap assessment.

Main domain Subdomains What it means for a mid-sized company
1. Cybersecurity Governance (10) 1-1 Strategy; 1-2 Management; 1-3 Policies and Procedures; 1-4 Roles and Responsibilities; 1-5 Risk Management; 1-6 Cybersecurity in IT Project Management; 1-7 Compliance with Standards, Laws and Regulations; 1-8 Periodical Review and Audit; 1-9 Human Resources; 1-10 Awareness and Training Paper and ownership: who is accountable, which policies exist, how risks are tracked, how staff are screened and trained
2. Cybersecurity Defense (15) 2-1 Asset Management; 2-2 Identity and Access Management; 2-3 Information Systems and Processing Facilities Protection; 2-4 Email Protection; 2-5 Network Security Management; 2-6 Mobile Devices Security; 2-7 Data and Information Protection; 2-8 Cryptography; 2-9 Backup and Recovery; 2-10 Vulnerability Management; 2-11 Penetration Testing; 2-12 Event Logs and Monitoring; 2-13 Incident and Threat Management; 2-14 Physical Security; 2-15 Web Application Security The technical controls: this is where most of the budget and most of the gaps are
3. Cybersecurity Resilience (1) 3-1 Cybersecurity Resilience Aspects of Business Continuity Management Can the business keep running and recover after an incident
4. Third-Party and Cloud Computing Cybersecurity (2) 4-1 Third-Party Cybersecurity; 4-2 Cloud Computing and Hosting Cybersecurity Contracts, outsourcing and cloud: 4-2 is binding only on entities that use or plan to use cloud and hosting services

One change deserves a flag for voluntary adopters: control 1-2-2 now requires all cybersecurity positions to be filled by full-time, qualified Saudi cybersecurity professionals (ECC-1 limited this to the head of function and critical positions). Outside the mandatory scope, treat it as a staffing target, not a reason to delay the technical controls.

How the NCA measures compliance

The ECC document states that the NCA evaluates compliance through self-assessment by the entities, periodic reports from the compliance tool, and field audit visits, and that it issues an ECC-2:2024 Assessment and Compliance Tool to organize the process. Subdomain 1-8 also requires the entity’s own cybersecurity function to review implementation periodically and to have it reviewed and audited by parties other than the cybersecurity department, independently and with conflict of interest in mind, with results documented and presented to management.

For a company outside the mandatory scope, the same mechanism is useful internally: run a self-assessment per subdomain, score each control as implemented, partially implemented, not implemented or not applicable, and present the result to the board once a year. That single artifact answers the “are we compliant” question better than any certificate.

The NCA ECC checklist: a phased roadmap for a private company

The order below is the one I would follow in a company that is starting with little documentation and a small team. It front-loads the controls that stop the common incidents (phishing, ransomware, lost laptops, departed staff with live accounts) and leaves the expensive items for when the basics are stable.

  1. Define scope and ownership (1-2, 1-4). Decide who the cybersecurity function reports to; control 1-2-1 requires the cybersecurity department to be independent of the IT department and recommends that it report to the head of the entity or a delegate. Name that authorized official (typically the CEO or a board member), get written approval for the program, and list the systems, sites and third parties in scope.
  2. Build the asset inventory (2-1). Every server, endpoint, network device, cloud subscription, application and data set, with an owner and a classification. Nothing else in the ECC can be evidenced without this list.
  3. Write the policy set (1-3, 1-5, 1-9, 1-10). Cybersecurity policy, acceptable use, access control, data classification, backup, incident response, third-party security, HR security (screening, onboarding, offboarding) and awareness. Each policy needs an owner, an approval date and a review cycle. Templates get you started; the policy is only real when the procedure under it is followed.
  4. Fix identity and access (2-2). Single identity source, multi-factor authentication for remote access, email and privileged accounts, named administrator accounts, a quarterly access review signed by system owners, and offboarding within the same day the person leaves.
  5. Harden email and endpoints (2-3, 2-4, 2-6). Anti-malware and endpoint detection on every device, patching with a defined window, SPF, DKIM and DMARC on your domains, attachment and link filtering, full-disk encryption on laptops and a mobile device policy.
  6. Segment and monitor the network (2-5, 2-12). Separate guest, office, server and production networks; firewall rules with a documented purpose; central log collection for servers, firewalls, identity and email, with someone actually reviewing alerts.
  7. Make backups provably restorable (2-9). Backups for every in-scope system, at least one copy offline or immutable, and a documented restore test on a schedule. The ECC asks explicitly for periodic testing of restore effectiveness; a backup that has never been restored is a hope, not a control.
  8. Run vulnerability management and penetration tests (2-10, 2-11). Periodic scanning with a remediation SLA by severity, and periodic penetration testing of internet-facing systems by a qualified party.
  9. Prepare for incidents and continuity (2-13, 3-1). An incident response plan with roles, escalation, evidence handling and reporting lines, and a business continuity view that identifies critical systems and their recovery targets.
  10. Bring third parties and cloud under control (4-1, 4-2). Security clauses in contracts, a register of vendors with access to your systems, review of where cloud data is hosted, and a documented exit path from each provider.
  11. Review, audit and report (1-7, 1-8). Annual self-assessment, independent review, a compliance register of the laws that apply to you (the Personal Data Protection Law, ZATCA e-invoicing rules and sector regulations), and a one-page cybersecurity report to the board.

If you are also building the IT function itself, the sequence above fits inside the phases I describe in building an IT department from scratch: governance and policies come after infrastructure stabilizes, not before.

Where to start if you only have ninety days

A gap assessment usually produces a list far longer than a small team can clear in a year. A simple decision rule picks the first wave: do first any control whose absence would let one phishing email become a company-wide outage (MFA, endpoint protection, offline backups with a tested restore, removal of shared and dormant accounts); do second whatever an auditor or major customer will ask for in writing (approved policies, the asset inventory, the risk register, the incident response plan); schedule the controls that need budget cycles or specialists; and mark not applicable, with a written reason, anything that genuinely does not apply.

Mistakes that make NCA ECC compliance fail

  • Buying policies instead of writing procedures. A forty-page policy pack downloaded from a consultant satisfies 1-3 on paper and nothing else. Auditors and attackers both test the procedure, not the policy.
  • Treating the ECC as an IT project. Domains 1, 3 and 4 need HR, legal, finance and operations. If the authorizing official is the IT manager, the program has no authority over the departments that generate most of the risk.
  • Skipping the asset inventory because “we know what we have.” Every later control depends on it, and the first vulnerability scan will find devices nobody listed.
  • Confusing ECC scope with OTCC scope in a factory. Production networks need the OTCC’s controls; applying office-style patching windows to a PLC is how you stop a line.
  • Backups without restore tests. The control is not “backups exist”; it is “recovery has been tested and the result recorded.”

Key takeaways

  • ECC-2:2024 is mandatory for government agencies, their affiliates and CNI operators, and strongly encouraged for everyone else; separate NCA controls now target the non-CNI private sector.
  • The structure is 4 domains, 28 subdomains, 108 main controls and 92 subcontrols; plan your gap assessment at subdomain level.
  • Industrial control systems left the ECC in version 2 and live in the OTCC; factories need both.
  • Compliance is assessed by self-assessment, compliance-tool reports and field audits, so build the self-assessment file from day one.
  • Sequence the work: ownership and asset inventory first, then identity, email, endpoints and backups, then the budget-heavy controls.
  • Policies are only evidence when the procedures beneath them are followed and reviewed.

Frequently asked questions

Is NCA ECC compliance mandatory for private companies in Saudi Arabia?

The ECC is mandatory for government agencies, their affiliated companies and private entities that own, operate or host Critical National Infrastructure. Other private companies are strongly encouraged to adopt it, and the NCA has since issued separate cybersecurity controls aimed at non-CNI private sector entities. Check the NCA website for the current scope and any notification that applies to your company.

How many controls are in the NCA ECC?

ECC-2:2024 contains 108 main controls and 92 subcontrols, organized into 4 main domains and 28 subdomains. The previous version, ECC-1:2018, had 114 controls across 5 domains and 29 subdomains; the industrial control systems domain was removed and its content moved to the Operational Technology Cybersecurity Controls.

What is the difference between the ECC and the OTCC?

The ECC sets the minimum cybersecurity requirements for an organization’s information and technology assets in general. The OTCC extends it for operational technology such as PLCs, SCADA and industrial networks. In ECC-2:2024 the old ICS domain was deleted, so a manufacturer applies the ECC to business IT and the OTCC to the production environment.

What changed between ECC-1:2018 and ECC-2:2024?

Version 2 clarified that affiliated government companies inside and outside the Kingdom are in scope, removed the industrial control systems domain in favor of the OTCC, consolidated overlapping controls, reduced the count from 114 to 108, and tightened the staffing requirement so that all cybersecurity positions are filled by full-time, qualified Saudi professionals.

Does the ECC require a CISO?

The ECC requires a cybersecurity function with defined roles, an authorizing official and, in ECC-2:2024, full-time qualified Saudi professionals in cybersecurity positions. In a mid-sized company this is often a cybersecurity lead inside IT with a direct reporting line to executive management, rather than a separate CISO office. What matters is documented accountability and independence of review.

If you are planning an ECC gap assessment or need the policies, procedures and evidence file built in a way your board and auditors will accept, I can help you scope it as part of a wider digital transformation and IT governance program. The official control text is published by the NCA as ECC-2:2024 (English version), with the Arabic version as the binding text. Get in touch to discuss where your company stands.

Cart 0 Checkout