On the effectiveness of distributed worm monitoring

  • Authors:
  • Moheeb Abu Rajab;Fabian Monrose;Andreas Terzis

  • Affiliations:
  • Computer Science Department, Johns Hopkins University;Computer Science Department, Johns Hopkins University;Computer Science Department, Johns Hopkins University

  • Venue:
  • SSYM'05 Proceedings of the 14th conference on USENIX Security Symposium - Volume 14
  • Year:
  • 2005

Quantified Score

Hi-index 0.00

Visualization

Abstract

Distributed monitoring of unused portions of the IP address space holds the promise of providing early and accurate detection of high-profile security events, especially Internet worms. While this observation has been accepted for some time now, a systematic analysis of the requirements for building an effective distributed monitoring infrastructure is still missing. In this paper, we attempt to quantify the benefits of distributed monitoring and evaluate the practicality of this approach. To do so we developed a new worm propagation model that relaxes earlier assumptions regarding the uniformity of the underlying vulnerable population. This model allows us to evaluate how the size of the monitored address space, as well the number and locations of monitors, impact worm detection time. We empirically evaluate the effect of these parameters using traffic traces from over 1.5 billion suspicious connection attempts observed by more than 1600 intrusion detection systems dispersed across the Internet. Our results show that distributed monitors with half the allocated space of a centralized monitor can detect non-uniform scanning worms in half the time. Moreover, a distributed monitor of the same size as a centralized monitor can detect the worm four times faster. Furthermore, we show that even partial knowledge of the vulnerable population density can be used to improve monitor placement. Exploiting information about the location of the vulnerable population leads, in some cases, to detection time that is seven times as fast compared to random monitor deployment.