CyberKit

Network Tap

Also called TAP, test access point.

A hardware device that copies a link's traffic for monitoring.

What it is

A dedicated hardware device inserted inline on a network link that passively copies every passing frame to a monitoring port without altering the original flow. Unlike a switch mirror, it does not compete for switch resources.

Why it matters

Because a tap captures all traffic faithfully and does not drop frames under contention the way a mirror can, it is the preferred source for forensic-grade capture and reliable detection.

In practice

Installing a tap in front of a critical server so the captured PCAP would be complete enough to stand up as forensic evidence.

What to look for

  • Taps placed where full traffic is visible.
  • Monitoring ports that drop packets under load.
  • Gaps when the tap or sensor goes offline.

Common mistake

Using a SPAN port for everything. SPAN can drop packets under load where a tap would not.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Wireshark Open source

    Opens a capture packet by packet so you can see exactly what crossed the wire. Our notes.

  • Zeek Open source

    Turns traffic into structured logs for connections, DNS, HTTP, TLS and more. Our notes.

  • Suricata Open source

    An IDS that alerts on known patterns and logs protocol metadata alongside. Our notes.

  • Arkime Open source

    Indexes full packet capture at scale so you can search and pull sessions later. Our notes.

Read next

Sources