During September, I’ve been very fortunate to attend two actual physical conferences focused on 5G. The first was in Denver Colorado, conveniently just across the Rocky Mountains from my current home in Grand Junction. The second was in London England, 200 miles or so south of my original home in Yorkshire (typically celebrated as the home of the most successful cricket team ever, though puddings also get a well-deserved mention).
At SuriCon 2019, Eric Leblond and Peter Manev – both of whom are key contributors in the Suricata community – presented important test results, emphasizing the implications of packet loss. Let’s dig a little deeper into the importance of zero packet loss in an IDS deployment.
The effect of packet loss on a variety of network analysis gear varies widely based on the function the analysis device is performing. The measurement accuracy of network and/or application performance monitoring devices is affected when packets are dropped by the network sensor. In the case of a cybersecurity appliance, like a Suricata-based Intrusion Detection System (IDS), missed intrusion alerts are directly affected by system packet loss. This is also the case for file extraction.
The effect of packet loss on intrusion alert generation
No matter how good the IDS rule, if all packets for a given session are not delivered to the IDS, alerts can be missed. This is mainly due to how an IDS processes a network session. The given packets that are dropped within the session will determine if the IDS has enough data to generate an alert. In many cases, the IDS will drop the entire session if key packets are missing. A missed alert could mean that an intrusion attempt went undetected.
To measure the missed alerts, the following methodology was used:
- Traffic source is a PCAP file containing actual network traffic with malicious activity
- PCAP file is processed to simulate specified random packet loss
- Suricata alerts are compared for original PCAP file to modified file
- 10% missed alerts with 3% packets loss
- 50% missed alerts with 25% packets loss
The effect of packet loss on IDS file extraction
Part of deploying a successful IDS strategy is to also automate file extraction. Most IDS engines support HTTP, SMTP, FTP, NFS, and SMB protocols. The file extractor runs on top of the protocol parser, which handles dechunking and unzipping the request and/or any response data if necessary. Loss of a single packet for a network stream carrying a file in most cases will cause file extraction to fail.
- 10% failed file extraction with 4% packet loss
- 50% failed file extraction with 5.5% packet loss
In conclusion, the test results show how important zero packet loss is to a successful IDS deployment. FPGA SmartNIC features like on board burst buffering, DMA, and optimized PCI express performance will minimize or completely eliminate packet loss in a standard server-based IDS.