CyberKit

Drill Case

PCAP Practice Capture

The capture stage of the Network Case against a second file, so nothing carries over from the sample. Download it, open it in PCAP Triage, and read the answers off the tool.

The case

Same questions, different capture. Download practice.pcap, open it in PCAP Triage beside this page, and work from scope to beacon again.

If an answer here matches the sample capture's, that is a coincidence of the traffic, not a shortcut.

Foundational · about 25 minutes · 10 questions

Download practice.pcap

What you will be able to do

  • Scope a capture by its packet count, time window and protocol mix before reading any of it (PCAP Triage)
  • Spot a beacon from conversation counts, sizes and a fixed interval rather than from any one packet
  • Recognize the DNS tunnelling shape: unique labels under one parent domain, queried for TXT (DNS Record Type Reference)
  • Read the indicators that survive in cleartext: the HTTP Host and URI, and the TLS SNI
  • Say which panel of the tool answers a given triage question

Read first: PCAP Triage.

Notes for teaching it
  • Run it with the tool on screen. The drill is deliberately about one capture so the class can point at the same rows.
  • Every answer is computed by the tool's parser over the shipped sample, so the drill and the tool cannot disagree. If they ever seem to, that is a bug worth reporting.
  • The "why is the beacon invisible in one packet" question is the lesson. It is worth asking the group to find the beacon in packet order first, then in the conversation table.
  • The sample is synthetic: documentation address space, reserved names, no real traffic. Say so, and then hand out a real capture for the follow-up.

Worksheet

Every question on one page, to print or to read without JavaScript. The answer key has the answers and why.

All 10 questions
  1. Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. How many packets are in the capture?

    Packets: 152   Bytes: 15666
    First seen: 2026-09-14T13:02:11Z
    Last seen:  2026-09-14T13:14:11Z
    Protocol mix: UDP 26, TCP 126
  2. Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. One domain is queried repeatedly for TXT records, each time with a different random-looking label in front. What is that parent domain?

    DNS queries
    Name                         Type  Count
    ---------------------------  ----  -----
    www.example.com              A     2
    updates.example.org          A     2
    portal.example-sso.test      A     2
    4d5a9000.q.sync.example.net  TXT   2
    03000000.q.sync.example.net  TXT   2
    04000000.q.sync.example.net  TXT   2
    ffff0000.q.sync.example.net  TXT   2
    b8000000.q.sync.example.net  TXT   2
    0e1fba0e.q.sync.example.net  TXT   2
    00b409cd.q.sync.example.net  TXT   2
    21b8014c.q.sync.example.net  TXT   2
    cd215468.q.sync.example.net  TXT   2
  3. Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. What does that run of TXT lookups most likely represent?

    DNS queries
    Name                         Type  Count
    ---------------------------  ----  -----
    www.example.com              A     2
    updates.example.org          A     2
    portal.example-sso.test      A     2
    4d5a9000.q.sync.example.net  TXT   2
    03000000.q.sync.example.net  TXT   2
    04000000.q.sync.example.net  TXT   2
    ffff0000.q.sync.example.net  TXT   2
    b8000000.q.sync.example.net  TXT   2
    0e1fba0e.q.sync.example.net  TXT   2
    00b409cd.q.sync.example.net  TXT   2
    21b8014c.q.sync.example.net  TXT   2
    cd215468.q.sync.example.net  TXT   2
    • DNS tunnelling: data carried in the query names and TXT answers
    • Ordinary SPF and DKIM policy checks made by a mail server during delivery
    • A misconfigured resolver retrying the same failed lookup until it times out
    • Certificate revocation checks made while validating the TLS session
  4. Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. What host and URI did the one HTTP GET request ask for? Answer as host/uri.

    HTTP requests
    Method  Host                 URI                   Count
    ------  -------------------  --------------------  -----
    GET     updates.example.org  /pkg/agent-2.4.1.msi  1
  5. Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. The TLS session is encrypted. Which server name can you still read from its ClientHello?

    TLS server names
    SNI                      Servers       Count
    -----------------------  ------------  -----
    portal.example-sso.test  203.0.113.80  1
  6. Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. One external address receives a long run of small, near-identical TCP conversations. Which address and port? Answer as ip:port.

    Conversations
    Source            Destination         Proto  Packets  Bytes  First seen
    ----------------  ------------------  -----  -------  -----  --------------------
    192.0.2.50:123    198.51.100.123:123  UDP    2        180    2026-09-14T13:02:11Z
    192.0.2.1:53      192.0.2.50:50001    UDP    2        166    2026-09-14T13:02:12Z
    192.0.2.50:49811  198.51.100.10:443   TCP    6        1664   2026-09-14T13:02:12Z
    192.0.2.1:53      192.0.2.50:50002    UDP    2        174    2026-09-14T13:02:31Z
    192.0.2.50:49820  198.51.100.20:80    TCP    6        517    2026-09-14T13:02:31Z
    192.0.2.1:53      192.0.2.50:50003    UDP    2        182    2026-09-14T13:02:52Z
    192.0.2.50:49833  203.0.113.80:443    TCP    6        570    2026-09-14T13:02:52Z
    192.0.2.1:53      192.0.2.50:53100    UDP    2        189    2026-09-14T13:03:11Z
    192.0.2.1:53      192.0.2.50:53101    UDP    2        189    2026-09-14T13:03:13Z
    192.0.2.1:53      192.0.2.50:53102    UDP    2        189    2026-09-14T13:03:16Z
    192.0.2.1:53      192.0.2.50:53103    UDP    2        189    2026-09-14T13:03:18Z
    192.0.2.1:53      192.0.2.50:53104    UDP    2        189    2026-09-14T13:03:21Z
    192.0.2.1:53      192.0.2.50:53105    UDP    2        189    2026-09-14T13:03:23Z
    192.0.2.1:53      192.0.2.50:53106    UDP    2        189    2026-09-14T13:03:26Z
    192.0.2.1:53      192.0.2.50:53107    UDP    2        189    2026-09-14T13:03:28Z
    192.0.2.1:53      192.0.2.50:53108    UDP    2        189    2026-09-14T13:03:31Z
    192.0.2.50:50300  203.0.113.99:9443   TCP    6        432    2026-09-14T13:03:41Z
    192.0.2.50:50301  203.0.113.99:9443   TCP    6        432    2026-09-14T13:04:26Z
    192.0.2.50:49900  198.51.100.10:443   TCP    6        1344   2026-09-14T13:04:31Z
    192.0.2.50:50302  203.0.113.99:9443   TCP    6        432    2026-09-14T13:05:11Z
    192.0.2.50:50303  203.0.113.99:9443   TCP    6        432    2026-09-14T13:05:56Z
    192.0.2.50:50304  203.0.113.99:9443   TCP    6        432    2026-09-14T13:06:41Z
    192.0.2.50:50305  203.0.113.99:9443   TCP    6        432    2026-09-14T13:07:26Z
    192.0.2.50:50306  203.0.113.99:9443   TCP    6        432    2026-09-14T13:08:11Z
    192.0.2.50:49901  198.51.100.10:443   TCP    6        1344   2026-09-14T13:08:28Z
    192.0.2.50:50307  203.0.113.99:9443   TCP    6        432    2026-09-14T13:08:56Z
    192.0.2.50:50308  203.0.113.99:9443   TCP    6        432    2026-09-14T13:09:41Z
    192.0.2.50:50309  203.0.113.99:9443   TCP    6        432    2026-09-14T13:10:26Z
    192.0.2.50:50310  203.0.113.99:9443   TCP    6        432    2026-09-14T13:11:11Z
    192.0.2.50:50311  203.0.113.99:9443   TCP    6        432    2026-09-14T13:11:56Z
    192.0.2.50:49902  198.51.100.10:443   TCP    6        1344   2026-09-14T13:12:23Z
    192.0.2.50:50312  203.0.113.99:9443   TCP    6        432    2026-09-14T13:12:41Z
    192.0.2.50:50313  203.0.113.99:9443   TCP    6        432    2026-09-14T13:13:26Z
    192.0.2.50:50314  203.0.113.99:9443   TCP    6        432    2026-09-14T13:14:11Z
  7. Download practice.pcap from the top of this page and open it in PCAP Triage with "Choose file" (or in Wireshark). Read the answer off the tool. The excerpt below is the same parser output if you would rather read it here. Those conversations to 203.0.113.99:9443 start at a fixed interval. How many seconds apart are they?

    Conversations
    Source            Destination         Proto  Packets  Bytes  First seen
    ----------------  ------------------  -----  -------  -----  --------------------
    192.0.2.50:123    198.51.100.123:123  UDP    2        180    2026-09-14T13:02:11Z
    192.0.2.1:53      192.0.2.50:50001    UDP    2        166    2026-09-14T13:02:12Z
    192.0.2.50:49811  198.51.100.10:443   TCP    6        1664   2026-09-14T13:02:12Z
    192.0.2.1:53      192.0.2.50:50002    UDP    2        174    2026-09-14T13:02:31Z
    192.0.2.50:49820  198.51.100.20:80    TCP    6        517    2026-09-14T13:02:31Z
    192.0.2.1:53      192.0.2.50:50003    UDP    2        182    2026-09-14T13:02:52Z
    192.0.2.50:49833  203.0.113.80:443    TCP    6        570    2026-09-14T13:02:52Z
    192.0.2.1:53      192.0.2.50:53100    UDP    2        189    2026-09-14T13:03:11Z
    192.0.2.1:53      192.0.2.50:53101    UDP    2        189    2026-09-14T13:03:13Z
    192.0.2.1:53      192.0.2.50:53102    UDP    2        189    2026-09-14T13:03:16Z
    192.0.2.1:53      192.0.2.50:53103    UDP    2        189    2026-09-14T13:03:18Z
    192.0.2.1:53      192.0.2.50:53104    UDP    2        189    2026-09-14T13:03:21Z
    192.0.2.1:53      192.0.2.50:53105    UDP    2        189    2026-09-14T13:03:23Z
    192.0.2.1:53      192.0.2.50:53106    UDP    2        189    2026-09-14T13:03:26Z
    192.0.2.1:53      192.0.2.50:53107    UDP    2        189    2026-09-14T13:03:28Z
    192.0.2.1:53      192.0.2.50:53108    UDP    2        189    2026-09-14T13:03:31Z
    192.0.2.50:50300  203.0.113.99:9443   TCP    6        432    2026-09-14T13:03:41Z
    192.0.2.50:50301  203.0.113.99:9443   TCP    6        432    2026-09-14T13:04:26Z
    192.0.2.50:49900  198.51.100.10:443   TCP    6        1344   2026-09-14T13:04:31Z
    192.0.2.50:50302  203.0.113.99:9443   TCP    6        432    2026-09-14T13:05:11Z
    192.0.2.50:50303  203.0.113.99:9443   TCP    6        432    2026-09-14T13:05:56Z
    192.0.2.50:50304  203.0.113.99:9443   TCP    6        432    2026-09-14T13:06:41Z
    192.0.2.50:50305  203.0.113.99:9443   TCP    6        432    2026-09-14T13:07:26Z
    192.0.2.50:50306  203.0.113.99:9443   TCP    6        432    2026-09-14T13:08:11Z
    192.0.2.50:49901  198.51.100.10:443   TCP    6        1344   2026-09-14T13:08:28Z
    192.0.2.50:50307  203.0.113.99:9443   TCP    6        432    2026-09-14T13:08:56Z
    192.0.2.50:50308  203.0.113.99:9443   TCP    6        432    2026-09-14T13:09:41Z
    192.0.2.50:50309  203.0.113.99:9443   TCP    6        432    2026-09-14T13:10:26Z
    192.0.2.50:50310  203.0.113.99:9443   TCP    6        432    2026-09-14T13:11:11Z
    192.0.2.50:50311  203.0.113.99:9443   TCP    6        432    2026-09-14T13:11:56Z
    192.0.2.50:49902  198.51.100.10:443   TCP    6        1344   2026-09-14T13:12:23Z
    192.0.2.50:50312  203.0.113.99:9443   TCP    6        432    2026-09-14T13:12:41Z
    192.0.2.50:50313  203.0.113.99:9443   TCP    6        432    2026-09-14T13:13:26Z
    192.0.2.50:50314  203.0.113.99:9443   TCP    6        432    2026-09-14T13:14:11Z
  8. Why can the beacon not be spotted by inspecting any single packet?

    • Each packet is small and ordinary; the signal is the repetition and the timing across many conversations
    • The packets are encrypted end to end, so nothing inside any of them can be read
    • The parser collapses repeated packets, so each beacon appears only once in the view
    • Beacons only ever use UDP, which the tool counts but does not decode any further
  9. Match each finding to the panel of the tool that shows it.

  10. You are handed an unfamiliar capture. Order the first-pass triage steps.

Next: Linux Case. All drills