DDOS features?

Typically an “official” DDoS attack targets host servers and not individual websites. I am sure that all big brand name hosts have DDoS protection in place on their servers. BPS currently provides Brute Force Login attack protection that can be considered loosely DDoS protection due to the volume of POST login attacks during large scale Brute Force Login attacks on an individual website. We are currently still in the R&D phase of looking at individual website DDoS protection methods that could be useful that are not already being done by web hosts.

You can do something simple like allowing only your IP address access to your WordPress Login page in the link below permanently or temporarily IF you are the only person that logs into your site. ie you do not allow anyone else to register, login and post comments on your site.
http://forum.ait-pro.com/forums/topic/protect-login-page-from-brute-force-login-attacks/

We have several sites where we need for people to be able to register, login and post comments. So during larger scale brute force login attacks we have seen 1,000 login attempts per second for up to 3 days. During the attack the forum site loaded .1 seconds slower than normal. That was the only negative impact and everything else worked as usual – new user’s were successfully able to register, login and post comments. Basically we were aware that the attack was going on, but no one else was – business as usual. 😉

And most importantly – all logging is done to plain text static files instead of using the WordPress DB/Queries. Queries are the most expensive operation for dynamic php site types so Queries should be used carefully and in the case of constant logging of events it would be very foolish/expensive to use the WP DB to handle any part of logging Security events. In addition, all log files are automatically zipped and emailed to you when they reach a certain size and are replaced with a new blank log file.