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

Concerning code


Seeing as sites run on code, it would be naïve not to query it before someone else does.

Deleting redundant code

You diligently update active code such as plugins and your theme. Disused code, though, may begin to show cracks, posing a risk. There's no point in retaining unused files on a server, so get your pinny on and have a clean out. Here are some cobwebs:

  • Abandoned plugins and other third party code

  • Old version themes

  • Rusty web file backups sat alongside production files

Spring clean the lot. If you must keep anything, move it above the web root and set the permissions to something like 600. Even better, download locally, and delete it remotely.

Scrutinize widgets, plugins and third party code

Do. Often, you don't know where they've been. Take time to research new additions.

There are approaching 10,000 plugins, for starters, featured in the official repository. Any could be poorly coded, badly maintained, or widely untested. Worse, there's the chance that an add-on masks...