- Market
- Saudi Arabia
- Written for
- CISO, Plant Manager
- Decision
- Meet the raised controls for systems classed as critical
- Languages
- EN · AR
Cybersecurity credentials
NCA ECC
ECC compliance expertise
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
Where the bar rises
What the critical designation adds to the baseline
The critical controls are not a separate framework; they are the baseline with the requirements raised where the consequence of failure is national. The drawing shows the inputs that decide the classification, the control column they feed, and what the raised standard has to produce.
Three inputs — consequence of loss, dependency and exposure — converge on a classification-and-controls column that produces segmentation, continuous monitoring and tested resilience.
Consequence of loss
Whether an outage reaches beyond the organisation to a public or national service.
Dependency
How many other systems or services rely on this one to function.
Exposure
How reachable the system is, and by whom.
What we do
Classification and raised controls
The designation sets the scope; the raised requirements apply within it.
Segmentation and hardening
Stronger isolation and configuration where a compromise would spread furthest.
Continuous monitoring
Detection tuned to the systems whose failure is least tolerable.
Tested resilience
Recovery proven by exercise, because these are the systems that may not simply be restored later.
Classification comes first: it decides which systems carry the raised bar, and getting it wrong scopes the whole programme wrongly.
Why classification is the risk
The system that was critical and nobody had said so
The expensive mistake in this programme is made at the start, in scope. Classify too narrowly and a system that should carry the raised controls does not, leaving the exposure the controls exist to close; classify too broadly and the organisation spends a critical-systems budget hardening things that never warranted it. The label is consequential in both directions, and it is a judgement about impact that the technology alone cannot make.
So we start there, with a classification exercise that reasons about consequence, dependency and exposure rather than defaulting to a list. The Authority is the arbiter of what is critical; our job is to bring you to that conversation already knowing which of your systems the designation reaches and why, so the programme that follows is scoped to the systems that actually carry national weight.
Our role
What we scope and what the Authority decides
We prepare the case and the controls; the classification of a national system rests with the regulator.
- 01
A reasoned classification
We assess which systems the critical designation reaches on consequence, dependency and exposure, so scope is argued rather than assumed and the programme sizes correctly.
- 02
The delta, not the whole
We identify only where the raised controls exceed what you already run for the baseline, so effort concentrates on the genuine increment rather than rebuilding the baseline.
- 03
Evidence the bar is met
We build the record that the heightened controls operate — segmentation enforced, monitoring live, resilience tested — because at this tier existence on paper is not the standard.
Whether a system is designated critical is the National Cybersecurity Authority’s determination; we bring you to it with a reasoned classification and the raised controls already in place, so the assessment confirms a standard you are holding rather than discovering one you are not.
The raised requirements
The four places a critical system is held higher
Where the baseline asks for a control to exist, the critical tier asks for it to be stronger, monitored and proven. These are the four where the increment is largest.
Isolation
Networks segmented to limit lateral movement.
Critical-tier expectation: Critical systems isolated so a compromise elsewhere cannot reach them at all.
Monitoring
Logging and periodic review.
Critical-tier expectation: Continuous detection tuned to the system, with the fastest response path.
Access
Least privilege and reviewed accounts.
Critical-tier expectation: Tightly restricted, strongly authenticated and fully accountable access.
Recovery
Backups and a continuity plan.
Critical-tier expectation: Recovery demonstrated by exercise against a defined objective.
Common questions
What buyers ask
How do we know if our systems count as critical?+
By reasoning about consequence rather than reaching for a checklist. A system tends toward the critical designation when its loss reaches beyond your organisation — into a public service, a national payment flow, a utility or a health platform — when many other systems depend on it, and when it is exposed. The National Cybersecurity Authority is the arbiter of the classification, but you should arrive at that determination already knowing which of your systems the designation plausibly reaches and why. We run that classification exercise first, because it sets the scope of everything after it, and both over- and under-scoping are expensive mistakes.
We already meet the Essential Cybersecurity Controls. How much more is this?+
Less than a fresh programme and more than a formality — the critical controls build on the baseline rather than replacing it, so the work is the increment where the bar rises, not a second full framework. If you already operate the Essential Cybersecurity Controls well, much of the critical tier is met in substance; the genuine additions concentrate in stronger isolation, continuous rather than periodic monitoring, tighter access and resilience proven by exercise. We measure the delta specifically so you invest in the raised requirements and get credit for the baseline you already run, rather than rebuilding controls you have.
Does meeting these controls mean the Authority has approved our critical system?+
No, and it is important to keep the two separate. Meeting the controls is what you do to be ready; the Authority’s own assessment and any determination it makes are separate and rest with it. Techbanq prepares the systems and the evidence so a critical designation finds a standard already held, but we do not classify your systems on the Authority’s behalf, and readiness is not the same as an approval or a certification. Anyone offering you the latter is describing something the regulator, not a supplier, controls.
In this cluster
Next step
Classify your systems first
A classification and gap review that names which of your systems the critical designation reaches and where the raised controls exceed what you already run for the baseline.
Classify your systems first
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
