{"id":10554,"date":"2011-02-22T02:09:46","date_gmt":"2011-02-22T01:09:46","guid":{"rendered":"http:\/\/rinf.com\/alt-news\/?p=10554"},"modified":"2014-02-25T12:47:42","modified_gmt":"2014-02-25T12:47:42","slug":"6-tips-to-make-your-wordpress-hack-proof","status":"publish","type":"post","link":"http:\/\/rinf.com\/alt-news\/webmasters\/6-tips-to-make-your-wordpress-hack-proof\/","title":{"rendered":"6 Tips To Make Your  WordPress Hack-Proof"},"content":{"rendered":"<p>by Abdul Karim<\/p>\n<p><a class=\"highslide\" onclick=\"return vz.expand(this)\" href=\"http:\/\/rinf.com\/alt-news\/wp-content\/uploads\/2011\/02\/wp-secure.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/rinf.com\/alt-news\/wp-content\/uploads\/2011\/02\/wp-secure-150x125.jpg\" alt=\"\" title=\"wp-secure\" width=\"150\" height=\"125\" class=\"alignleft size-thumbnail wp-image-10565\" \/><\/a> I never  thought it would actually happen to me, I always thought that getting your blog  hijacked was something that happens to &quot;other people&quot;, but when it  happened to me I was devastated. I foolishly installed a &quot;free&quot; WordPress  theme from an untrusted site. And weeks later I had links appearing all over my  sidebar, and every time I removed them from my blog, they reappeared days  later. I don&#8217;t know what was worse, the fact that my blog was now linking to  bad neighbourhood sites or the fact that I knew there was a backdoor entry in  my WordPress and I didn&#8217;t have a clue how to remove it.<\/p>\n<p> Almost a  year on, and a year wiser, I&#8217;ve learnt quite a few things about WordPress  security and I&#8217;m going to share with you the tips that helped me to lock down  my WordPress blog.<\/p>\n<p> I&#8217;ll be  asking you to perform a few tweaks to your blog, so as always back up both your  database and your files in order to have some way of restoring your blog if  things go pear shaped.<\/p>\n<p><strong>Tip 1: Stay updated<\/strong><\/p>\n<p> This one  comes straight out of chapter &quot;obvious&quot;, but as exploits and  vulnerabilities are discovered, WordPress is fast to implement changes to patch  them up. Having an out of date WordPress running on your blog means that you&#8217;re  one of the remaining sites that are still open to the exploit. Check your back  end administration panel for notifications of potential updates, and make sure  to run them on all of your sites. You may need to have a test blog running with  the same plugins and themes installed in order to run a &quot;guinea pig  test&quot; to make sure they&#8217;re all compatible, before you actually run the  updates on your live sites.<\/p>\n<p><strong>Tip 2: Make Regular Backups<\/strong> <\/p>\n<p> No matter  what security measures you have in place, you need to have good reliable  backups just in case something goes wrong. I really like the <strong>WP-Db-Backup<\/strong> plugin as it automatically creates a backup of my database and sends it to me  via email. You can set the frequency of time it takes to create the backup, I  would advise you to make weekly or daily backups depending on how often the  blog is updated. The WordPress files can be backed up manually via FTP by  connecting to your web server, I make monthly backups of the files as they  aren&#8217;t updated much.<\/p>\n<p> It&#8217;s good  practice to backup your files on an offsite server, I tend to use online  backup services to upload all my music, documents and work related  files using online backup, it&#8217;s a great way for mobile bloggers who work off  laptops to safely backup their files in a safe location. <\/p>\n<p><strong>Tip 3: Lock down your WP-admin<\/strong><\/p>\n<p> Many  users down realise this, but the wp-admin isn&#8217;t as secure as it should be, in  most cases it&#8217;s open for brute force password hackers to repeatedly attack the  login page with a hash file and attempt to gain access to your login.  Thankfully there are great steps you can take to prevent that<\/p>\n<ol start=\"1\" type=\"1\">\n<li>Firstly use a non-default       login name, but default &quot;admin&quot; is set as the login name, change       it to a nickname which isn&#8217;t known to anyone else, you can do this through       another admin account or by editing the wp-users table using phpmyadmin.       Remember to backup your database before doing so.<\/li>\n<li>Install the <strong>login-lockdown<\/strong> plugin for WordPress, it does a great job of deterring brute force       hackers, it will lock down the login page after a set of repeated attempts       from any given IP.<\/li>\n<li>Use a server based password       protection for added security, Google search &quot;htpasswd creator&quot;       to create you htpasswd and htaccess files.<\/li>\n<\/ol>\n<p><strong>Tip 4: Lock down your WP-includes folder<\/strong><\/p>\n<p> Not many  users are aware of this but the \/wp-includes folder is viewable to the public  if your server has enabled directory listing, the problem is the WP-includes  can leave footprints of plugins and WordPress versions which may have security  loopholes and can be exploited. To fix this:<\/p>\n<ol start=\"1\" type=\"1\">\n<li>Create a blank index.html       file and upload it onto \/wp-includes<\/li>\n<li>Or simply add &quot;Options       -Indexes&quot; on a new line in your root .htaccess file, if you don&#8217;t       have one create one. This command turns off directory listing for the that       particular folder and all subfolders, if you upload it onto the root, it       will prevent directory listing for the entire website<\/li>\n<\/ol>\n<p><strong>Tip 5: Stay away from themes and plugins outside of  wordpress.org<\/strong><\/p>\n<p> Simply  put, Always download your plugins and themes through your WordPress admin  pages, they&#8217;re verified and tested by the WordPress team. Many WordPress themes  acquired from outside have encrypted elements in them, some can be just  hyperlinks to other sites, however many are shady enough to leave backdoor  entries into your blog allowing them access onto your blog. <br \/>\n  Themes  and plugins outside of wordpress.org should only be acquired if they are  reliable, do plenty of research before downloading, read up reviews, and even  if there are many positive reviews check for authenticity and authority for  these reviews.<\/p>\n<p><strong>Tip 6: Perform scans before installing unfamiliar  plugins and themes.<\/strong><\/p>\n<p> I highly recommend  the <strong>Wp-Security-Scan<\/strong> plugin, it scans your WordPress installation for  security vulnerabilities, and also scans themes and plugins to detect any  irregular activity, such as encrypted elements and potential backdoor threats,  when installing a new plugin, add it, but before activating run the  Wp-Security-Scan to get the all clear before activating.<br \/>\n  From my  past experience of getting breached, I found <strong>Wp-mal-watch<\/strong> an excellent  plugin, it scans your WordPress blog every night to look for traces of any  security threats, such as suspicious files appearing on your web host, or  unauthorised changes to your WordPress blog.<\/p>\n<p><strong>Conclusion<\/strong><\/p>\n<p> So there  you have it, 6 great tips that you can execute in less than 30 minutes which  will drastically increase the level of security of your WordPress blog. I hope  you&#8217;ve enjoyed this post, and feel free to tweet it and post it on your  frequently visited forums to help out other WordPress bloggers.<\/p>\n<p><em>Karim, author of <a href=\"http:\/\/www.onlinebackupservices.co\">online backup services<\/a>, provides reviews, news and helpful advice relating to online backup and cloud computing services. Use the online backup reviews page to locate the best service suitable for you<\/em>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>by Abdul Karim<br \/> <br \/>\nThis one  comes straight out of chapter &quot;obvious&quot;, but as exploits and  vulnerabilities are discovered, Wordpress is fast to implement changes to patch  them up. Having an out of date Wordpress running on your blog means that you&#8217;re  one of the remaining sites that are still open to the exploit.<\/p>\n","protected":false},"author":1213,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[518],"tags":[378],"class_list":{"0":"post-10554","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-webmasters","7":"tag-wordpress-2"},"_links":{"self":[{"href":"http:\/\/rinf.com\/alt-news\/wp-json\/wp\/v2\/posts\/10554","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/rinf.com\/alt-news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/rinf.com\/alt-news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/rinf.com\/alt-news\/wp-json\/wp\/v2\/users\/1213"}],"replies":[{"embeddable":true,"href":"http:\/\/rinf.com\/alt-news\/wp-json\/wp\/v2\/comments?post=10554"}],"version-history":[{"count":0,"href":"http:\/\/rinf.com\/alt-news\/wp-json\/wp\/v2\/posts\/10554\/revisions"}],"wp:attachment":[{"href":"http:\/\/rinf.com\/alt-news\/wp-json\/wp\/v2\/media?parent=10554"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/rinf.com\/alt-news\/wp-json\/wp\/v2\/categories?post=10554"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/rinf.com\/alt-news\/wp-json\/wp\/v2\/tags?post=10554"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}