NCA ECC compliance, built for continuous audit readiness
Govrly gives Saudi government entities, regulators, and critical national infrastructure operators one connected system for NCA ECC compliance — every control mapped to an owner, an implementation status, and reviewed evidence, ready for assessment at any time.
- 4
- 28
- 108
- 92
This page reflects how we see these requirements applied in practice. It is not an official reference. The authoritative source is the current document published by the National Cybersecurity Authority (NCA), which may be revised — confirm what applies to your organisation against it and with your own advisers.
What is NCA ECC compliance?
From the compliance programmes we build and run in Saudi Arabia: NCA ECC compliance means implementing, sustaining, and evidencing the Essential Cybersecurity Controls issued by Saudi Arabia's National Cybersecurity Authority. The current edition, ECC-2:2024, is organised into 4 main domains, 28 subdomains, 108 main controls, and 92 sub-controls. It is a mandatory baseline — every applicable control needs a named owner, an implementation state, and defensible evidence.
ECC-2:2024 replaced ECC-1:2018, which was structured around 5 domains, 32 subdomains, and 114 controls. The restructure removed the standalone Industrial Control Systems domain, consolidated overlapping subdomains, and made two changes that materially affect operations: cybersecurity roles must be filled by qualified Saudi nationals, and data localisation authority moved to the National Data Management Office (NDMO) at SDAIA rather than sitting inside the ECC itself.
Compliance is assessable. In-scope entities are expected to maintain a current self-assessment, submit evidence through the NCA's national reporting channel, and remediate non-conformities within the timeframes set for them. That is why NCA ECC compliance is an operating model, not a document set.
Who must comply with the NCA ECC?
The Essential Cybersecurity Controls apply across the public sector and to the private organisations that underpin it.
Ministries, authorities, establishments, and agencies operating in the Kingdom.
Companies and entities affiliated with government bodies, whether operating inside or outside Saudi Arabia.
Private-sector organisations that own, operate, or host CNI, regardless of sector.
The NCA encourages every organisation in the Kingdom to adopt the ECC as best practice. In tender processes, alignment is frequently requested whether or not you are formally in scope.
The four ECC-2:2024 domains
Every domain maps to a working area of the platform, not a separate module you have to reconcile later.
Strategy, organisational structure, roles, policies, risk management, compliance, audit, and awareness. Govrly holds versioned documents with approval trails, plus a risk register with inherent and residual scoring.
Asset and identity management, network and system security, cryptography, backup and recovery, vulnerability management, penetration testing, logging, and incident response. Measures carry owners, status, and linked evidence.
Cybersecurity within business continuity management. Continuity measures, testing records, and evidence live in the same system as every other control, rather than in a separate BCM silo.
Third-party cybersecurity, outsourcing, managed services, and cloud hosting. Vendor inventory with agreements, certifications, assessments, and impact scoring, linked to the controls each vendor affects.
Why NCA ECC programs break down
Most ECC programs do not fail on intent. They fail on operations.
- 01/05Evidence is scattered
Across shared drives, email threads, and ad hoc submissions, so nobody can prove implementation on demand.
- 02/05Control ownership is unclear
A control has a policy but no accountable person, and remediation actions are tracked informally or not at all.
- 03/05Reporting is rebuilt by hand
For every management meeting and every assessment cycle, and it is usually stale by the time it is presented.
- 04/05Audit preparation becomes a project
A scramble every cycle instead of a continuous state.
- 05/05Parent entities have no normalised view
Because each entity reports in its own format, on its own schedule, against its own interpretation.
Running ECC compliance in Govrly

- A.
- Applicability set onceEach of the 108 main controls is marked applicable or excluded against your entity scope, with the reasoning attached to the record — which is what assessors question, far more often than the inclusions.
- B.
- A person, not a departmentEvery applicable control carries a named owner and a target date. Where no owner can be found during scoping, that gap surfaces immediately rather than at assessment.
- C.
- Collected as operations runEvidence is requested from the owner who produces it, reviewed before it counts, and given a validity period — so the submission is compiled from current records rather than assembled in the weeks beforehand.
- D.
- One control, four frameworksThe access control satisfying your ECC requirement carries your SAMA subdomain, your CST control and your ISO Annex A entry from the same record, each scored in its own framework's terms.
- E.
- Linked to the controls that treat itInherent and residual scoring, with each risk connected to the specific ECC controls reducing it — so the residual number has something testable behind it.
- F.
- Affiliates visible without merging themAffiliated entities keep isolated workspaces while the parent sees normalised posture across them, which matters because ECC scope extends to affiliates inside and outside the Kingdom.
NCA ECC vs SAMA CSF
Saudi entities are rarely measured against a single framework. Understanding where the ECC ends and sector regulation begins determines how much work you can reuse.
| Feature | NCA ECC | SAMA CSF |
|---|---|---|
| Issued by | National Cybersecurity Authority | Saudi Central Bank |
| Applies to | Government entities, affiliates, and critical national infrastructure | SAMA-supervised financial institutions |
| Current edition | ECC-2:2024 | Cyber Security Framework v1.0 |
| Scope | Cross-sector national baseline | Financial sector only |
| Assessment | Self-assessment plus NCA reporting | SAMA supervisory review |
| Managed in Govrly | Yes | Yes |
Do the work once, reuse it everywhere
Most Saudi entities are not measured against the ECC alone. Banks carry SAMA CSF. ICT and telecom licensees carry the CST CRF. Anyone processing personal data carries the Saudi PDPL. Cloud consumers and providers carry the NCA CCC on top of the ECC — the CCC is an extension, not a substitute.
These frameworks overlap heavily at the control level. In Govrly, controls, measures, and evidence are shared objects. Implement access control once and satisfy the ECC requirement, the SAMA CSF requirement, and the ISO 27001:2022 Annex A control from the same record, with the same evidence and the same owner.
A practical path to NCA ECC compliance
Most organisations we work with take six to eighteen months to reach full implementation, depending on size, existing control maturity, and internal resourcing.
- 01/07Define scope
Confirm which entities, systems, and e-services fall inside the ECC boundary, and record the reasoning behind every inclusion and exclusion.
- 02/07Run a gap assessment
Score each control across all four domains as implemented, partially implemented, not implemented, or not applicable — with written justification for every exclusion.
- 03/07Assign ownership
Every applicable control gets a named owner and a target date. A department is not an owner.
- 04/07Close the documentation layer
Strategy, policies, standards, and procedures — approved, versioned, and traceable to the controls they support.
- 05/07Collect and review evidence
Link evidence to each control, with a reviewer distinct from the owner wherever the structure allows it.
- 06/07Remediate to verification
Track corrective actions to verified closure, not to "in progress". A finding closes when someone confirms it, not when someone reports it.
- 07/07Operate continuously
Snapshot posture, re-test, and keep the self-assessment current between assessment cycles.
Every applicable ECC control sits in one library with a named owner, an implementation status and the evidence behind it — and the same control carries your SAMA, CST or ISO 27001 requirement at the same time. Scope once, evidence once, report to each authority in its own format.
NCA ECC compliance FAQs
ECC-2:2024 contains 108 main controls and 92 sub-controls across 28 subdomains. The previous edition, ECC-1:2018, contained 114 controls across 32 subdomains and 5 domains.
Yes, for government entities and their affiliates, and for private-sector organisations that own, operate, or host Critical National Infrastructure. The NCA encourages all other entities in the Kingdom to adopt the controls voluntarily, and government procurement frequently requires evidence of alignment regardless of formal scope.
The framework moved from 5 domains to 4, with the Industrial Control Systems domain restructured and subdomains consolidated. Cybersecurity roles must now be filled by qualified Saudi nationals, and data localisation is directed by the National Data Management Office at SDAIA rather than by the ECC document itself.
Cybersecurity Governance; Cybersecurity Defense; Cybersecurity Resilience; and Third-Party and Cloud Computing Cybersecurity.
The NCA ECC is the cross-sector cybersecurity baseline for government entities and critical national infrastructure. SAMA CSF is the financial-sector framework issued by the Saudi Central Bank and applies only to SAMA-supervised entities. They overlap substantially at the control level, but each has its own supervisor, assessment cadence, and evidence expectations.
Typically six to eighteen months to full implementation, depending on organisational size, existing control maturity, and internal resourcing. Organisations with an established ISO 27001 program usually reach readiness sooner because much of the required evidence already exists.
ECC-2:2024 does not itself set the data localisation rule. That authority sits with the National Data Management Office at SDAIA, and entities should consult NDMO guidance alongside any sector-specific requirements to determine their residency obligations.
Every applicable control needs demonstrable proof of implementation — approved policies and procedures, configuration records, logs, test results, training records, assessment reports, and records of corrective action. Self-declared status without supporting evidence is the most common assessment finding.
Government entities in the Kingdom, their affiliated companies inside and outside Saudi Arabia, and private-sector organisations that own, operate, or host Critical National Infrastructure. All other entities are encouraged to adopt the controls as best practice.
Yes. Controls, measures, and evidence are shared objects in Govrly, so one implementation effort and one piece of approved evidence can satisfy overlapping requirements across the NCA ECC, SAMA CSF, CST CRF, Saudi PDPL, ISO 27001:2022, and custom frameworks.
See your ECC control library in one place
Controls, owners, evidence, and audit status — connected, and ready when the assessor is.
