CyberKit

Protocol Tunneling

Also called ICMP tunneling, HTTP tunneling.

Smuggling one protocol's traffic inside another to evade controls.

What it is

Encapsulating arbitrary traffic inside a protocol that is normally allowed out (such as ICMP, HTTP, or HTTPS), so it passes through firewalls and proxies. The carrier protocol acts as a wrapper for the hidden payload.

Why it matters

Tunneling lets attackers reach the outside world or move data even where egress is tightly filtered, so investigators learn to question traffic whose volume or pattern does not match the protocol it claims to be.

In practice

Catching an implant that wrapped its command channel in oversized ICMP echo packets to slip past an egress firewall that allowed pings.

What to look for

  • DNS, ICMP or HTTP carrying unusual amounts of data.
  • Long sessions on protocols that are usually short.
  • Tools such as SSH or chisel on unexpected ports.

Common mistake

Allowing a protocol because it is common. Attackers tunnel through what you already allow.

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.

  • Wireshark Open source

    Opens a capture packet by packet so you can see exactly what crossed the wire. Our notes.

  • Zeek Open source

    Turns traffic into structured logs for connections, DNS, HTTP, TLS and more. Our notes.

  • Suricata Open source

    An IDS that alerts on known patterns and logs protocol metadata alongside. Our notes.

  • Arkime Open source

    Indexes full packet capture at scale so you can search and pull sessions later. Our notes.

Read next

Sources