Compliance
NCA ECC Compliance Checklist for Saudi Companies
The NCA Essential Cybersecurity Controls are the baseline for Saudi government entities, critical infrastructure, and the companies that supply them. Here is who must comply, what the controls cover, and a practical readiness checklist.
EclipticLink Security Team8 min read
The Essential Cybersecurity Controls (ECC) from Saudi Arabia's National Cybersecurity Authority (NCA) define the minimum cybersecurity requirements for organizations that matter most to the Kingdom's security and economy. As Vision 2030 moves more services online, ECC requirements increasingly appear in contracts for software vendors, IT service providers, and consultancies too.
This guide explains who must comply, what the controls cover, and how to prepare, with a checklist you can work through.
Who must comply?
- Government organizations inside and outside the Kingdom, including ministries, authorities, and their companies and entities.
- Private-sector organizations that own, operate, or host critical national infrastructure (CNI).
- Suppliers, in practice: government and CNI organizations must manage third-party risk, so they pass ECC requirements to vendors through contracts and security questionnaires.
Not government or CNI? In December 2025 NCA adopted the Non-CNI Private Sector Entities Cybersecurity Controls (NCNICC-1:2025), a separate baseline for private companies outside critical national infrastructure, with requirements scaled by company size. Check whether it applies to you; much of this checklist is still relevant.
If you sell technology or services to Saudi government or critical-infrastructure clients, plan for ECC requirements, even if you are not directly in scope.
What the ECC covers
The current version, ECC-2:2024, groups the controls into four main domains. Industrial control system controls, a separate domain in the 2018 version, now sit in NCA's Operational Technology Cybersecurity Controls. Always check the latest version on NCA's website:
| Domain | What it includes |
|---|---|
| Cybersecurity governance | Strategy, cybersecurity function and roles, policies, risk management, compliance reviews, HR security, awareness and training |
| Cybersecurity defense | Asset management, identity and access, system and network protection, email security, mobile and data protection, cryptography, backups, vulnerability management, penetration testing, logging and monitoring, incident management, physical security, web application security |
| Cybersecurity resilience | Cybersecurity in business continuity management |
| Third-party and cloud cybersecurity | Security requirements for suppliers, outsourcing, and cloud and hosting services |
Related NCA control frameworks
The ECC is the baseline. Depending on your situation, NCA's more specific frameworks may also apply, such as the Non-CNI Private Sector Entities Cybersecurity Controls (NCNICC), the Cloud Cybersecurity Controls (CCC) for cloud providers and customers, the Critical Systems Cybersecurity Controls (CSCC), the Data Cybersecurity Controls (DCC), the Operational Technology Cybersecurity Controls (OTCC), and the Telework Cybersecurity Controls (TCC).
NCA ECC readiness checklist
Governance
- Cybersecurity strategy approved by leadership and aligned with business goals
- A dedicated cybersecurity function independent of IT, with cybersecurity positions filled by qualified, full-time Saudi professionals
- Cybersecurity policies and procedures approved, published, and reviewed periodically
- Documented cybersecurity risk assessment and treatment plan
- Cybersecurity requirements built into projects and change management
- Security awareness and training program for all staff
Defense
- Complete, maintained inventory of information and technology assets
- Identity and access management with MFA for remote and privileged access
- Hardened systems, network segmentation, and email protection
- Data classification, protection, and approved cryptography
- Tested backups for critical systems
- Vulnerability management with defined remediation timelines
- Periodic penetration testing of external and critical systems
- Centralized security event logging and monitoring
- Documented incident response process and reporting to NCA where required
Resilience
- Cybersecurity requirements included in business continuity and disaster recovery plans
- Continuity plans tested and updated after exercises
Third parties and cloud
- Cybersecurity clauses in supplier and outsourcing contracts, including confidentiality and incident notification
- Supplier security assessments before onboarding and periodically after
- Cloud and hosting arrangements that meet ECC cloud controls and any NDMO or sector data-residency rules
Common gaps we see
- No independent cybersecurity function, with security sitting informally inside IT, or roles not staffed as the ECC requires.
- Policies copied from templates that do not match real practice.
- Incomplete asset inventories, especially for cloud and SaaS.
- Penetration testing done once, not periodically, and findings not tracked to closure.
- Supplier contracts with no cybersecurity requirements.
- Evidence scattered across emails and shared drives instead of organized per control.
How to prepare: a practical sequence
- Confirm your scope: directly regulated, or bound through client contracts.
- Download the latest ECC from NCA and assign an owner to every control.
- Run a gap assessment and rank gaps by risk and effort.
- Fix governance foundations first: the cybersecurity function, strategy, and policies.
- Close technical gaps: access, logging, vulnerabilities, backups, and testing.
- Organize evidence per control so you are ready for NCA compliance assessments and client audits.
Key takeaways
- The ECC applies directly to government and CNI organizations, and indirectly to many of their suppliers. Other private companies should check NCNICC-1:2025.
- It covers governance, defense, resilience, and third-party and cloud security.
- Governance gaps, such as an independent cybersecurity function and real policies, are the most common blockers.
- Work from the latest NCA version, and keep evidence organized per control.
EclipticLink supports Saudi organizations with NCA ECC gap assessments and remediation, penetration testing, and ongoing monitoring. See our cybersecurity services in Saudi Arabia. This guide is general information, not legal advice; always confirm requirements against NCA's official publications.
Frequently asked questions
Who must comply with the NCA ECC?
Government organizations inside and outside Saudi Arabia, their companies and entities, and private-sector organizations that own, operate, or host critical national infrastructure. Other private companies may fall under NCA's Non-CNI Cybersecurity Controls (NCNICC-1:2025), and many meet ECC requirements because government and CNI clients include them in contracts.
Where can I get the latest version of the ECC?
Download it from the National Cybersecurity Authority's official website. NCA updates its control frameworks over time, so always work from the current version before starting a gap assessment.
Does the ECC require data to stay in Saudi Arabia?
ECC-2:2024 removed the explicit in-country hosting requirement that appeared in the 2018 version. Data localization is now governed mainly by SDAIA's National Data Management Office (NDMO), existing rules on hosting government data, sector regulators, and the Personal Data Protection Law, so localization obligations may still apply. Check these rules for your data before choosing cloud regions.
How is the ECC different from the SAMA Cyber Security Framework?
The ECC is the national baseline set by NCA. The SAMA Cyber Security Framework applies specifically to financial institutions regulated by the Saudi Central Bank. Some financial institutions need to address both.
- NCA ECC
- Essential Cybersecurity Controls
- NCA compliance
- Saudi cybersecurity regulations
- ECC checklist
- Saudi Arabia cybersecurity