Packet Capture
Also called PCAP, full packet capture.
Recording raw network frames off the wire for later analysis.
What it is
The act of copying network traffic (frame by frame, with full headers and payloads) into a file or buffer for inspection. The stored result is commonly called a PCAP after the long-standing capture file format.
Why it matters
A full capture is ground truth for an investigation: it preserves exactly what crossed the wire, so analysts can reconstruct sessions, extract files, and confirm or refute alerts long after the activity occurred.
In practice
Pulling the PCAP from a tap in front of a compromised server to reassemble the exact bytes an attacker downloaded over a cleartext channel.
What to look for
- Full payloads for protocols that are not encrypted.
- Handshakes, retransmissions and resets.
- Captures that dropped packets because the link was busy.
Common mistake
Capturing at the wrong place. Pick a point that sees the traffic you need, before NAT or encryption hides it.
Use it in CyberKit
- PCAP Triage
A first pass over a capture: conversations, protocol mix, DNS, HTTP hosts and TLS names.
- Network Case
A host suspected of beaconing: work its capture from scope to beacon, then the port recall and subnet math behind 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.
-
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.
Tools practitioners use
Read next
- Network Tap: A hardware device that copies a link's traffic for monitoring.
- Flow Data: Summarized session metadata: who talked to whom, without payloads.
- Deep Packet Inspection: Inspecting a packet's payload, past the headers, to identify content.