Series Summary: Building the 3G Blacklist

Post #550 categorized as Websites, last updated on May 26, 2008
Tagged with apache, blacklist, htaccess, ip, mod_rewrite, security, tips

[ 3G Stormtrooper ] In the now-complete series, Building the 3G Blacklist, I share insights and discoveries concerning website security and protection against malicious attacks. Each article in the series focuses on unique blacklist strategies designed to protect sites transparently, effectively, and efficiently. The five articles culminate in the release of the next generation 3G Blacklist.

For the record, here is a quick summary of the entire Building the 3G Blacklist series:

Building the 3G Blacklist, Part 1
Improving Site Security by Recognizing and Exploiting Server Attack Patterns: In this first article of the series, I examine the process of identifying attack patterns and trends and using them to immunize against future attacks.
Building the 3G Blacklist, Part 2
Improving Site Security by Preventing Malicious Query-String Exploits: In this second article, I present an incredibly powerful method for eliminating malicious query string attacks.
Building the 3G Blacklist, Part 3
Improving Site Security by Selectively Blocking Rogue User Agents: In this third article, I discuss targeted, user-agent blacklisting and present an alternate approach to preventing site access for the most prevalent and malicious user agents. Subsequent articles will focus on key blacklist strategies designed to protect your site transparently, effectively, and efficiently.
Building the 3G Blacklist, Part 4
Improving the RedirectMatch Directives of the Original 2G Blacklist: In this fourth article, I build upon the ideas and techniques presented previously in the series by improving the directives contained in the original, 2G Blacklist.
Building the 3G Blacklist, Part 5
Improving Site Security by Selectively Blocking Individual IPs: In this fifth and final article of the series, I provide the final key to our comprehensive blacklist strategy: selectively blocking individual IPs.
Perishable Press 3G Blacklist
The 3G Blacklist is an extremely effective security strategy for preventing a vast majority of common exploits. The list consists of four distinct parts, providing multiple layers of protection while synergizing into a comprehensive defense mechanism. Further, the 3G Blacklist is designed to be as lightweight and flexible as possible, thereby facilitating periodic cultivation and maintenance.

And of course, the following articles are also involved with the series:

I hope you find the information useful for improving the security of your website. As always, thanks for reading! :)

Subscribe to Perishable Press


5 Responses

TopLeave a comment

[ Gravatar Icon ]

#1Peter

Interesting series, thank you !

I was just wondering how this would fit into your scheme of things :

http://www.0×000000.com/index.php?i=567

[ Gravatar Icon ]

#2Perishable

Hi Peter, thanks for the feedback. That tutorial looks pretty sweet! I haven’t tried the entire method, but many similar directives are currently in effect here at Perishable Press, through either the 3G Blacklist or otherwise. Some great stuff! Thanks for sharing :)

[ Gravatar Icon ]

#3Alissa Miller

I recently encountered a conflict with one of the 3G rules and the WordPress plugin WP Super Cache. The particular 3G rule is the following rules:

RedirectMatch 403 \/\/

I was able to figure out how to fix it, but the explanation is far too long for a comment. You can view it here:

http://blog.nerdstargamer.com/…/perishable-press-3g-blacklist-and-wp-super-cache/

[ Gravatar Icon ]

#4Perishable

Thanks for sharing this information with us, Alissa. Your article is excellent and provides an elegant and practical solution for resolving the Super-Cache/3G conflict. If anyone else is experiencing 403 errors while using the 3G Blacklist with the WordPress Super Cache plugin, read this post for a clean fix ;)
Cheers!

Share your thoughts..

TopRead official comment policy

The rules are simple. Comment intelligently. Stay on-topic. Don’t spam! Suspected spam will be deleted. Use your real name or nickname, not a site name or business name. Using a site name or business name is a good way to get your link or comment removed. Certain comments are moderated; if your comment does not appear after several days, or if you wish to comment privately, contact me. Also, by posting a comment, you grant this site a perpetual license to reproduce your comment, name, and website URL. Lastly, you may use basic HTML markup, but please do not use <pre> tags. Instead, wrap your code with <code> tags. Use a new set of <code> tags for each code term or phrase, as well as for each individual line of code (i.e., multiple lines of code require multiple code tags). Please see the complete comment policy for more information.