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

Server and file problems


Check any other sites that you have on the same server, WordPress-powered or not. If those are down, is the server? Users tend to find problems before their hosting provider, but check with yours, who may or may not own up to a known issue. If you file a ticket, perhaps tipping them off, they may even tip you back with a downtime credit. Also check support and forum pages and, if there is one, your control panel server status widget.

Then again, did you make a server configuration change? If so, revert it and try again.

Had you been managing web files prior to the problem? Did you delete something or change some file or folder permission? Just a thought.

For any server type, check site and server logs for unusual activity such as traffic spikes, stopped processes, or changed file configurations, ownerships and permissions. Check that recent server logins were yours and that there are no new users in the /etc/passwd file or for MySQL administration. If you suspect any kind of infiltration has occurred, then you should change all such passwords.

These latter tasks take time. Often it's best to address them once the site's back on track.