Use cases

PCAP analysis use cases

Six tasks analysts bring to a packet capture, from opening a pcapng in the browser to triaging an infected host. Each page works its task through several public sample captures, shows the checks in A-Packets and in Wireshark or tshark, and says what a capture cannot tell you.

Pick the task in front of you

Use cases and sample reports

The sample reports take one capture each and tell its story frame by frame. The pages here go the other way: one task across several captures, so you can see which signs hold from one sample to the next and which belong to a single file. Every number comes from a public capture, counted in its A-Packets report or with tshark on the original file, and every screenshot is the report as the engine at apackets.com produced it. When a capture cannot answer a question, such as what a file sent over HTTPS contained, the page says so.

To get the same report for your own traffic, upload a capture. Public analysis suits samples and sanitized captures; for production or incident traffic, use a private plan or the on-premise build. Longer investigations of single infections are on the blog.