CyberKit

Deep Packet Inspection

Also called DPI.

Inspecting a packet's payload, past the headers, to identify content.

What it is

Examining the application-layer contents of packets (not merely the IP and port headers) to identify protocols, extract fields, and match patterns. It lets a sensor recognize what an application is actually doing inside a connection.

Why it matters

DPI underpins protocol-aware detection and content extraction, but it is blind inside encrypted streams, which pushes investigators toward metadata and fingerprinting techniques when traffic is wrapped in TLS.

In practice

Using DPI to spot a malicious HTTP request whose URI and User-Agent matched a known implant even though it rode over a non-standard port.

What to look for

  • Protocols identified on ports that do not match.
  • Files and commands inside cleartext sessions.
  • Policy blocks based on content.

Common mistake

Trusting it on encrypted traffic. Without TLS inspection it sees only metadata.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Palo Alto Networks NGFW Commercial

    A next generation firewall that enforces policy by application and user and logs each session.

  • Cloudflare WAF Commercial

    Filters web traffic at the edge before it reaches the application.

  • Suricata Open source

    Can run inline as an IPS to block traffic that matches its rules. Our notes.

  • Snort Open source

    A long standing open source IDS and IPS with a large public rule set.

Read next

Sources