Viewers: in countries Watching now:
This course explains how to secure self-hosted WordPress sites, including site configuration, code modification, and the use of free plug-ins. Beginning with the basics of site security, author Jeff Starr explains how to harden a WordPress site by configuring authentication keys, setting proper file permissions, and removing version numbers. The course shows how to implement a firewall, prevent automated spam, and control proxy access, and concludes with a series of advanced tips and site security best practices.
The bad guys are clever when it comes to covering their tracks. Often they will gain access to your site and leave only a small file, or slice of code on the server, without messing with anything else. The small file or code is referred to as a back door and enables the bad guys to come and go as they please. In this screencast, we'll see how to keep a close eye on any changes, so you can take swift action should this occur. Here in our FTP/file editor we're looking at the root directory of our demo site and as we can see here, a typical WordPress installation provides many places, many files and places for bad guys to get in and hide code snippets, other files, evil scripts, and so on, either tucked deep within one of these files or inserted into a directory somewhere. Unless you know exactly what to look for, finding these hacked files in your WordPress installation is virtually impossible, but there is an easy way to keep track of what's being changed on your server.
Using a plug-in called WordPress File Monitor helps us to keep track of any and all changes made to anything on the server, and it's all done automatically. Let's go to the Add New Plugins screen and type in WordPress File Monitor to take a look at the plug in. Click on the Details link for WordPress File Monitor, and it says here that it has not been tested with a current version of WordPress, but in fact it is compatible with WordPress 3.0.
I can say from personal experience that this plug-in works great at the current 3.1.3 version of WordPress. This plug-in has been downloaded many times, enjoys excellent ratings, was updated not too long ago, and as you can see, installation is typical. And since we already have this plug-in installed on our demo site, let's go ahead and click on the WordPress File Monitor link in the Settings menu to configure the plug-in.
Here we are at the Plugins Settings page. Let's for now display a message on the Dashboard whenever there's an active alert. When this plug-in notices a change on the server, we can go to our dashboard and see a notification of what's going on. The Scan Interval, don't go too crazy here. This is something that should be set. 30--actually the default value is fine. Leave it at 30. If anything, change it to 60. I wouldn't go anything less than 15 minutes, especially if you have a lot of traffic on your site.
So let's just leave it at the default and let the plug-in scan your files every 30 minutes. For the Detection Method, let's just leave this at the default setting. We don't want to invoke any potential performance issues, but feel free to experiment if you have time. And here, enter your email address and then replicate it here. For the Notification Format, leave it at detailed so you can see what a detailed alert looks like, and then if it's too much information, maybe change it later.
And here the site root will be pre-filled by the plug-in, but if it doesn't look right or if the plug-in doesn't work, feel free to change it. And here, exclude paths are helpful if you're running specific plug-ins that are changing files constantly or continuously and should be excluded from these alerts. For example, here we have w3 total cache and we've added its directory here, so that the plug-in knows not to worry about changes made in this directory.
Once we have all of our settings in place, click on the Submit button to save our changes, and that's it. Now that we've configured the plug-in, let's see it in action. We go to the FTP/file editor and we open a random file, which we've done, and let's make a change. A good way of modifying a file without actually changing anything is to simply tab down, add some text, and then remove your changes, and click Save, and put the file back up on the server.
Then we return to the File Monitor settings page and run a test by clicking Performs Scan Now. It may take a moment, especially if you have a lot of files and aha! The plug-in has noticed the change. We can click this link here to view changes and clear this alert, which is also available from the WordPress dashboard. Click on View changes and clear this alert and you will see the changes we've made, both for this tutorial and previous tutorials.
When we're done we click Remove Alert after we've inspected the changes. If there's anything that you see that you did not change, you're in a better position to take immediate action. We've been using WordPress File Monitor at our Digging into WordPress site for over a year, and with much success. It's a great way to keep an eye on changes in an easy automated way. If our site is ever hacked, we'll know exactly which files have been added, deleted, or edited. In this screencast, we've seen how to improve the security of our site by keeping a close eye on changes made to the server.
We do this with a plug-in called WordPress File Monitor, which is free and easy to install--highly recommended to increase the security of your WordPress site.
There are currently no FAQs about WordPress 3: Developing Secure Sites.
Access exercise files from a button right under the course name.
Search within course videos and transcripts, and jump right to the results.
Remove icons showing you already watched videos if you want to start over.
Make the video wide, narrow, full-screen, or pop the player out of the page into its own window.