We e-mail the editable toolkit files to the address you gave, usually within 2 to 3 business days.
Cyber Security

ECC-1:2018 Explained: What the NCA Essential Cybersecurity Controls Require

ECC-1:2018 Explained: What the NCA Essential Cybersecurity Controls Require
In short

A practical guide to NCA ECC-1:2018: who it applies to, the five domains, the documents and evidence you need, and how to plan implementation.

In this article
  1. What ECC-1:2018 is and who it applies to
  2. How the framework is structured
  3. What documentation and evidence you need
  4. A practical implementation path
  5. Common mistakes to avoid
  6. How ECC relates to other frameworks
  7. Frequently asked questions

If you work with Saudi government bodies or critical infrastructure operators, you will have come across ECC-1:2018. It is the Essential Cybersecurity Controls framework issued by the National Cybersecurity Authority (NCA) of Saudi Arabia. It sets the minimum cybersecurity baseline that in-scope organizations are expected to meet.

This article explains what ECC-1:2018 is, who it applies to, how it is structured, and how to approach implementation without drowning in paperwork.

What ECC-1:2018 is and who it applies to#

ECC-1:2018 is a set of mandatory cybersecurity controls. The NCA developed it after studying earlier cybersecurity standards, frameworks and regulations, so it will feel familiar if you know ISO 27001 or similar standards. It is not a certificate you buy. It is a national requirement you must show you meet, and the NCA can assess you against it.

In general terms, it applies to:

  • Government organizations in Saudi Arabia, including ministries, authorities and establishments, and their companies and entities.
  • Private sector organizations that own, operate or host Critical National Infrastructure (CNI).

The NCA also encourages other organizations to adopt it. If you serve in-scope clients as a supplier or cloud provider, expect them to ask how you align with it.

A note on versions: the NCA has since published an updated edition of the ECC. Always confirm with the NCA which version applies to your organization and what transition expectations exist. The principles below carry across, but control wording and numbering can change between versions.

How the framework is structured#

ECC-1:2018 is organized into five main domains. Each domain contains subdomains, and each subdomain contains individual controls.

DomainWhat it covers
Cybersecurity GovernanceStrategy, policies, roles and responsibilities, risk management, project and change security, compliance, review and audit, HR security, awareness and training
Cybersecurity DefenseAsset management, identity and access management, system and network protection, email, mobile devices, data and information protection, cryptography, backup, vulnerability management, penetration testing, logging and monitoring, incident management, physical security, web application protection
Cybersecurity ResilienceCybersecurity aspects of business continuity management and disaster recovery
Third-Party and Cloud Computing CybersecuritySecurity requirements for suppliers, outsourcing, managed services and cloud hosting
Industrial Control Systems (ICS) CybersecurityProtection of operational technology environments, where relevant

The ICS domain only matters if you run industrial or operational technology. The other four apply to nearly every in-scope organization.

The framework also expects controls to be documented, approved, implemented and reviewed. Many controls ask for a documented policy or procedure, and a separate control asks you to put it into practice. An auditor will look for both.

What documentation and evidence you need#

Most of the effort in ECC work is producing and maintaining the right documents, then proving they are used. A typical set includes:

  • Cybersecurity strategy and roadmap, aligned with business objectives and approved by management.
  • Policies for each major control area, such as access control, acceptable use, backup, cryptography, logging, and third-party security.
  • Procedures and standards that explain how each policy is carried out in practice.
  • Roles and responsibilities, including a defined cybersecurity function and a steering committee or equivalent oversight body.
  • Risk assessment methodology, risk register and treatment plans.
  • Asset inventory covering information and technology assets.
  • Incident response plan and records of incidents handled.
  • Business continuity and disaster recovery plans with test records.
  • Third-party and cloud security requirements built into contracts and onboarding checks.
  • Awareness and training records.

Evidence is as important as documents. Examples include access review records, vulnerability scan reports, penetration test reports, log review samples, backup restore tests, management meeting minutes and approval records. A policy with no evidence of operation is a common weak point.

If you are weighing whether to build your documents from scratch or start from a template pack, our guide to what to look for in an NCA ECC documentation pack covers the quality checks worth making.

A practical implementation path#

You do not need to tackle every control at once. A sequence that works for most teams:

  1. Confirm scope and applicability. Decide which systems, sites, business units and suppliers are in scope, and whether the ICS domain applies. Write this down.
  2. Run a gap assessment. Map each control to your current state: implemented, partly implemented, not implemented, or not applicable with a justification. This becomes your work plan.
  3. Secure management commitment. The governance domain expects leadership approval and oversight. Get named owners and a reporting rhythm in place early.
  4. Close documentation gaps first. Policies and procedures are the quickest wins and give your technical teams a clear standard to implement against.
  5. Implement technical and operational controls. Prioritize by risk. Identity and access, logging and monitoring, vulnerability management, backup and incident response usually need the most work.
  6. Address third parties. Review contracts and cloud arrangements for security clauses, and keep a register of suppliers with access to your data or systems.
  7. Test, review and fix. Run an internal assessment against the controls, test your incident and recovery plans, and correct findings before any external review.
  8. Keep it running. Schedule periodic reviews of policies, risk assessments, access rights and supplier compliance.

Common mistakes to avoid#

  • Copying generic policies without tailoring them. Assessors check whether documents reflect how you actually operate.
  • Treating it as an IT-only project. HR, legal, procurement, facilities and business owners all hold controls.
  • Ignoring third parties. Supplier and cloud controls are a distinct domain, not an afterthought.
  • No evidence trail. If you cannot show a review happened, assume it will be treated as not done.
  • One-off effort. Controls need periodic review, so assign ongoing owners.

How ECC relates to other frameworks#

If you already hold ISO 27001 certification, you will likely have a head start on risk management, access control, logging, incident response and supplier management. Do not assume equivalence, though. ECC has its own control wording, its own expectations and national requirements, so map each control explicitly instead of relying on your existing certificate. Organizations that also serve European clients may be looking at NIS 2 documentation requirements as well, and the same core records can often be reused across both.

Frequently asked questions#

Is ECC-1:2018 mandatory?#

It is mandatory for the organizations the NCA has placed in scope, namely government entities and private sector owners, operators or hosts of Critical National Infrastructure. Other organizations may adopt it voluntarily or because clients require it. Confirm your own status with the NCA or your regulator.

Is ECC-1:2018 the same as ISO 27001?#

No. They overlap in many areas, but ISO 27001 is an international management system standard with a certification scheme. ECC is a national control framework with specific requirements set by the NCA. Having one helps with the other, but it does not replace it.

Has ECC-1:2018 been replaced?#

The NCA has published a later version of the Essential Cybersecurity Controls. Check the NCA's current guidance to see which version applies to you and what transition timeline, if any, has been set. Your gap assessment should be based on the version your regulator expects.

If you are starting an ECC programme and want help scoping it or structuring your documentation, you can talk to the AdWiser team.

Share this guide

Need help with your next audit?

Our consultants can assess your gaps and guide you to certification.

Chat on WhatsApp