How to prepare a PCAP for vendor support without leaking the whole capture (opens in new tab)

Packet captures are useful because they are specific. They are risky for the same reason. A raw PCAP can contain: internal IP addresses hostnames credentials or tokens in cleartext protocols cookies DNS queries customer traffic unrelated to the bug proprietary endpoints timing information enough context to reveal network architecture Before sending a capture to a vendor, support team, customer, or public issue, treat it like evidence that needs minimization. The goal is not to make the file p...