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

Local problems


There is no guarantee that anything you do remotely is anything but a short term fix unless you can be sure that your local machine and its web connection haven't been compromised. In some cases, the problem may be entirely local anyway.

Try accessing other sites with the same cache-cleared browser, then using another browser, and then a different PC. If at any stage other sites are working normally then, sure, your site or the server has some problem and, maybe, has been hacked.

Some local breach could still, all the same, be the underlying issue.

Maybe your wireless has been compromised by some sniffer who, for instance, plundered your FTP details and attacked your site. Or you could be being keylogged. It may not be the priority, but run virus and rootkit scans using the tools we looked at in Chapter 3.

If you can, perhaps while running the previously mentioned local tests, use a different PC for the site recovery process. Lose the wireless too, instead using an Ethernet cable.