Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Packet capture records network traffic in full, byte for byte. It is the most detailed evidence available and the most expensive to store, so the question is where and when.

What Is Packet Capture?
Packet capture records network traffic exactly as it crossed the wire, headers and payload together, usually into a PCAP or the newer PCAPNG file format. Where flow records tell you that two hosts exchanged 40 megabytes over TCP 445, a capture lets you see which files moved. It is the highest-fidelity network evidence there is, and the reason it is not everywhere is cost.
Two methods, with a meaningful difference.
A network tap is a passive device inserted into the link. It copies every frame to a monitor port and cannot drop traffic under load, because it is not making forwarding decisions. For fibre, a passive optical tap splits the light and has no power requirement at all, so it cannot fail in a way that affects the production path.
A SPAN or mirror port is a switch feature that copies traffic from selected ports to a monitor port. It is free and easy to configure, and it drops frames when the switch is busy — which is to say, exactly when an incident is generating load. It also typically discards malformed frames, which are often the interesting ones. Use SPAN for convenience, a tap when the evidence matters.
In cloud environments the equivalents are VPC Traffic Mirroring on AWS, Virtual Network TAP on Azure, and Packet Mirroring on Google Cloud, which deliver copies to a collector instance.
tcpdump and dumpcap handle collection; Wireshark and tshark handle analysis. Capture filters use BPF syntax and are applied before writing, so they reduce what you store. Display filters are applied afterwards and are far more expressive. Mixing them up is the most common beginner error.
A sensible long-running capture uses a ring buffer so that disk use is bounded:
dumpcap -i eth1 -b filesize:1024000 -b files:200 -w /capture/edge.pcapng
For continuous capture at speed, purpose-built tools such as Arkime, Stenographer, or Suricata’s capture mode index as they write, so retrieval of a specific conversation does not require reading terabytes sequentially. Zeek is worth running alongside: it writes structured protocol logs rather than packets, which are a fraction of the size and answer most questions without touching the capture at all.
At 10 Gbps sustained, full capture consumes roughly 100 terabytes a day. Few organisations capture everything continuously; the common patterns are capturing at the internet edge only, capturing in front of specific high-value systems, or triggering capture automatically when a detection fires so you get the packets around an event without storing the rest.
Encryption has changed what a capture yields. Most payloads are now opaque, so the value has shifted towards metadata that is visible regardless: TLS handshake details and certificates, SNI where ECH is not in use, DNS, timing, and sizes. Captures remain decryptable in two cases worth knowing — when you hold the server private key and the connection used a non-ephemeral key exchange, which is rare now, or when you have the session keys, which browsers will export to a file named by the SSLKEYLOGFILE environment variable and which Wireshark can consume. That second method is extremely useful in a test environment and inapplicable to real traffic you did not instrument.
A capture is often the most compelling artefact in an investigation, and it is only compelling if its handling stands up. Hash the file with SHA-256 immediately on collection and record the value. Document who captured it, from which interface, using which device and clock source, and when — synchronised time matters here as much as anywhere. Maintain a chain of custody record, work on copies, and never analyse the original.
Packet captures contain the content of communications, which makes them personal data under UK GDPR and, in many cases, interception for the purposes of the Investigatory Powers Act. Capturing on your own network for network security purposes is generally lawful, but the policy, the lawful basis, and the retention period should be written down before you need them, not afterwards. Restrict access to captures tightly, because a capture from a corporate network contains credentials, personal correspondence, and anything else that crossed it.
Our Digital Forensic and Incident Response Services work from captured traffic routinely, and the quality of the capture usually determines how much of the question can be answered.
A tap is a passive hardware device in the link that copies every frame and cannot drop traffic, because it makes no forwarding decisions. A SPAN port is a switch feature that mirrors traffic to a monitor port and will discard frames when the switch is loaded, which is precisely when an incident is occurring. Use taps where evidence completeness matters.
Yes, though the value has shifted. Payloads are usually opaque, but handshake metadata, certificates, DNS, timing, and packet sizes remain visible and answer many investigative questions. Captures also preserve the exact sequence of events for reconstruction. For most organisations the pragmatic split is flow records and protocol logs for breadth, packet capture at a few critical points for depth.
Roughly 100 terabytes per day at a sustained 10 Gbps, which is why continuous full capture is rare. Common approaches are capturing only at the internet edge, capturing in front of specific high-value systems, or triggering capture automatically when a detection fires so you retain packets around events without storing everything else.
Capturing on your own network for network security purposes is generally lawful in the UK, but captures contain the content of communications, which engages UK GDPR and raises Investigatory Powers Act considerations. Document the lawful basis, the purpose, the retention period, and who may access the data before deploying, and restrict access tightly because captures contain credentials and personal correspondence.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.