Cybersecurity credentials
NCA ECC
ECC compliance expertise
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
The patterns
Four gap patterns that recur across Saudi ECC postures
These are patterns, not statistics: shapes that appear again and again because ordinary organisational forces produce them. If one reads like your estate, the cause beside it is the thing to fix.
- 01
Governance that lives on paper
The policies exist, the committee has a charter, the roles are named — and none of it is used to decide anything. The cause is that the structure was built to satisfy a reader, not to carry decisions, so nothing in daily work depends on it and it quietly stops being real.
- 02
An inventory that drifted from the estate
The asset register was accurate the month it was built. Since then systems were added, moved and retired through channels the register never hears about. The cause is a register maintained by memory and effort instead of being fed by the processes that change the estate.
- 03
Logging without anyone reading
Collection was the project; review was assumed. Logs flow into a platform and no routine, no owner and no alert threshold turns them into attention. The cause is that enabling a log is an engineering task with an end date, while reviewing one is an operating duty nobody was given.
- 04
Third parties connected, not managed
Suppliers hold access and data, and nobody can list which, under what terms, reviewed when. The cause is that supplier relationships are owned commercially — procurement signs, the business runs — and the security dimension has no owner between contract signature and the incident.
Why they persist
The organisational habits that keep reopening the same ECC gaps
Notice what the four patterns share: none of them is a missing technology. Each is a working thing that lost its connection to daily operations — a structure without decisions, a register without feeds, a log without a reader, a supplier without an owner. That is why a remediation programme that buys tools and rewrites documents leaves the patterns intact. It treats the visible symptom while the force that produced the gap keeps operating.
The force is usually the same one: work that produces a compliance artefact gets funded as a project, and projects end. The register, the policy set and the log platform are all end-states of projects. What the published controls actually describe are ongoing behaviours — governing, inventorying, reviewing, managing — and behaviour needs an owner, a cadence and a trigger in the operating calendar, none of which a project budget line creates. Until a gap's closure includes those three things, the closure has a shelf life.
The order
Closing recurring ECC gaps in a sequence where each fix holds the next
The patterns are connected, so the order matters: closed in the wrong sequence, each fix is built on ground the next pattern erodes.
Make the inventory self-maintaining
Feed the register from the processes that change the estate — provisioning, procurement, decommissioning — so accuracy stops depending on effort. Every other control is scoped by this one; fixing anything else first means fixing it against a moving picture. A register the estate updates, not one a person remembers to.
Give every collected log a reader
Attach a named owner, a review routine and thresholds that summon attention to what is already being collected, before collecting more. Review is the control; collection is only its raw material. Monitoring that produces decisions and a review trail, not storage.
Put an owner between every supplier and your estate
List who connects and what they hold — the fresh inventory now makes this answerable — then assign each relationship a security owner and a review cadence proportionate to its access. A supplier picture someone is accountable for keeping true.
Rebuild governance around the decisions now flowing
The three fixes above generate real questions — exceptions, supplier risks, review findings — and governance built last has actual material to decide on. A committee with a docket stays alive; one built first waits for an agenda that never comes. Governance used because it is needed, which is the only kind that lasts.
Our role
What we change so a closed ECC gap stays closed
- 01
Diagnosis before remediation
We read your posture for the pattern and its cause, not only the finding — because a register of findings without causes prices the symptom and leaves the disease.
- 02
Fixes wired into operations
Each closure ships with its feed, its owner and its cadence — the inventory fed by change processes, the log with its reader, the supplier with its reviewer — so the fix does not depend on anyone remembering it.
- 03
A posture that reads well later
The routines leave dated records as they run, so the next assessment reads months of operation rather than a fresh coat of preparation.
Whether the posture satisfies the framework remains the assessment's determination — what we leave is an estate whose gaps have lost the causes that kept regrowing them.
The control sets a posture is measured against are published by the National Cybersecurity Authority on its regulatory-documents pages — read your gaps against that text, not against any summary of it. Source
Common questions
What buyers ask
Why do ECC gaps we closed last year keep coming back?+
Because the closure fixed the artefact and left the force that erodes it. An inventory corrected by hand drifts again the moment systems change through channels it does not hear; a rewritten policy is dead again within months if no decision depends on it. A closure that lasts changes how the thing is maintained — the feed, the owner, the cadence — not just its state on the day the register entry was marked done. If a gap has returned once, treat that as evidence about the closure, not about the team.
Which of the recurring ECC gap patterns should be closed first?+
The inventory, almost always. Not because it is the highest risk on its own, but because every other control is scoped by it: access reviews, logging coverage, supplier lists and assessment scope all inherit its accuracy. Close the flashier gaps first and each is closed against a picture of the estate that is quietly wrong — which is how organisations discover, at assessment, that a hardening programme missed the systems the register did not know about. Sequence by dependency, not by how alarming each finding sounds.
Is it worse to have many small ECC findings or a few structural ones?+
The structural ones, though the long list feels worse in the room. Many small findings often share one cause — a drifting inventory alone can generate findings across access, logging and hardening — and treating the cause collapses the list. A few structural findings, like governance no decision passes through, mean the machinery that would prevent the next hundred findings does not exist. Count causes, not findings: a register of forty findings with three causes is a healthier position than ten findings with ten.
In this cluster
Read your posture against the patterns
A posture review that names which of the recurring patterns your estate carries, the cause behind each, and a closure order that holds.
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
