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

WordPress security by ultimate obscurity


Securing WordPress involves a two-pronged campaign, commissioning solid defenses to control access, with assistive distractions to confound the attacker.

These defences, for example, begin with impermeable code and are complimented with things such as a firewall and strong passwords. The distractions, on the other hand, protect nothing directly but, by obscuring information that would otherwise aid an attack, they nonetheless back up the first line of defence.

For instance, say you've got WordPress 3.x.x, the latest version is 3.x.y, and for whatever reason you haven't yet upgraded. Along comes a hacker who knows how to exploit a weakness in 3.x.x. You do have a fallback though: you've hidden your WordPress version. The hacker could still try, successfully, to exploit your site but, rather like an (empty!) alarm housing that persuades a thief to burgle the neighbor instead, the confusion you provide is enough to sway the hacker to seek out a more obvious...