How to analyze a TCP and UDP network traffic spike

What does it mean when TCP and UDP network traffic spikes? Network security expert Mike Chapple explains what this means for enterprise network security management.

I recently noticed an unusual spike in TCP and UDP flows from a single internal source to multiple destinations. What steps should I take to determine the type of traffic this represents?

In order to analyze network traffic, check the destination port number using the network monitoring tool that identified the spikes. In many cases, this will tell you the type of TCP and UDP traffic you're seeing. For example, traffic on port 80 is normally HTTP traffic, while traffic on port 443 is normally HTTPS traffic. You can consult the Port Database if you encounter a port you don't recognize.

If that doesn't do the trick, you'll need to sniff the network traffic to identify it. You can do this by connecting a computer running a packet sniffer to your network and leaving it running during one of the spikes. My favorite tool for this job is Wireshark. For more information on using Wireshark, see my tutorial: How to sniff network traffic.

For more information:

  • Learn more about writing Wireshark network traffic filters.
  • How should service providers address VoIP security issues and threats? Read more.

Dig Deeper on Threat detection and response

Enterprise Desktop
Cloud Computing