Book Image

WordPress 3 Ultimate Security

Book Image

WordPress 3 Ultimate Security

Overview of this book

Most likely – today – some hacker tried to crack your WordPress site, its data and content – maybe once but, with automated tools, very likely dozens or hundreds of times. There's no silver bullet but if you want to cut the odds of a successful attack from practically inevitable to practically zero, read this book. WordPress 3 Ultimate Security shows you how to hack your site before someone else does. You'll uncover its weaknesses before sealing them off, securing your content and your day-to-day local-to-remote editorial process. This is more than some "10 Tips ..." guide. It's ultimate protection – because that's what you need. Survey your network, using the insight from this book to scan for and seal the holes before galvanizing the network with a rack of cool tools. Solid! The WordPress platform is only as safe as the weakest network link, administrator discipline, and your security knowledge. We'll cover the bases, underpinning your working process from any location, containing content, locking down the platform, your web files, the database, and the server. With that done, your ongoing security is infinitely more manageable. Covering deep-set security yet enjoyable to read, WordPress 3 Ultimate Security will multiply your understanding and fortify your site.
Table of Contents (23 chapters)
WordPress 3 Ultimate Security
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Isolating risk with SuPHP


We've addressed open_basedir to sandbox one site's PHP from another. Here's another damage limitation exercise, this time using an Apache module such as SuPHP or FastCGI.

These and similar modules work by making a site's PHP files run under the user-owner rather than as the Apache-group. That way, if one of your .php scripts is manipulated, the damage is limited to your files without affecting my files or those of other users. Apache, on the other hand, has some level of access to the server-wide web files, at least, meaning there's a greater risk of wider attack penetration.

Clearly that's useful and, accordingly, SuPHP is widely employed by shared web hosts. Equally, modules like this spread the risk if you host a bunch of your own sites. Simply create a new user for each and, once set up, a module like SuPHP creates the barrier.

Note

SuPHP vs FastCGI

SuPHP works best for lower traffic and FastCGI for busy sites. If Sod's law says that your traffic sits somewhere in...