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

Slamming backdoors and rootkits


With most of the products in this chapter, at least, there's crossover. Two or more products often do similar stuff. Then again, it's a bit like a Venn diagram. Each sector, or product, does its own thing, then there's a doubling up, or redundancy. Different products report in different ways as well though, which assists with analysis and crime scenes.

The point is, gaps are worse than dupes. Crossover is a small price to pay for full coverage which, besides, will never be full coverage anyway. One can but try.

Rootkit detection is a classic example. We've set up OSSEC and that scans on auto-pilot. But it's signature file, while samey, is not the same as that of product B and neither it nor B exactly match that of C. Meanwhile, rootkits and backdoors are particularly nasty little s-h-one-t-s, if you'll pardon the parochial. This malware type needs over-compensation. So, in this category particularly, we'll cover the bases. Meet B and C: