- Market
- Saudi Arabia
- Written for
- CISO, CIO
- Decision
- Prepare a licensed provider for CST’s cybersecurity expectations
- Languages
- EN · AR
Enterprise delivery credentials
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
The obligation
A licence to operate arrives with cybersecurity obligations attached
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 Communications, Space & Technology Commission is the regulator of Saudi Arabia’s communications and technology sector, and for the service providers it licenses, cybersecurity is part of the regulatory relationship — an obligation the Commission defines, updates and supervises, not a voluntary standard a provider opts into. That changes the character of the work. A voluntary certification is examined once a cycle by an auditor you appoint; a regulatory framework is read continuously by the authority your business cannot operate without.
One honest note before anything else: the obligation itself is CST’s document, and it is the Commission’s to define. We deliberately do not paraphrase its structure, control counts or timelines here, because a paraphrase ages and the framework text on cst.gov.sa does not need one — read the current published version there. What this page describes is the work that sits between that text and a compliant network: assessment, remediation and evidence, done in the licensee’s own engineering terms.
The translation
From a sector framework to a gap register one network can close
A framework is written for every provider in the sector; your network is one of them. The readiness work converges what you actually run into a single register, and everything downstream is ordered by it.
Four inputs — asset inventory, security operations, supplier agreements, incident records — converge into a gap register mapped to CST’s framework, which produces remediation ordered by exposure, evidence built for supervision, and answers ready for the regulator.
Network and asset inventory
Core, access, IT and the field estate, as they exist rather than as drawn.
Current security operations
What is monitored, by whom, and what happens when something fires.
Supplier and interconnection agreements
The third parties whose access and failures become yours.
Incident and change records
The history that shows how the estate actually behaves under stress.
What we do
The gap register
Every expectation in the framework CST publishes, paired with the current state of your estate and a named owner — the one document from which remediation, budget and reporting all read.
Remediation ordered by exposure
Engineering work sequenced by what an attacker or an outage would reach first.
Evidence built for supervision
Records organised so a regulator’s question has an answer with a date on it.
Answers ready before they are asked for
Self-assessment positions your team can state and defend, not reconstruct under deadline.
The register is the deliverable the rest of the engagement hangs from; the framework text itself stays CST’s.
The estate
Four ways a provider’s network resists a corporate-IT playbook
Generic hardening programmes assume an office network. A licensee’s estate breaks those assumptions in ways the readiness work has to respect from the start.
Availability is measured in subscribers
An outage is not a productivity loss inside one company; it is a service the public depends on going quiet. Controls are chosen and scheduled so the fix never becomes the incident.
Subscriber data at population scale
The records a provider holds — identity, location, usage — are sensitive at a scale few enterprises ever touch, and access to them has to be provable, not just restricted.
Interconnection widens the perimeter
A provider’s network touches other providers by design, so its boundary includes parties it does not control and the readiness work has to treat those seams as first-class assets.
Infrastructure lives in the field
Exchanges, towers and street cabinets sit far from any office, so physical access, remote management and tamper evidence carry weight that a data-centre-only programme never gives them.
Our role
What readiness covers before CST’s own assessment begins
- 01
The baseline, against the real text
We assess your estate against the framework CST currently publishes — not a summary of it — and record every gap with its owner, so the position you hold is the position you can prove.
- 02
Remediation in engineering terms
Gaps are closed as network and systems work — segmentation, access, monitoring, supplier controls — sequenced so nothing the public depends on goes down for the sake of a compliance date.
- 03
Evidence shaped for a supervisor
Because a regulator’s attention is continuous, the evidence is organised to be produced on request at any time, not assembled once for a visit and left to age.
CST defines the framework, conducts its own assessment and supervises its licensees; readiness prepares you to stand in front of that process, and the standing itself is yours as the licence holder.
The Communications, Space & Technology Commission defines the cybersecurity framework for the providers it licenses and supervises compliance with it. The framework text CST publishes is the obligation; this page describes preparation to meet it. Source
Common questions
What buyers ask
Where do we find the actual text of CST’s cybersecurity requirements?+
From CST directly — the Commission publishes its regulatory framework and related instruments on cst.gov.sa, and that published text is the obligation, in the current version the Commission maintains. We deliberately do not restate its structure, control counts or deadlines on this page, because any paraphrase starts ageing the day it is written and a licensee acting on a consultant’s summary instead of the regulator’s text has added a translation error to its compliance risk. Our work starts from the current framework text and ends in your network; the text itself always stays CST’s.
We already run an NCA ECC programme. Does CST readiness start from zero?+
No — much of the underlying engineering serves both, because asset inventories, access control, monitoring and incident handling are the same work whichever authority asks about them. What differs is the asking: a sector regulator reads your estate through its own framework, in its own categories, with its own evidence expectations, and an answer filed for one authority rarely drops unmodified into the other’s format. The efficient approach is one control implementation mapped to both frameworks, so each obligation is answered from shared work rather than run as a separate programme that duplicates it.
Can Techbanq handle the relationship with CST on our behalf?+
No, and you should be wary of anyone who offers to. The regulatory relationship belongs to you as the licence holder: CST defines the framework, conducts its own assessments and supervises its licensees, and Techbanq is not licensed, approved or endorsed by CST in any capacity. What we do is make that relationship easier to stand in — the baseline assessed against the current framework text, the gaps remediated as engineering work, the evidence organised so a question from the Commission has a dated answer. You face the regulator; our job is that you face it prepared.
In this cluster
Next step
Baseline your position
A baseline assessment that turns CST’s published framework into a gap register with named owners, so remediation starts from your network’s facts rather than the framework’s table of contents.
