CyberKit

TLS Handshake

Also called SSL/TLS Handshake.

The negotiation that sets up an encrypted TLS connection.

What it is

The opening exchange of a TLS session in which client and server agree on a protocol version and cipher suite, authenticate via certificates, and establish shared session keys before any application data flows.

Why it matters

The handshake decides the security of everything that follows, so its details matter in forensics and detection: weak cipher choices, downgrade attempts, and certificate anomalies all surface here. The unencrypted handshake fields are also valuable for fingerprinting traffic.

In practice

Inspecting a packet capture's handshake to see a client and server settle on an ECDHE cipher suite for forward secrecy.

What to look for

  • TLS versions and cipher suites in the ClientHello and ServerHello.
  • Server name indication values that do not match the destination.
  • Self-signed or mismatched certificates.

Common mistake

Thinking encrypted traffic shows nothing. The handshake still reveals names, versions and fingerprints.

Use it in CyberKit

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