Drill Case
Network Case
A host suspected of beaconing: work its capture from scope to beacon, then the port recall and subnet math behind it.
The case
A host on the lab segment is suspected of beaconing out. You have a packet capture from its switch port, open in PCAP Triage beside this page.
Read the capture first. Then come the ports, status codes and record types you have to recognize on sight, and the subnet math that decides whether an address is even yours.
Finished the capture stage? Try the practice capture, a second file with the same questions.
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
- Name the service behind the ports that recur in traffic review, without looking them up (Network Port Reference)
- Recall the HTTP status codes that carry investigative weight: the auth failures, the redirects, the 5xx family (HTTP Status Code Reference)
- Go from what a DNS record does to its type, which is the direction a zone file or passive-DNS export needs (DNS Record Type Reference)
- Switch between three lookup tables without losing time deciding which one applies
- Convert between a prefix length, a netmask and a host count without a calculator (CIDR & VLAN Calculator)
- Build the smallest CIDR block that contains a required set of addresses and excludes the rest
- Read a network and broadcast address off a block and say which addresses are usable
- Recognize the special-use IPv4 ranges on sight and say what each one means when it shows up in a log (IP & CIDR Reference)
Read first: PCAP Triage, IP & CIDR Reference.
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.
- The most beginner-friendly drill here, and the natural first one for someone new to the site. No prerequisites and no tooling.
- Deliberately interleaved rather than run in blocks. Grouping all the ports together lets a learner settle in and coast; mixing them forces the "what kind of thing is this" step every question, which is the step that actually happens in triage.
- Every answer is generated from the same tables the three reference pages render, so a learner who checks will find the drill and the page agreeing exactly. Worth saying out loud. It is the reason to trust the drill.
- The drill accepts common shorthands (RDP for 3389, SMB for 445), so do not let anyone lose confidence over transcription. If a class finds a spelling that should be accepted and is not, that is a real bug worth reporting.
- The port selection is curated, not exhaustive: 16 of the reference table's 258 entries. Anyone who wants the rest should be sent to the reference page, not drilled on them.
- The live readout is the teaching surface here: have learners predict the network, broadcast and host count aloud BEFORE they drag, then check themselves against the panel.
- Deliberately IPv4-only. IPv6 prefix maths is the same idea at a scale where the powers-of-two intuition stops helping, and mixing them in one drill teaches neither.
- The special-use range questions are recall, not arithmetic, and tend to be where a class splits: consider running the IP & CIDR Reference on the projector for the first pass.
Terms behind it
- Packet Capture: Recording raw network frames off the wire for later analysis.
- Beaconing: Malware 'phoning home' on a regular interval.
- DNS Tunneling: Smuggling data or C2 inside DNS queries and responses.
- TLS Handshake: The negotiation that sets up an encrypted TLS connection.
- Network Segmentation: Dividing a network into zones to contain and control traffic.
Worksheet
Every question on one page, to print or to read without JavaScript. The answer key has the answers and why.
Capture, 10 questions
-
Open PCAP Triage, press "Load sample", and 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: 37 Bytes: 3444 First seen: 2026-03-01T12:47:09Z Last seen: 2026-03-01T12:53:50Z Protocol mix: ARP 1, UDP 7, TCP 29
-
Open PCAP Triage, press "Load sample", and 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 --------------------------- ---- ----- cdn.example.org A 2 a1b2c3d4.tunnel.example.net TXT 1 e5f6a7b8.tunnel.example.net TXT 1 c9d0e1f2.tunnel.example.net TXT 1 a3b4c5d6.tunnel.example.net TXT 1
-
Open PCAP Triage, press "Load sample", and 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 --------------------------- ---- ----- cdn.example.org A 2 a1b2c3d4.tunnel.example.net TXT 1 e5f6a7b8.tunnel.example.net TXT 1 c9d0e1f2.tunnel.example.net TXT 1 a3b4c5d6.tunnel.example.net TXT 1
- 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
-
Open PCAP Triage, press "Load sample", and 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 files.example.com /updates/patch.bin 1
-
Open PCAP Triage, press "Load sample", and 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 --------------- ------------- ----- cdn.example.org 198.51.100.20 1
-
Open PCAP Triage, press "Load sample", and 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.10:51514 192.0.2.1:53 UDP 2 166 2026-03-01T12:47:09Z 192.0.2.10:49212 198.51.100.20:443 TCP 2 310 2026-03-01T12:47:09Z 192.0.2.10:49213 198.51.100.20:80 TCP 2 286 2026-03-01T12:47:09Z 192.0.2.10:51600 192.0.2.1:53 UDP 1 87 2026-03-01T12:47:10Z 192.0.2.10:51601 192.0.2.1:53 UDP 1 87 2026-03-01T12:47:10Z 192.0.2.10:51602 192.0.2.1:53 UDP 1 87 2026-03-01T12:47:11Z 192.0.2.10:51603 192.0.2.1:53 UDP 1 87 2026-03-01T12:47:12Z 192.0.2.10:49300 203.0.113.47:8443 TCP 2 181 2026-03-01T12:47:14Z 192.0.2.10:49301 203.0.113.47:8443 TCP 2 181 2026-03-01T12:47:44Z 192.0.2.10:49302 203.0.113.47:8443 TCP 2 181 2026-03-01T12:48:14Z 192.0.2.10:49303 203.0.113.47:8443 TCP 2 181 2026-03-01T12:48:44Z 192.0.2.10:49304 203.0.113.47:8443 TCP 2 181 2026-03-01T12:49:14Z 192.0.2.10:49305 203.0.113.47:8443 TCP 2 181 2026-03-01T12:49:44Z 192.0.2.10:49306 203.0.113.47:8443 TCP 2 181 2026-03-01T12:50:14Z 192.0.2.10:49307 203.0.113.47:8443 TCP 2 181 2026-03-01T12:50:44Z 192.0.2.10:49308 203.0.113.47:8443 TCP 2 181 2026-03-01T12:51:14Z 192.0.2.10:49309 203.0.113.47:8443 TCP 2 181 2026-03-01T12:51:44Z 192.0.2.10:49310 203.0.113.47:8443 TCP 2 181 2026-03-01T12:52:14Z 192.0.2.10:49311 203.0.113.47:8443 TCP 2 181 2026-03-01T12:52:44Z 192.0.2.10:49400 198.51.100.20:445 TCP 1 58 2026-03-01T12:53:49Z 2001:db8::1:53 2001:db8::a:51700 UDP 1 62 2026-03-01T12:53:50Z
-
Open PCAP Triage, press "Load sample", and 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.47:8443 start at a fixed interval. How many seconds apart are they?
Conversations Source Destination Proto Packets Bytes First seen ---------------- ----------------- ----- ------- ----- -------------------- 192.0.2.10:51514 192.0.2.1:53 UDP 2 166 2026-03-01T12:47:09Z 192.0.2.10:49212 198.51.100.20:443 TCP 2 310 2026-03-01T12:47:09Z 192.0.2.10:49213 198.51.100.20:80 TCP 2 286 2026-03-01T12:47:09Z 192.0.2.10:51600 192.0.2.1:53 UDP 1 87 2026-03-01T12:47:10Z 192.0.2.10:51601 192.0.2.1:53 UDP 1 87 2026-03-01T12:47:10Z 192.0.2.10:51602 192.0.2.1:53 UDP 1 87 2026-03-01T12:47:11Z 192.0.2.10:51603 192.0.2.1:53 UDP 1 87 2026-03-01T12:47:12Z 192.0.2.10:49300 203.0.113.47:8443 TCP 2 181 2026-03-01T12:47:14Z 192.0.2.10:49301 203.0.113.47:8443 TCP 2 181 2026-03-01T12:47:44Z 192.0.2.10:49302 203.0.113.47:8443 TCP 2 181 2026-03-01T12:48:14Z 192.0.2.10:49303 203.0.113.47:8443 TCP 2 181 2026-03-01T12:48:44Z 192.0.2.10:49304 203.0.113.47:8443 TCP 2 181 2026-03-01T12:49:14Z 192.0.2.10:49305 203.0.113.47:8443 TCP 2 181 2026-03-01T12:49:44Z 192.0.2.10:49306 203.0.113.47:8443 TCP 2 181 2026-03-01T12:50:14Z 192.0.2.10:49307 203.0.113.47:8443 TCP 2 181 2026-03-01T12:50:44Z 192.0.2.10:49308 203.0.113.47:8443 TCP 2 181 2026-03-01T12:51:14Z 192.0.2.10:49309 203.0.113.47:8443 TCP 2 181 2026-03-01T12:51:44Z 192.0.2.10:49310 203.0.113.47:8443 TCP 2 181 2026-03-01T12:52:14Z 192.0.2.10:49311 203.0.113.47:8443 TCP 2 181 2026-03-01T12:52:44Z 192.0.2.10:49400 198.51.100.20:445 TCP 1 58 2026-03-01T12:53:49Z 2001:db8::1:53 2001:db8::a:51700 UDP 1 62 2026-03-01T12:53:50Z
-
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
-
Match each finding to the panel of the tool that shows it.
-
You are handed an unfamiliar capture. Order the first-pass triage steps.
Recall, 39 questions
-
Port 22/TCP. What service is this?
-
HTTP 200. What is the reason phrase?
-
Which DNS record type does this? Maps a hostname to a 32-bit IPv4 address: the fundamental record type behind ordinary IPv4 name resolution.
-
Port 23/TCP. What service is this?
-
HTTP 301. What is the reason phrase?
-
Which DNS record type does this? Maps a hostname to a 128-bit IPv6 address: the IPv6 counterpart to the A record, needed because A's RDATA only has room for 32 bits.
-
Port 25/TCP. What service is this?
-
HTTP 302. What is the reason phrase?
-
Which DNS record type does this? Points one name to another canonical name, so every other record for the alias is looked up through the target instead of being duplicated.
-
Port 53/TCP/UDP. What service is this?
-
HTTP 304. What is the reason phrase?
-
Which DNS record type does this? Identifies a mail server for the domain along with a preference value used to rank it against any other mail servers for the same domain: lower values are preferred.
-
Port 80/TCP. What service is this?
-
HTTP 400. What is the reason phrase?
-
Which DNS record type does this? Delegates a zone (or subdomain) to a specific set of authoritative name servers.
-
Port 88/TCP/UDP. What service is this?
-
HTTP 401. What is the reason phrase?
-
Which DNS record type does this? Maps an address back to a hostname (the reverse of an A/AAAA lookup) conventionally served from the in-addr.arpa (IPv4) or ip6.arpa (IPv6) reverse-lookup zones.
-
Port 135/TCP. What service is this?
-
HTTP 403. What is the reason phrase?
-
Which DNS record type does this? Marks the start of a zone of authority (one SOA record per zone), and carries its primary name server, admin mailbox, serial number, and the refresh/retry/expire timers secondary servers use to stay in sync.
-
Port 139/TCP. What service is this?
-
HTTP 404. What is the reason phrase?
-
Which DNS record type does this? Publishes the hostname, port, and relative priority/weight for a specific service, addressed via an underscore-prefixed "_service._proto.name" label instead of a plain hostname.
-
Port 389/TCP/UDP. What service is this?
-
HTTP 407. What is the reason phrase?
-
Which DNS record type does this? Holds arbitrary text data attached to a name. The RFC leaves the meaning of that text up to whatever's using it, and in practice that's grown to include domain-ownership verification and email-authentication policies such as SPF.
-
Port 443/TCP. What service is this?
-
HTTP 429. What is the reason phrase?
-
Which DNS record type does this? Restricts which certificate authorities are allowed to issue TLS certificates for the domain, and can name where a CA should report policy violations.
-
Port 445/TCP. What service is this?
-
HTTP 500. What is the reason phrase?
-
Port 1433/TCP. What service is this?
-
HTTP 502. What is the reason phrase?
-
Port 3268/TCP. What service is this?
-
HTTP 503. What is the reason phrase?
-
Port 3389/TCP/UDP. What service is this?
-
Port 5985/TCP. What service is this?
-
Port 5986/TCP. What service is this?
Subnets, 10 questions
-
A new lab segment needs a single CIDR block that exactly covers the 16 addresses from 10.30.6.0 through 10.30.6.15, no more and no fewer. Build the block.
-
100.64.55.10 falls inside 100.64.0.0/10 (Shared Address Space). What category does this block belong to?
-
Team A's workstation pool must include 172.20.14.10 and 172.20.14.200. Team B owns the /24 blocks immediately before and after it. Build a single CIDR block that covers both of Team A's addresses without reaching into Team B's space.
-
A firewall rule must match traffic from 10.50.8.64 and 10.50.8.95 only, not from 10.50.8.63, 10.50.8.96, or the unrelated address 10.50.9.1. Build the CIDR block.
-
169.254.10.5 falls inside 169.254.0.0/16 (Link Local (APIPA)). What category does this block belong to?
-
A WAN link uses an RFC 3021 point-to-point IPv4 addressing scheme with just two host addresses and no separate network/broadcast address: 10.255.255.0 and 10.255.255.1. Build the smallest CIDR block containing both.
-
An incident report references two hosts inside the same site allocation: 10.4.1.5 and 10.7.254.20. Build the smallest single CIDR block that contains both addresses.
-
192.0.2.55 falls inside 192.0.2.0/24 (Documentation (TEST-NET-1)). What category does this block belong to?
-
An analyst wants a single rule that flags any traffic from IANA's benchmarking address space (RFC 2544), reserved for testing network-interconnect throughput so a benchmark never floods a real internet address. A benchmarking host lives at 198.18.0.1, another at 198.19.255.254. Build the CIDR block that covers the whole benchmarking range.
-
A report cites hosts at 203.0.113.10 and 203.0.114.250, addresses in two adjacent /24s from this site's own documentation-range examples. Build the smallest single CIDR block that contains both addresses.
Next: Linux Case. All drills