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

Service or disservice?


Unnecessary or vulnerable network services, or daemons, that sit listening on ports waiting to process activity not only pose potential risks but also waste resources so, if you don't need it, weed it, then close the port. The first thing is to find out what's running.

Researching services with Netstat

Netstat provides network information, is installed by default (on your local PC as well as on the server), and should be properly understood to help secure a networked machine.

Let's carry out a service check, running netstat as root so we can see associated programs, and adding a grep parameter to specify those services that are listening on ports:

sudo netstat -tap | grep LISTEN

We can see MySQL which will be listening on the internal port 3306. Apache is doing its thing, presumably on port 80, and smtp is busy with e-mail. The SSH daemon sshd is sat nicely on a custom port, 54321. We can confirm the ports by adding the n switch:

sudo netstat -tapn | grep LISTEN

So what...