| CERT. CERT Advisory CA-2001-26 Nimda Worm. http://www. cert.org/advisories/ca-2001-26.html. |
....as viruses, no longer use legitimate remote execution interfaces to acquire a bounded number of nodes. Rather, they exploit bugs and loopholes and install themselves on machines where they are unwanted. They often try to grow without bound, attempting to infect every machine accessible to them [2], 1] 3] In the best case, these viruses simply steal cycles. However, they can easily have more destructive payloads: delete files and or otherwise damage the host machines, steal sensitive data, participate in a denial of service attack, etc. The Slammer worm [3] did in fact cause ATM ....
CERT Advisory CA-2001-26: Nimda Worm. http://www.cert.org/advisories/CA-2001-26.html, September 2001.
....activities, including: Establishing a topology. A network s topology has a significant impact on its cost, security, and performance. An increasingly important aspect of topology design is network segmentation. In an effort to provide fault isolation and mitigate the spread of worms like Nimda [3] and Code Red [2] enterprises segment their networks using firewalls [4] routers, VLANs [7] and other technologies. Establishing policies. Different users of a network have different privileges. Some users may have unlimited access to external networks while others may have restricted access. ....
CERT COORDINATION CENTER. CERT Advisory CA-2001-26: Nimda Worm. http://www.cert. org/advisories/CA-2001-26.html, September 2001.
....since the NI sees exactly what the host receives and sends. For example, the NI can easily tell if a host is ignoring SYN ACK packets, as would be the case if it is participating in a SYN bomb DoS attack. Third, the random propagation approach used by the recent Code Red worm [8] and follow ons [7, 9, 35]) can be readily identified by the abnormal behavior of contacting large numbers of randomly chosen IP addresses with no corresponding DNS translations. To detect this, a self securing NI can shadow its host s DNS cache and check the IP address of each new connection against it. The main ....
CERT. CERT Advisory CA-2001-26 Nimda Worm, September 18, 2001. http://www.cert.org/advisories/CA-2001-26.html.
....approach of sending email warnings. Specifically, once a new virus is discovered, the administrator can update all selfsecuring NIs to identify propagation attempts to and from their hosts, prevent them, and identify machines already infected. Second, the recent Code Red worm [8] and follow ons [9, 41]) can be readily identified by the traffic pattern at a self securing NI. Specifically, these worms spread exponentially by the abnormal behavior of targeting large numbers of randomly chosen IP addresses with no corresponding DNS translations. Digging deeply into network traffic, as promoted ....
CERT. CERT Advisory CA-2001-26 Nimda Worm, September 18, 2001. http://www.cert.org/advisories/CA-2001-26.html.
No context found.
CERT. CERT Advisory CA-2001-26 Nimda Worm. http://www. cert.org/advisories/ca-2001-26.html.
No context found.
CERT Advisory CA-2001-26 Nimda Worm. http://www.cert.org/advisories/CA-2001-26.html, April 2006.
No context found.
CERT. CERT Advisory CA-2001-26 Nimda Worm, http://www.cert.org/advisories/ca-2001-26.html.
No context found.
CERT. CERT Advisory CA-2001-26 Nimda Worm. http:// www.cert.org/advisories/ca-2001-26.html.
No context found.
CERT advisory CA-2001-26 nimda worm. http://www.cert.org/ advisories/CA-2001-26.html.
No context found.
Cert advisory ca-2001-26 nimda worm. http://www.cert.org/advisories/CA-2001-26.html.
No context found.
Cert advisory ca-2001-26 nimda worm. http://www.cert.org/advisories/ca-2001-26.html.
No context found.
CERT Coordination Center: CERT advisory ca-2001-26 nimda worm. Technical report, CERT Coordination Center, Pittsburgh, PA (2001)
No context found.
C. E. R. Team. CERT Advisory CA-2001-26 Nimda Worm. http://www.cert.org/advisories/CA-2001-26.html, July 2001.
No context found.
CERT Advisory CA-2001-26 Nimda Worm. CERT advisory by CERT/CC, Email: cert@cert.org, CERT Coordination Center, Software Engineering Institute, Carnegie Mellon University, Pittsburgh PA 15213-3890, U.S.A., 18 September revised 25 September 2001. http://www.cert.org.
No context found.
CERT. Cert advisory ca-2001-26: Nimda worm, September 2001.
No context found.
CERT Advisory CA-2001-26 Nimda Worm. http://www.cert.org/advisories/CA-2001-26.html
No context found.
CERT. Cert advisory ca-2001-26 nimda worm. www. cert.org/advisories/CA-2001-26.html, September 2001.
No context found.
CERT. CERT Advisory CA-2001-26 Nimda Worm, Sept. 2001. Available at http://www.cert.org/ advisories/CA-2001-26.html.
No context found.
CERT. CERT Advisory CA-2001-26 Nimda Worm, http://www.cert.org/advisories/ca-2001-26.html.
No context found.
CERT. CERT Advisory CA-2001-26 Nimda Worm, http://www.cert.org/advisories/ca-2001-26.html.
No context found.
CERT. Cert advisory ca-2001-26: Nimda worm, September 2001.
No context found.
CERT. CERT Advisory CA-2001-26 Nimda Worm, http://www.cert.org/advisories/ca-2001-26.html.
No context found.
CERT. Cert advisory ca-2001-26: Nimda worm, September 2001.
No context found.
CERT. CERT Advisory CA-2001-26 Nimda Worm, Sept. 2001. Available at http://www.cert.org/ advisories/CA-2001-26.html.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC