NCA ECC Compliance in Saudi Arabia: Who Must Comply, Costs and Timelines
Selling to a Saudi ministry, bank or utility? ECC obligations will reach you through the contract. Here's who's in scope, how ECC maps to ISO 27001 and PDPL, and what a realistic budget and timeline look like.
Who NCA ECC compliance reaches, directly and through contracts
If a Saudi government entity, a state-owned company or a critical infrastructure operator has sent you a security questionnaire that cites "ECC" control numbers, you're already in scope for NCA ECC compliance, whether or not you have an office in the Kingdom. The real questions are how far the obligation goes and what it will cost to meet.
The National Cybersecurity Authority (NCA) issued the Essential Cybersecurity Controls in 2018 and later published a revised edition, ECC-2:2024. The controls apply directly to three groups:
- Government organizations: ministries, authorities, establishments and their affiliated bodies.
- Companies and entities owned or controlled by government, including many large state-linked enterprises in energy, utilities, transport and industry.
- Private-sector organizations that own, operate or host Critical National Infrastructure (CNI), such as operators in energy, water, healthcare, telecoms, finance and transport.
For everyone else, ECC is voluntary in principle, and the NCA encourages broad adoption. The bigger effect comes from the third-party domain. In-scope entities have to set cybersecurity requirements in their supplier contracts: confidentiality, incident notification, the right to assess, secure data handling and, for cloud services, where data is hosted. Those requirements then pass down to IT service providers, managed security firms, SaaS vendors, integrators and outsourcers. That's what NCA compliance for vendors means in practice: you're contractually bound to controls written for your customer.
Several companion frameworks sit alongside ECC, and buyers often confuse them. The Cloud Cybersecurity Controls (CCC) apply to cloud providers and the tenants that use them. The Critical Systems Cybersecurity Controls (CSCC) add stricter requirements for systems an entity classifies as critical. The Operational Technology Cybersecurity Controls (OTCC) cover industrial environments. Sector regulators add their own layers: the Saudi Central Bank (SAMA) has a cybersecurity framework for financial institutions, and the Communications, Space and Technology Commission (CST) regulates telecoms and cloud licensing. A bank vendor may answer to SAMA's framework and ECC-derived contract clauses at once.
A quick scoping test
Answer three questions. Is your customer a government body, a state-owned entity or a CNI operator? Will you store, process or access their data or systems? Will any of that happen in the cloud? Two yeses mean you should plan for ECC-aligned contract terms. Three yeses usually add CCC obligations and data-residency requirements.
What the Saudi Essential Cybersecurity Controls require, mapped to ISO 27001
The Saudi Essential Cybersecurity Controls are organized into main domains, subdomains and individual controls. The core domains are Cybersecurity Governance, Cybersecurity Defense, Cybersecurity Resilience, and Third-Party and Cloud Computing Cybersecurity. Industrial control system requirements, once part of ECC, now sit mainly in the OTCC. Work from the current official NCA text, because numbering changed between editions and many customer questionnaires still cite the 2018 numbers.
If you already hold ISO 27001 certification, most ECC topics have a matching Annex A control. The catch is that ECC is more prescriptive. ISO lets you pick controls based on your own risk assessment. ECC mandates them and adds Saudi-specific conditions.
| ECC area | Closest ISO 27001:2022 coverage | Typical gap for an ISO-certified firm |
|---|---|---|
| Cybersecurity governance, strategy and roles | Clauses 4-6, A.5.1-A.5.4 | Cybersecurity function independent of IT; Saudization expectations for the head of cybersecurity |
| Regulatory compliance and periodic review | A.5.31, A.5.35, A.5.36 | Formal reporting against ECC and NCA assessment cycles |
| Asset, identity and access management | A.5.9-A.5.18, A.8.2-A.8.5 | Usually minor: tighter privileged access review frequencies |
| Vulnerability management and penetration testing | A.8.8, A.8.29 | Defined testing frequencies and scope for internet-facing and critical systems |
| Logging, monitoring and incident management | A.5.24-A.5.28, A.8.15-A.8.16 | Log retention minimums and incident notification paths |
| Resilience and business continuity | A.5.29-A.5.30 | Cyber-specific continuity testing tied to critical services |
| Third-party and cloud cybersecurity | A.5.19-A.5.23 | In-Kingdom data hosting for in-scope cloud use; mandatory contract clauses |
Two gaps catch foreign vendors more than any others. The first is data residency. ECC's cloud controls generally expect in-scope entities to host and store their information inside Saudi Arabia, so a vendor running only from Frankfurt, Virginia or Singapore will struggle to win government work. The second is Saudization of the cybersecurity leadership role. That rule binds the in-scope entity, not necessarily its suppliers. But a local subsidiary that becomes a CNI operator, or that runs a managed service as the customer's de facto cybersecurity function, will face it head-on.
Our position: if you sell into the Kingdom regularly, keep ISO 27001 certification and add an ECC delta assessment on top. Don't build a separate ECC program from scratch. ISO gives procurement teams a recognized baseline, and a clean mapping document answers most questionnaire items with evidence you already produce.
Where Saudi PDPL compliance overlaps with ECC, and where it doesn't
The Personal Data Protection Law (PDPL) took effect in September 2023, with a grace period for enforcement that ran about a year. It's regulated by the Saudi Data and Artificial Intelligence Authority (SDAIA), not the NCA. So Saudi PDPL compliance and ECC are two obligations with two regulators, even though they touch the same systems.
The overlap is real but partial. ECC's controls on encryption, access management, logging and incident response go a long way toward the security measures PDPL expects of controllers and processors. A mature ECC program will meet most of PDPL's security expectations.
What ECC does not cover:
- Lawful basis and purpose limitation: why you collect personal data and whether you're allowed to.
- Data subject rights: access, correction, destruction and the right to be informed, with defined response handling.
- Breach notification to SDAIA: the implementing regulations set a short notification deadline, commonly cited as 72 hours from awareness of a qualifying breach, and in some cases require notifying affected individuals. Confirm the current wording with local counsel. It's a separate track from any NCA incident reporting.
- Cross-border transfers: PDPL's transfer rules allow transfers outside the Kingdom under defined conditions, such as adequate protection, safeguards or specific exceptions. For government-linked data, ECC's residency expectations are usually stricter than PDPL alone.
- Records of processing, privacy notices and, where required, a data protection officer and registration.
PDPL penalties are significant: fines in the millions of Saudi riyals per violation, higher for repeat offenses, and possible imprisonment for disclosing sensitive data with intent to harm. Treat those as statutory ceilings, not typical outcomes, and have a licensed Saudi legal adviser confirm how they apply to your processing.
For foreign vendors, GDPR experience transfers well. Rights handling, processing records and data processing agreements look familiar. Transfer rules and regulator notifications don't, so they need Saudi-specific procedures. If you already run a GDPR program in Europe, or comply with India's DPDP Act or the UAE's federal data protection law, extend that program with a Saudi annex rather than starting a separate one.
Indicative costs and timelines for local entities and foreign vendors
Costs depend mostly on four things: how many ECC controls genuinely apply, how much evidence you already have from ISO 27001 or SOC 2, whether you need new in-Kingdom hosting, and whether you hire local staff or buy services. The figures below are typical 2026 market ranges in USD. They vary by contract, scope and provider, and local Saudi pricing from regional consultancies often differs from what global firms quote, so confirm with vendors before you budget.
| Cost item | Mid-size vendor (ISO 27001 in place) | Large in-scope entity or CNI operator | Typical duration |
|---|---|---|---|
| ECC gap assessment | $12,000-$40,000 | $50,000-$150,000 | 4-10 weeks |
| Policy and procedure set aligned to ECC | $10,000-$35,000 | $40,000-$120,000 | 6-12 weeks |
| Technical remediation (PAM, SIEM, EDR, vulnerability tooling) | $30,000-$200,000 per year | $300,000-$2M+ per year | 3-12 months |
| In-Kingdom hosting or a local cloud region | $2,000-$25,000 per month incremental | Often existing; migrations can run into seven figures | 2-9 months |
| Managed SOC with Saudi presence | $60,000-$250,000 per year | $250,000-$1M+ per year | 1-3 months to onboard |
| PDPL program extension | $15,000-$60,000 | $60,000-$200,000 | 2-5 months |
| ISO 27001 certification audit cycle | $8,000-$30,000 per cycle | $30,000-$90,000 per cycle | Stage 1 and 2 over 2-4 months |
On timelines, an ISO-certified vendor whose only ECC exposure is contractual can often be questionnaire-ready in 3 to 6 months. A government entity or CNI operator starting from a weak baseline should plan 12 to 24 months to reach a defensible position. Hosting migrations and hiring usually push it to the long end.
Worked example (hypothetical)
Say a 150-person European SaaS company with ISO 27001 wins a pilot with a Saudi government authority. The gap assessment finds about 20 partially met controls, mostly around log retention, penetration testing frequency and contract clauses. One blocker is serious: all customer data sits in an EU region. The company deploys into an in-Kingdom cloud region (several major global providers have launched or announced Saudi regions, and local providers are options too), engages a Riyadh-based managed security provider and adds a Saudi PDPL annex to its privacy program. First-year spend lands around $180,000-$350,000 and the work takes six to eight months. Without the hosting change, the deal would have stalled at procurement however good the rest of the evidence was.
Check region availability and CST classification for your specific workload directly with each provider. Availability and licensing status change, and not every service in a provider's catalog runs in its Saudi region.
Red flags and a sequencing plan for NCA compliance for vendors
ECC efforts tend to go wrong in the same few places. Watch for these when you hire advisers or answer customer assessments:
- A consultant who promises "NCA certification" for your company. The NCA oversees compliance of in-scope entities. It doesn't issue ISO-style certificates to ordinary vendors. Anyone selling a badge is overselling.
- Mapping documents built on the 2018 numbering with no reference to ECC-2:2024.
- Treating PDPL as covered by ECC. Different regulator, different notifications, different rights obligations.
- Accepting residency clauses you can't meet. Signing a contract that requires in-Kingdom hosting while your data still sits offshore is a breach waiting to happen.
- Ignoring sector overlays. A bank or telecom customer will layer SAMA or CST requirements on top of ECC-style terms.
- Uncapped liability for cyber incidents. Ask your broker whether your cyber policy covers contractual liability and regulatory investigations in Saudi Arabia, and whether the territory definition includes it.
Sequencing that works
- Confirm your role. Are you a directly in-scope entity, a cloud provider under CCC, or a supplier bound by contract? Get your customer to state which ECC, CCC and CSCC controls they're passing down.
- Run a delta assessment against your ISO 27001 or SOC 2 evidence instead of a from-scratch audit.
- Fix the structural blockers first: hosting location, local support presence and incident notification paths. These take longest.
- Extend your privacy program for PDPL transfers, SDAIA breach notification and data subject rights.
- Negotiate the contract with counsel licensed in Saudi Arabia, aligning liability, audit rights and notification windows with what you can actually deliver.
- Keep evidence on a calendar. Penetration tests, access reviews and continuity tests should run at the frequencies ECC specifies, so the next assessment takes days, not months.
Here's the decision rule: if expected Saudi public-sector or CNI revenue clearly exceeds the cost of an in-Kingdom hosting footprint and a local security partner (roughly $150,000-$300,000 a year for a mid-size vendor, by the ranges above), make the investment now and compete properly. If it doesn't, sell only workloads that don't touch customer data, or go to market through a Saudi partner that already holds the hosting and compliance position.
Frequently asked questions
Does NCA ECC apply to private companies with no government customers?
Not directly, unless the company owns, operates or hosts Critical National Infrastructure. The NCA encourages all organizations to adopt ECC as good practice, and some large private buyers use it as a supplier baseline. In practice, a private company can end up meeting ECC-style requirements because its customers write them into contracts.
Can a foreign vendor get certified against ECC?
There's no ECC certificate for ordinary vendors comparable to an ISO 27001 certificate. The NCA oversees compliance of in-scope entities, and those entities assess their suppliers against the controls they pass down. Vendors usually prove alignment through ISO 27001 certification, an ECC mapping document, independent assessment reports and contractual commitments.
Is ISO 27001 enough to satisfy Saudi buyers?
It covers much of the ground but rarely all of it. ECC adds prescriptive requirements that ISO leaves to your risk assessment, such as in-Kingdom data hosting for in-scope cloud use, specific testing and log retention expectations, and Saudi incident reporting paths. Treat ISO 27001 as the foundation and close the remaining gaps with a documented ECC delta.
Do we have to store data inside Saudi Arabia?
If your customer is a government entity or CNI operator subject to ECC and CCC, expect a requirement to host and store their information in the Kingdom. PDPL on its own allows some cross-border transfers under defined conditions, but government-linked contracts usually apply the stricter ECC position. Confirm the exact requirement for your data classification with the customer and with licensed local counsel.
How long does it take to become ECC-ready?
An ISO-certified vendor facing contractual ECC requirements can often be ready in 3 to 6 months, longer if a hosting migration is needed. Directly in-scope entities starting from a low baseline typically need 12 to 24 months. Hiring, security tooling procurement and data migrations usually set the pace.
Does cyber insurance cover ECC or PDPL penalties?
It depends on the policy wording and on local law. Some regulatory fines may not be insurable in a given jurisdiction, while investigation costs, breach response and third-party liability are more commonly covered. Ask a licensed broker to confirm territorial scope, contractual liability coverage and the regulatory sublimits for Saudi exposure.
Written by the Auditcover Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.