Saudi Arabia’s National Cybersecurity Authority (NCA) regulates cybersecurity for government bodies and critical national infrastructure. Its approach is a baseline plus add-ons: every regulated organisation implements the Essential Cybersecurity Controls (ECC), then adds specialised control sets depending on whether it runs cloud services, handles sensitive data, operates critical systems or controls industrial equipment. The obligations reach suppliers too, which is why NCA compliance now appears in contracts signed by Indian IT services and cloud companies.
1 · The Control Family
| Control set | Covers | Applies to |
|---|---|---|
| ECC — Essential Cybersecurity Controls (ECC-2:2024) | The national minimum: governance, defence, resilience, third-party and cloud | Government organisations and critical national infrastructure operators, and the parties that serve them |
| CCC — Cloud Cybersecurity Controls | Extra controls for cloud service providers and for organisations using cloud | CSPs serving regulated entities, and those entities as cloud customers |
| DCC — Data Cybersecurity Controls | Protecting data across its lifecycle by classification level | Organisations handling classified or sensitive data |
| CSCC — Critical Systems Cybersecurity Controls | Stronger controls for systems whose failure would have national impact | Owners of designated critical systems |
| OTCC — Operational Technology Cybersecurity Controls | Industrial control systems: segregation, remote access, safety-aware patching | Energy, water, manufacturing and other OT operators |
| Other sets | Narrower areas such as telework and organisations’ social-media accounts | As specified in each document |
▸ The 2024 revision moved the industrial control systems domain out of the ECC and into the OTCC, so the ECC is now a pure IT baseline and OT requirements live in one place.
2 · Inside the ECC Baseline
| Domain | What it requires |
|---|---|
| Governance | Strategy, a cybersecurity function independent of IT, policies, roles, risk management, cybersecurity in projects and HR, awareness, compliance reviews and periodic assessment |
| Defence | Asset management, identity and access, protecting systems and email, network and mobile security, data protection and cryptography, backup, vulnerability management, penetration testing, logging and monitoring, incident and threat management, physical security, web application security |
| Resilience | Cybersecurity aspects of business continuity |
| Third-party & cloud | Security requirements in supplier contracts, and in the use of cloud and hosting services, including data location |
ECC-2:2024 has 108 main controls (plus sub-controls) across 4 domains; the 2018 edition had 114 controls across 5. Control counts as reported for the published edition.
3 · Mapping to ISO 27001 and NIST CSF
If you already run an ISO 27001 ISMS or use NIST CSF, most of the ECC is familiar. The gaps are in what the ECC prescribes more precisely.
| ECC domain | ISO/IEC 27001:2022 | NIST CSF 2.0 | Where the ECC is stricter |
|---|---|---|---|
| Governance | Clauses 4–10; Annex A 5.1–5.4, 5.31–5.36 | Govern | A cybersecurity function separate from IT, reporting high enough to be independent |
| Defence | Annex A 5.9–5.18, 8.1–8.34 | Identify, Protect, Detect, Respond | Specific minimum settings and periodic testing requirements |
| Resilience | Annex A 5.29–5.30 | Recover | Explicit cybersecurity scenarios in continuity plans |
| Third-party & cloud | Annex A 5.19–5.23 | Govern (supply chain) | Data hosting and location expectations for regulated data |
For choosing between general frameworks, see Choosing a Security Framework; for the ISO controls themselves, ISO 27001:2013 → 2022.
4 · If You Supply Saudi Clients from India
- Ask which control sets the client is bound by — ECC always; CCC if you provide cloud; DCC if you handle their classified data; OTCC for industrial work.
- Map your ISMS to them — ISO 27001 evidence covers much of the ECC; record the gaps.
- Settle data location early — some regulated data must stay in the Kingdom; design hosting and support access around it.
- Expect contract clauses and assessments — security requirements, right to audit, incident notification, and evidence on request.
- Remember personal data — Saudi Arabia’s Personal Data Protection Law (PDPL), supervised by SDAIA, applies alongside, much as India’s DPDP Act does at home (see DPDP vs GDPR vs ISO 27701).
Bottom line
- Baseline plus add-ons — ECC for everyone, then CCC, DCC, CSCC, OTCC as the work requires.
- ECC-2:2024: 108 main controls in 4 domains; OT moved to the OTCC.
- ISO 27001 gets you most of the way; the ECC is more prescriptive on independence, settings and data location.
- Suppliers are in scope through contracts — Indian providers included.
- PDPL sits alongside for personal data.
Sources & method. National Cybersecurity Authority (nca.gov.sa) published control documents, including ECC-2:2024; control counts as reported for that edition. Applicability is summarised; each document defines its own scope. ISO 27001 and NIST CSF mappings are the author’s indicative analysis, not an official crosswalk. Saudi PDPL is administered by the Saudi Data & AI Authority (SDAIA). Not legal advice. Original analysis; no third-party graphics or text reproduced.
← Back to Cyber security