CyberKit

Encrypted Traffic Analysis

Also called ETA.

Inferring intent from encrypted traffic's shape and metadata.

What it is

A set of techniques that draw conclusions about encrypted connections using observable features (packet sizes, timing, direction, handshake details, and certificate data) instead of payload content. It treats the cipherstream as opaque and reasons about its envelope.

Why it matters

With most traffic now encrypted, payload inspection alone is insufficient; ETA lets investigators still surface command channels, exfiltration, and anomalous applications without decryption.

In practice

Identifying an interactive command channel inside TLS because its tiny, bursty request-and-reply timing looked nothing like normal web browsing.

What to look for

  • Packet sizes and timing that match beacons.
  • Certificates that are self-signed or newly issued.
  • Sessions with unusual upload to download ratios.

Common mistake

Expecting certainty. It points to likely behavior, so confirm on the endpoint.

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