CyberKit

Flow Data

Also called NetFlow, IPFIX, flow records.

Summarized session metadata: who talked to whom, without payloads.

What it is

Records that summarize a conversation between two endpoints by its 5-tuple, byte and packet counts, timestamps, and duration, but without the actual content. NetFlow and its IETF standard successor IPFIX are the common formats.

Why it matters

Flow is cheap to store at scale, so it often covers far longer windows than full capture. It is ideal for spotting beaconing patterns, large outbound transfers, and lateral connections across a whole enterprise.

In practice

Noticing in flow records that an internal workstation opened thousands of short, evenly spaced sessions to one external IP, a classic beaconing rhythm.

What to look for

  • Long sessions and regular beacons.
  • Large outbound byte counts.
  • Internal hosts scanning many others.

Common mistake

Expecting payloads. Flows show volume and timing, not content.

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

  • Packet Capture: Recording raw network frames off the wire for later analysis.
  • Beacon Analysis: Finding C2 callbacks by their periodic, repetitive connection pattern.
  • Low and Slow: Pacing activity below thresholds to stay under the radar.

Sources