- Market
- Saudi Arabia
- Written for
- CISO, CIO
- Decision
- Prepare for an NCA ECC assessment and close the gaps it will find
- Languages
- EN · AR
Cybersecurity credentials
NCA ECC
ECC compliance expertise
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
Applicability
The first question is which control set actually binds you
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
The Essential Cybersecurity Controls are the national minimum baseline. They apply to government entities and to private-sector organisations that own, operate or host critical national infrastructure. The 2024 revision widened both the scope and the depth of what is expected, so an entity that mapped itself against the earlier version has work to do rather than a finished exercise.
The ECC is rarely the only thing that applies. The NCA publishes further control sets alongside it — cloud, critical systems, data — and a sector regulator may impose its own on top. An entity can be subject to three overlapping sets asking for related but differently formatted evidence. Working out that map before starting is not bureaucracy; it is what stops the same control being implemented three times in three ways.
What surprises most entities is where the difficulty sits. The technology controls are usually the easier half — they can be bought, configured and demonstrated. The governance controls are where assessments are lost: a policy with no owner, a risk register nobody has updated in a year, a review that is supposed to happen quarterly and last happened when the framework was adopted. Those cannot be fixed the week before an assessment, because the evidence they need is a history of the control operating.
Domains
What each domain asks for, and what closing it involves
Grouped by the kind of work rather than by control number, because the sequencing that matters is which gaps need a history before they can be evidenced.
Governance
Policies with a named owner, a risk register that is actually maintained, defined roles, and a review cycle that has happened more than once.
Evidence an assessment expects: Approved documents, meeting records, dated review outputs
Asset and access management
An asset inventory that matches what is running, a joiner-mover-leaver process that is followed, privileged access separated and reviewed.
Evidence an assessment expects: Current inventory, access review records, privileged account list
Technical protection
Segmentation, secure configuration baselines, patch and vulnerability management with a measured cycle, malware protection, cryptography and key handling.
Evidence an assessment expects: Configuration standards, patch cycle metrics, scan and closure records
Monitoring and response
Log collection with retention that outlasts the audit window, detection rules that fire on something real, and an incident process that has been exercised rather than written.
Evidence an assessment expects: Retention configuration, alert history, incident and exercise records
Resilience
Backups that have been restored from, a recovery objective that has been measured rather than declared, and a dependency map reflecting the current estate.
Evidence an assessment expects: Restore test results with timings, dependency map, recovery plan
Third-party and cloud
Supplier assurance that verifies rather than assumes, contract terms that pass obligations down, and cloud services scoped against the applicable cloud control set.
Evidence an assessment expects: Supplier register with assessment status, contract clauses, cloud scope record
Sequence
The order that saves the most time
Sequencing matters more here than in most compliance work, because some evidence can only be produced by letting time pass.
Fix retention first
Anything requiring a history — logs, review records, patch metrics — should start on day one, because you cannot create the past.
Map applicability
Establish which control sets bind you and where they overlap, so a control is implemented once and evidenced in several formats.
Assess
Control by control, separating what is missing from what exists but cannot be shown. Those two need very different work.
Assign ownership
Every control needs a named person. Unowned controls are how an entity passes one assessment and fails the next.
Remediate
Engineering work on the technical gaps, sequenced so items needing external approval start early.
Rehearse
Walk the evidence pack as an assessor would before the assessment, which is when gaps are cheap to find.
Our role
What a consultancy does on an ECC programme
- 01
An honest current position
We assess your environment against the published control set and state where you stand, including the controls that are already met.
- 02
The engineering
We close the technical gaps ourselves — segmentation, identity, logging, hardening — rather than handing over a plan for someone else to implement.
- 03
Governance that produces evidence
We design the governance so controls generate their own records continuously, which is what makes the next assessment cheaper than this one.
- 04
A rehearsed evidence pack
We assemble the pack and rehearse it against the control text before the assessment, so the first person to test it is not the assessor.
Compliance itself is a state of your organisation, determined through the Authority's own processes and your assessors, and the programme is built so that determination is straightforward when it comes.
The National Cybersecurity Authority publishes the Essential Cybersecurity Controls and the accompanying implementation guidance. Read the current control set directly rather than relying on a summary — including this one. Source
Common questions
What buyers ask
Does the ECC apply to private companies?+
It applies to government entities and to private-sector organisations that own, operate or host critical national infrastructure. Many private companies are not in scope for the ECC directly but inherit equivalent obligations through a customer contract or a sector regulator. Establishing which of those situations you are in is the first piece of work, and it sometimes concludes that a lighter requirement applies than assumed.
Can you make us ECC compliant?+
We can assess you against the published control set, close the gaps and assemble the evidence. Compliance itself is a state of your organisation, determined through the authority's own processes and your assessors — not something a supplier confers. Treat any firm that describes it otherwise as one that has not read the process carefully.
We mapped ourselves to the earlier version. Is that still valid?+
It is a useful starting point but not a finished exercise. The 2024 revision expanded both scope and control depth, so a prior mapping tells you where you stood against the old baseline. The efficient approach is a delta assessment against the current set rather than starting again — most of the earlier work is still worth something.
What is the single most common reason entities fail?+
Controls that exist but produce no record of having operated. The technology is in place, the process is real, and there is nothing dated to show an assessor. It is also the most avoidable, because the fix is administrative rather than expensive — but it needs a cycle or two of history before it can be shown, which is why it should be the first thing addressed rather than the last.
In this cluster
Next step
Request a gap assessment
A gap assessment against the control set that applies to you, returning a control-by-control position, an owner for each gap and a remediation sequence. One hour to scope it, no cost, no commitment.
Request a gap assessment
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly
