If you do not already have network and server monitoring tools in place, install them. Familiarize yourself with your typical inbound traffic. If, for example, you typically receive 2000 visitors on Tuesday afternoon, it may be cause for concern if you suddenly see ten thousand pings on your website.
Pay close attention to your server’s performance, as well. If you notice routine tasks are taking an unusually long time or certain resources are unavailable, contact your host. While there is a chance it may simply be a service outage, there is also a possibility that you are under attack.
If resources are already geographically dispersed, it is important to view each data center as having more than one pipe to Internet, and ensure that not all data centers are connected to the same Internet provider.
Overall, priorities for architecture should be geographic diversity, provider diversity, and elimination of bottlenecks. While these are best practices for general business continuity and disaster recovery, they will help ensure organizational resiliency in response to a DDoS attack.
Hardware. Deploy appropriate hardware that can handle known attack types and use the options that are in the hardware that would protect network resources. Again, while bolstering resources will not prevent a DDoS attack from happening, doing so will lessen the impact of an attack.
Finally, keep a close watch on any email accounts that are linked to your server, and the comments sections of any websites hosted on that server. A dramatic increase in spambot activity could indicate that it is time to shore up your defenses.
More Info: ddos
No comments:
Post a Comment