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

Added protection for wp-config.php


The wp-config.php file, containing your WordPress database credentials, is for many of us the most sensitive web file on the server. It merits special attention.

Assuming you've followed the tips in Chapter 6, your configuration file is seriously solid already, barring a server exploit or administrative error. Barring a server exploit or administrative error? Precisely. Let's throw something else at it.

Moving wp-config.php above the WordPress root

This involves cutting the file from its WordPress root location and pasting it a level above, outside of the public web files. The platform will find it there, but some plugins won't. In that case, have a word with the plugin author or swap the plugin. Failing that, you'll have to weigh up the merit of this move against the loss of functionality.

Less value for non-root installations

The previous move is more powerful when WordPress lives in your site's root. Then, by shifting the wp-config.php above the public web...