For telecom regulators and digital-safety authorities
DPI for telecom regulators: governance visibility across networks
For a telecom regulator, deep packet inspection (DPI) is one of the capabilities operators and internet service providers use to apply national requirements on their networks and to show that they have applied them: content filtering, digital-safety and online minor-protection mandates, and traffic reporting. What a regulator can expect depends on what operators can classify, enforce and report. Interkey Intelligent DPI serves operators, ISPs and the regulatory bodies that enforce digital-safety laws, with application classification, content filtering to meet national regulatory requirements, policy execution and a reporting layer for regulatory teams.
A Saudi product, built by Interkey
For technical and regulatory teams at government bodies responsible for telecom regulation, digital safety and online minor protection. Reviewed November 2026.
- Where DPI runs:on operators' and ISPs' networks, where national requirements are applied.
- What a regulator gets:requirements applied consistently, and reports on what was classified and which policies were triggered.
- What keeps it about networks:rules act on classes of traffic, per application, subscriber group or cell, and the output is metadata.
- What to check:encrypted traffic, false positives, report-only testing, change control and where the data stays.
How DPI serves regulatory objectives
National requirements are set by the regulator and other competent authorities, and applied by licensed operators and providers. In Saudi Arabia, for example, the Communications, Space and Technology Commission (CST) provides internet filtering services in the Kingdom and supplies filtering lists to data service providers to apply on their internet gateways, and users can submit block and unblock requests to CST.
A requirement is only as effective as the operator's ability to recognise the traffic it refers to. Encryption hides payloads, many applications share the same common ports, and some applications disguise their traffic as other services. DPI closes that gap by identifying the application each flow belongs to. Source: CST internet filtering service
Regulatory objectives and what operator DPI provides
| Objective | What operator DPI provides | What the regulator can ask to see |
|---|---|---|
| National filtering requirements applied consistently | Application classification and content filtering to meet national regulatory requirements, with a URL library | Which requirements are in force, and the policy execution feedback for each |
| Digital-safety and online minor-protection mandates | Content governance applied per application, subscriber group or cell | The rule behind each mandate, its scope and its owner |
| Encrypted and evasive traffic covered | Classification of encrypted and tunnelled flows without decryption; an AI traffic model that is retrained automatically as applications change | Per-class accuracy results measured on the operator's own traffic |
| Network-wide visibility | Network- and application-level traffic trends and a reporting layer for regulatory teams | The reports agreed between the regulator and the operator |
| Proportionate enforcement | Blocking where the operator's policy and applicable regulation require it; report-only mode before enforcement | False-positive results and approval records before rules are enforced |
| Data kept under national control | Deployment on the operator's own infrastructure, able to operate entirely in the Kingdom; output limited to metadata | Where records are kept, for how long and who can access them |
Questions a regulator can put to operators about their DPI
These questions can be asked of any operator or provider, whichever platform it uses:
1. Coverage.Which parts of the network does the platform see, and is any traffic outside it?
2. Encrypted traffic.How is encrypted and tunnelled traffic classified, and what accuracy has been measured on your own traffic?
3. False positives.Are results reported per application class, including traffic wrongly placed in a class?
4. Testing before enforcement.Do new rules run in report-only mode before they act on traffic?
5. Rule records.For each rule: the requirement it comes from, its scope, its action and its owner.
6. Change control.How do list, model and policy updates enter the live network, and who approves them?
7. Data.Where are records kept, for how long, and who can query them?
8. Reporting.Which reports can be produced, how often, and how close to real time?
Safeguards that keep DPI about networks
A regulator gains most from DPI when the deployments it relies on are governed well. The safeguards below are set by the operator and can be reviewed by the regulator:
- Rules act on classes of traffic.In Interkey Intelligent DPI, policies act per application, subscriber group or cell.
- The output is metadata.Classification produces metadata about applications, traffic volumes and triggered policies.
- Encrypted content stays encrypted.Classification uses observable flow characteristics, without decrypting traffic.
- Retention and access are set by the operator.They follow the operator's data-governance rules and the contract, not a vendor default.
- Accuracy is measured, not assumed.False positives are measured as carefully as detection, because a false positive means a rule acts on traffic it was never meant to touch. See Measuring DPI classification accuracy.
Where Interkey fits
Interkey supplies Interkey Intelligent DPI to operators and ISPs, localises it to the local traffic mix, application set and reporting obligations, integrates it with their policy, billing, security and reporting systems, and supports it from Riyadh in Arabic and English. Interkey recommends starting each deployment with a proof of concept in 3 stages: written acceptance criteria; out-of-band classification against verified traffic; and report-only policy before the inline decision. How Interkey runs a DPI proof of concept
Regulatory teams that want to understand what an operator's DPI can classify, enforce and report are welcome to discuss requirements with our team.
DPI for telecom regulators: common questions
Who runs DPI: the regulator or the operator?
Can DPI enforce requirements on encrypted traffic?
How can a regulator judge over-blocking?
Does the data stay in the Kingdom?
What does the platform record?
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 DPI governance requirements
Tell us which requirements you are working on (content filtering, digital safety, online minor protection or traffic reporting) and what you need operators to be able to show. 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