1. Internet Quarantine: Requirements for Containing Self-Propagating Code David Moore, Colleen Shannon, Geoffrey M.Voelker, Stefan Savage University of California, San Diego Published: IEEE Infocom 03, San Francisco Presented By: Darshan Purandare

2. Outline  Introduction  Background  What’s worm, especially Code-Red  Prevention, Treatment and Containment of the worm  Model  SI epidemic model and Code Red propagation model  Idealized Deployment  Practical Deployment  Conclusion

3. Introduction  Dramatic Increase of “worm” outbreaks  Code-Red recovery cost in excess of $2.6 billion  Still unequipped to tackle such system and software vulnerabilities  Factors for the spread of epidemic infections  Vulnerability of population  Length of Infectious period  Rate of Infection  These map to  Prevention  Treatment  Containment

4. Prevention  Reduces the size of the vulnerable population  Limits the worm outbreak  Vulnerability == function (Insecure S/W Engg Practices)  System and Software security are widely researched  Pro-active prevention measures are not enough

5. Treatment  Virus detectors and system update feature in MS Windows  Reduces vulnerable population  Reduces rate of infection  Can’t provide short-term relief during acute outbreak  Time to design, develop and test security update  Insignificant for actively spreading worms  Took on an average 16 days to eliminate Code-Red vulnerability, many were pending till 6 weeks later

6. Containment  Containment is used to protect individual networks, and isolate infected hosts  Firewalls, Content Filters and Automated routing blacklists  Reduce/Stops spread of infection  During Code-Red epidemic  Blocking inbound access to TCP port 80  Content filtering based on Code-Red specific signature  Isolating infected hosts (blocking hosts outbound access to TCP port 80)  These quarantine measures gave limited protection to portions of the internet, if not halt the spread of infection

7. Why Containment is so important ???  Most viable alternative among all three  It can be completely automated  Can be deployed in the network  Its possible to implement a solution w/o requiring universal deployment on every internet hosts

8. Aims and Approach  To investigate use of widespread containment mechanisms  Authors don’t propose any particular technology for detection and containment of worms “How effectively can any containment approach counter a worm epidemic on the internet?”……  Consider containment systems in 3 abstract properties  Detection and Reaction Time  Strategy for Identification and Containment of the pathogen  Breadth and Topological Placement of Containment System  Used Code-Red empirical Internet topology data for simulation and analysis of a worm spread under various defense mechanisms

9. SI Epidemic Model  A vulnerable machine is described as susceptible (S) machine.  A infected machine is described as infected (I)  Let N be the number of vulnerable machines.  Let S(t) be the number of susceptible host at time t, and s(t) be S(t)/N, where N = S(t) + I(t).  Let I(t) be the number of infected hosts at time t, and i(t) = I(t)/N  Let be the contact rate of the worm.  Define:

10. SI Model Solving the differential equation: where T is a constant

11. Code Red Propagation Model Code Red generates IPv4 address randomly. Thus, there are totally 2^32 addresses Let r be the probe rate of a Code Red worm

12. Code Red Propagation Model  Two problems  Cannot model preferential targeting algorithm e.g. select targets form address ranges closer to the infected host  The rate only represents average contact rate e.g. a particular epidemic may grow significantly more quickly by making a few lucky targeting decisions in early phase.

13. Code Red Propagation Model  Example on 100 simulations on Code Red propagation model: After 4 hours: 55% on average 80% in 95 th percentiles 25% in 5 th percentiles

14. Modeling Containment Systems A containment system has three important properties:  Reaction Time  Containment Strategy  Deployment Scenario

15. Reaction Time  Detection of malicious activity  Propagation of the containment information to all hosts participating the system  Activating any containment strategy

16. Containment Strategy I. Address blacklisting  Maintain a list of IP addresses that have been identified as being infected.  Drop all the packets from one of the addresses in the list.  E.g. Mail filter.  Advantage: can be implemented easily with existing firewall technology  Limitation: Needs to be updated continuously

17. Containment Strategy II Content filtering  Requires a database of content signatures known to represent particular worms  This approach requires additional technology to automatically create appropriate content signatures  Advantage: a single update is sufficient to describe any number of instances of a particular worm implementation  Works well with unintended DoS attack

18. Deployment scenarios  Ideally, a global deployment is preferable.  Practically, a global deployment is impossible.  Can be deployed  At the edge of the corporate networks like firewalls  By ISPs at the access points and exchange points in the network

19. Idealized Deployment Simulation goal To find how short the reaction time is necessary to effectively contain the Code-Red style worm. Simulation Parameters  360,000 vulnerable hosts out of 2 32 hosts.  Probe rate of a worm : 10 per sec Containment strategy implementation –Address blacklisting Send IP addresses of infected hosts to all participating hosts. –Content filtering Send signature of the worm to all participating hosts.

20. Idealized Deployment Result: Content filtering is more effective… 20 min 2 hr Number of susceptible host decreases Worms unchecked

21. Idealized Deployment Next goal  To find the relationship between containment effectiveness and worm aggressiveness.  Figures are in log-log scale.

22. Idealized Deployment Percentage of infected hosts Address blacklisting is hopeless when encountering aggressive worms.

23. Practical Deployment  Network Model –AS sets in the Internet:  routing table on July 19, 2001 from Route Views  1 st day of the Code Red v2 outbreak. –A set of vulnerable hosts and ASs:  Use the hosts infected by Code Red v2 during the initial 24 hours of propagation.  A large and well-distributed set of vulnerable hosts.  338,652 hosts distributed in 6,378 ASs.

24. Practical Deployment  Deployment Scenarios  Use content filtering only.  Filtering firewall are deployed on the borders of both the customer networks, and ISP’s networks. Deployment of containment strategy.

25. Practical Deployment  Reaction time: 2hrs Difference in performance because of the difference in path coverage.

26. Practical Deployment System fails to contain the worm.

27. Conclusion Explored the properties of the containment system  Reaction time  Containment strategy  Deployment scenario In order to contain the worm effectively  Require automated and fast methods to detect and react to worm epidemics.  Content filtering is the most preferable strategy.  Have to cover all the Internet paths when deploying the containment systems

28. Strengths Simple, very well written Reasonable assumptions and real world data for simulation Quantified the quarantine properties of worm epidemics Gives head-start for developers and security people by quantifying reaction time at hand for various scenarios Recommendations to ISPs and ASs, more cooperation and coordination among ISPs needed

29. Weak Links Simulator details and source code not public SI epidemic model doesn’t capture all the dynamics Pessimistic picture ahead

30. Questions, Concerns, Issues ???