Website Walkthrough – 5 Ways to Make Your WordPress Hack-Proof
Having your blog hacked or worse, stolen right under your nose, is a nightmare. Sure, WordPress improves its standard installation security with every new version it comes out with, but new versions are not invincible and they’re not impermeable. Bottom line – you need to do what you can to help make your WordPress hack-proof.
This website walkthrough shares 5 ways you can make your blog more secure. Shall we start?
1. Upgrade your WordPress. Hate the thought of saying goodbye to WordPress 2.6? Don’t. You need upgrade to the latest WP version, and you need to do it now. Don’t worry; it’s easy. Just look for the Upgrade button in Tools or your dashboard.
2. Update your plugins. Anything old is a security risk. Keep your plugin versions up-to-date.
3. Delete the default user. In this case, it’s Admin so bin this. Replace it with a new user (naturally, this user has admin rights) and create a nickname for this user. That way, the username on public display is not the same as yours.
4. Limit the access to wp-admin. This restricts .htaccess of your wp-admin to your IP. The downside to this security measure, though, is that you will need to update the .htaccess folder whenever you move to another area. You may need another website walkthrough for this; but obviously, this step is out of the question for you if your IP address is dynamic.
5. Install the plugin Login Lockdown. This plugin records the time stamp and IP address whenever someone tries to log in to WordPress and fails. It works great at preventing attempts to discover your password through brute force attacks. If attempts to log in by one IP range exceed the maximum number of tries allowed, the plugin automatically disables the login function.
Of course, there are many more ways you can make your blog hack-proof. This website walkthrough only covers the basics and the ones that are easiest to do. Feel free to look for more! When it comes to website security, it’s better to go over-protect than be sorry.
