Content governance for ISPs and operators
ISP content filtering for national regulatory requirements
ISP content filtering means applying the filtering requirements that apply to a provider at the point where subscriber traffic meets the internet. In Saudi Arabia, the Communications, Space and Technology Commission (CST) provides filtering lists to data service providers to apply on their internet gateways. Interkey Intelligent DPI supports that work with application classification, content filtering to meet national regulatory requirements, a URL library, policy execution and reporting, deployed on the provider's own infrastructure and supported from Riyadh.
A Saudi product, built by Interkey
For network engineers and compliance teams at ISPs, data service providers and telecom operators. Reviewed November 2026.
- The requirement:filtering lists are applied at internet gateways. In Saudi Arabia, CST supplies the lists to data service providers.
- What DPI adds:it identifies which application a flow belongs to, including encrypted and tunnelled flows, without decrypting them.
- What Interkey Intelligent DPI provides:content filtering to meet national regulatory requirements, a URL library, policy execution (including blocking where your policy and applicable regulation require it) and reporting for regulatory teams.
- How to start:out-of-band classification first, then report-only policy, then the inline decision.
What ISP content filtering involves
Every provider that carries subscriber traffic to the internet has to answer three practical questions about filtering: which content and applications a requirement covers, where in the network it is applied, and how the provider shows that it has been applied.
In Saudi Arabia, CST provides internet filtering services in the Kingdom and supplies filtering lists to data service providers, who apply them on their internet gateways. The lists, and any change to them, come from CST. The provider's job is to apply them consistently, at the scale of its own network, and to be able to report on that.
A list is only as useful as the provider's ability to recognise the traffic it refers to. Encryption hides payloads from inspection, many applications share the same common ports, and some applications change their behaviour to avoid being identified. That is the gap deep packet inspection (DPI) fills.
Source: CST internet filtering service
How Interkey Intelligent DPI supports content filtering
| Function | What it does |
|---|---|
| Application classification | Identifies the application or protocol of each flow, including encrypted and tunnelled flows, from flow behaviour (handshake structure, packet sizing and timing, and endpoint behaviour), without decrypting them |
| Content filtering | Content filtering to meet national regulatory requirements, part of the platform's content-governance role for ISPs and operators |
| URL library | The platform includes a URL library for content governance |
| Policy execution | Policies are deployed and adjusted in real time, per application, subscriber group or cell, with blocking where your policy and applicable regulation require it |
| Evasive applications | VPN and other evasive applications keep changing to avoid detection. The AI traffic model built into the engine extracts features from live traffic automatically and is retrained automatically, so classification keeps up where your requirements cover such applications |
| Live View and reporting | A network-wide view with drill-down to application and flow level, real-time policy execution feedback and a reporting layer for regulatory and capacity teams, with latency measured in seconds |
| Third-party interconnection | Supported; the systems the platform connects to are defined in the integration plan |
See also: Interkey Intelligent DPI features
Bringing your filtering lists into the platform
How your filtering lists reach the platform, in which format and how often they are refreshed is agreed with your team during scoping and written into the integration plan, together with the other systems the platform connects to.
Bring these to the scoping discussion:
- The filtering lists you must apply, and who supplies each one.
- Where your internet gateways sit, and how traffic reaches them across fixed and mobile access.
- How a change to a list is approved and recorded inside your organisation.
- The reports your compliance team submits, and how often.
Where filtering runs: out-of-band and inline
| Out-of-band | Inline |
|---|---|
| The platform receives a copy of traffic and classifies and reports without sitting in the forwarding path | The platform sits in the forwarding path and can act on traffic |
| Shows how your traffic matches your requirements before anything acts on it | Needed for enforcement, including blocking |
| Where most operators start | Usually a second phase, after classification has proven itself |
Both modes run on your own infrastructure. The platform can operate entirely in the Kingdom, and it is designed for carrier-scale traffic across fixed and mobile networks, where volumes run from Tbps up to dozens of Tbps; throughput is sized for each deployment.
Governance: filtering traffic, not monitoring people
Content filtering applies a requirement to classes of traffic. Interkey Intelligent DPI is built and offered for network governance and regulatory compliance, not for surveillance of individuals: it classifies traffic so that the policies a provider approves can act on it. Its output is metadata about applications, traffic volumes and triggered policies, and policies act per application, subscriber group or cell.
The controls below sit with the provider, not the platform. Setting them up before the first rule is enforced makes every later decision easier to explain and to audit.
1. A policy catalogue.For each rule: the list or requirement it comes from, the scope, the action, and an owner.
2. An approval route.Who signs off a rule before it moves from report-only to enforcement, and what evidence they need to see.
3. Data rules.Which reports are kept, for how long, and who can query them. Retention and access follow your data-governance rules and the contract.
4. A review rhythm.Compare policy execution feedback with what each rule was approved to do.
5. Change control.List, model and policy updates enter the live network through your change-control process.
What to check before choosing a content-filtering platform
- Encrypted and tunnelled traffic:can the platform classify it without decrypting it, and have you seen that on your own traffic?
- False positives:are results reported per application class? A false positive means a rule acts on traffic it was never meant to touch.
- Out-of-band first:can you measure classification before anything acts on traffic?
- Policy scope:can rules apply per application, subscriber group or cell?
- Reporting:does the reporting give your compliance team what it submits, close to real time?
- Data:does subscriber traffic stay in the Kingdom, and who sets retention and access?
- Local support:who supports the platform, from where, and in which languages?
- Proof of concept:are acceptance criteria agreed in writing before testing starts?
A proof of concept in 3 stages
1. Written acceptance criteria.What is tested, on which traffic, how it is measured and what counts as a pass, agreed before deployment.
2. Out-of-band classification against verified traffic.The platform classifies without touching the forwarding path, and false positives are measured as carefully as detection.
3. Report-only policy, then the inline decision.Rules run in report-only mode first; inline enforcement follows only after classification has proven itself.
See also: How Interkey runs a DPI proof of concept
Questions ISPs and operators ask
Does Interkey Intelligent DPI decide what is filtered?
Can it filter encrypted traffic without decrypting it?
How are our filtering lists loaded and kept up to date?
Does subscriber traffic have to leave Saudi Arabia?
Can we see the effect of a rule before it is enforced?
How is it priced?
Proof of concept in three phases
Written acceptance criteria.Agree which rules are tested, on which traffic and subscriber groups, how results are measured and what counts as a pass.
Out-of-band classification against verified traffic.Measure false positives as carefully as detection for every class the rules depend on.
Report-only policy, then the inline decision.Each rule shows what it would have done; enforcement follows only after classification has proven itself.
Discuss a DPI proof of concept
Tell us what kind of provider you are, which filtering requirements apply to you, where your internet gateways sit and your timeline. Our team in Riyadh replies in Arabic or English.
- Our engineers read your request
- We agree the scope of a technical session
- You see the product on a use case you choose