Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Deep packet inspection reads the payload of network traffic, not just the headers, to identify applications and detect threats. Encryption has steadily narrowed what it can see.

What Is Deep Packet Inspection?
A traditional packet filter decides what to allow using the source and destination addresses, the ports, and the protocol — information carried in the headers. Deep packet inspection goes further and examines the payload, reassembling streams so it can identify the application in use, match signatures against known attacks, and apply policy to content rather than to addresses. It is the technology underneath next-generation firewalls, intrusion prevention systems, and most data loss prevention at the network layer.
Four things happen in sequence. First the device reassembles fragmented packets and reorders TCP segments, because an attacker who splits a malicious string across three packets defeats any inspection that works on single packets. Then it identifies the protocol, often finding HTTP on a non-standard port or a tunnelling tool pretending to be something else. Then it matches: signature sets for known exploits, regular expressions for card numbers or national insurance numbers, file type detection by magic bytes rather than extension. Finally it acts — permit, drop, reset, log, or rate limit.
Hardware matters here. Inspecting at tens of gigabits per second requires dedicated pattern-matching silicon or a carefully tuned software data plane, and enabling full inspection on an undersized appliance is a reliable way to turn a security control into a performance incident.
DPI was designed when most traffic was plaintext. Today the overwhelming majority of web traffic is encrypted, and each protocol generation has removed more metadata.
Organisations respond in one of two ways. Some deploy TLS interception, where the inspecting device terminates the client’s connection with a certificate issued by an internal authority, inspects, and re-encrypts to the server. That restores visibility at a significant cost: a device holding plaintext for everything, certificate pinning breakage in mobile and desktop applications, and privacy implications for staff traffic. Others accept reduced payload visibility and lean on encrypted traffic analysis instead, classifying flows by timing, size distributions, and TLS fingerprints such as JA3 or JA4, combined with endpoint telemetry from EDR, which sees the plaintext anyway.
In enterprise security the uses are clear: blocking exploit traffic, enforcing application policy, catching exfiltration, and giving an analyst enough context to investigate. Internet service providers use DPI for traffic management and for the content filtering that UK providers apply by default under the arrangements overseen by the Internet Watch Foundation.
The same technology enables censorship and mass surveillance, which is why DPI procurement attracts scrutiny. For a UK employer, deploying TLS interception on staff traffic engages the UK GDPR: you need a lawful basis, a data protection impact assessment in most cases, and a clear acceptable use policy that tells employees their traffic is inspected. The ICO’s guidance on monitoring at work is explicit that covert monitoring is rarely justifiable. Excluding categories such as banking and health sites from interception is standard practice and is worth documenting as a safeguard.
Decide what you need to see before choosing where to inspect. Inspecting outbound staff browsing, inbound traffic to your own published applications, and east-west traffic between internal segments are three different problems with different appliances and different policies. Tune the signature set rather than enabling everything, because a default-on ruleset produces a volume of alerts no team can work through. Size for inspected throughput, not line rate. Feed the logs into your SIEM and pair them with flow records, which stay useful even when payloads are opaque.
Our Network Security Services include testing whether your inspection policy actually blocks what it claims to, which is rarely the same as what the datasheet says.
Not without intercepting it. Encrypted traffic is opaque to payload inspection, so a device can only read metadata such as the destination address and, on older TLS versions, the requested hostname. To inspect content, the device must terminate and re-encrypt the connection using a certificate trusted by your endpoints, which is a significant architectural and privacy decision.
Monitoring employee traffic is lawful but regulated. Under UK GDPR you need a lawful basis, usually legitimate interests, and a data protection impact assessment where monitoring is systematic. ICO guidance expects transparency, so staff must be told what is inspected and why. Covert monitoring is only justifiable in narrow circumstances such as a specific investigation into suspected criminality.
It can substantially. Stream reassembly and pattern matching cost far more than header filtering, and TLS interception adds cryptographic work on every connection. Vendor throughput figures usually quote plain firewall performance; the inspected throughput with threat prevention and decryption enabled is often a fraction of it. Size appliances against the features you will actually enable.
Combine approaches. Encrypted traffic analysis classifies flows by timing, packet sizes, and TLS client fingerprints without decryption. Endpoint detection sees plaintext before it is encrypted. DNS logging shows what was resolved even when the connection itself is opaque. Flow records still reveal who talked to whom, for how long, and how much data moved, which detects beaconing and bulk exfiltration.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.