198 Part II . Running the Show With (Web site template)
198 Part II . Running the Show With the advent of DSL and cable modems, millions of people are enjoying Internet access with virtually no speed restrictions. In their rush to get online, many of those people neglect even the most basic security. Because the vast majority of these people run Microsoft operating systems, they tend to get hit with worms and viruses rather quickly. Until very recently, it was common practice for Microsoft systems to have many services open to the network of which users were unaware and very little emphasis placed on using firewall features to block intruders. After a machine has been infiltrated, quite often the worm or virus installs a program on the victim s machine that instructs it to quietly call home and announce that it is now ready to do the master s bidding. At the whim of the master, the infected machines can now be used to focus a concentrated stream of garbage data at a selected host. In concert with thousands of other infected machines, an attacker now has the power to take down nearly any site on the Internet. Detecting a DDoS is similar to detecting a DoS attack. One or more of the following signs are likely to be present: . Sustained saturated data link . No reduction in link saturation during off-peak hours . Hundreds or even thousands of simultaneous network connections . Extremely slow system performance Pinging an outside host can tell you a lot about your data link saturation: Much higher than usual latency is a dead giveaway. Normal ping latency (that is, the time it takes for a ping response to come back from a remote host) looks like the following: # ping www.example.com PING www.example.com (192.0.34.166) from 10.0.0.11: 56(84) bytes of data 64 bytes from 192.0.34.166: icmp_seq=1 ttl=49 time=40.1 ms 64 bytes from 192.0.34.166: icmp_seq=2 ttl=49 time=42.5 ms 64 bytes from 192.0.34.166: icmp_seq=3 ttl=49 time=39.5 ms 64 bytes from 192.0.34.166: icmp_seq=4 ttl=49 time=38.4 ms 64 bytes from 192.0.34.166: icmp_seq=5 ttl=49 time=39.0 ms — www.example.com ping statistics — 5 packets transmitted, 5 received, 0% loss, time 4035ms rtt min/avg/max/mdev = 38.472/39.971/42.584/1.432 ms In this example, the average time for a ping packet to make the round trip was about 39 thousandths of a second. A ping to a nearly saturated link will look like the following:
Check Tomcat Web Hosting services for best quality webspace to host your web application.