{"id":477,"date":"2008-03-02T16:01:46","date_gmt":"2008-03-02T21:01:46","guid":{"rendered":"http:\/\/rreynoso.com\/blog\/links-n-junk\/protect-your-neck-securing-your-wordpress-blog\/"},"modified":"2008-03-02T16:01:46","modified_gmt":"2008-03-02T21:01:46","slug":"protect-your-neck-securing-your-wordpress-blog","status":"publish","type":"post","link":"http:\/\/rreynoso.com\/reysapoint\/links-n-junk\/protect-your-neck-securing-your-wordpress-blog\/","title":{"rendered":"Protect Your Neck: Securing Your WordPress Blog"},"content":{"rendered":"

A couple of weeks ago my other site, the Bible Archive, was flagged by google for containing badware. I think its still listed as flagged: I’m just waiting for them to review it again to show that there’s no badware on it. I had a cache on my site that allowed quicker rendering of the site but what wound up happening was that a hacker injected an SQL code so that my site would render a 1 x 1 iframe with a certain w*p*s*t*a*t-s dot i*n*f*0. As it was I had to spend several hours (up till 3 AM) finding this code then removing it. Well, its gone now but here are a few steps for people to learn from my experience and take precautions up front.<\/p>\n

<\/p>\n

    \n
  1. Update your wordpress. <\/strong>Each time a new version comes out, security holes are patched. Each time you don’t upgrade, everybody knows about your security holes.<\/li>\n
  2. Get rid of plugins you don’t use.<\/strong> If you have a plugin you haven’t used, get rid of it. Each plugin has the potential of being an open window into the internet inviting every nefarious hacker inside your virtual home.<\/li>\n
  3. Change your admin username. <\/strong>Don’t simply use the default username for wordpress. Sure you create your own password but that’s not enough. That’s like simply changing the keys for your house while everyone knows what model lock.<\/li>\n
  4. Change your admin password to something devilish. <\/strong>That means words, letters, numbers and symbols people. Instead of using mcfspassword use MC3Fzp@$sw0(r)D. Now that is tight<\/a>.<\/li>\n
  5. Use a different password for your database.<\/strong> People, being forgetful, like to use the same password for everything. Don’t.<\/li>\n
  6. Protect your admin directory.<\/strong> That means adding an .htaccess file linking to an .htpasswd file or a protect directory command through your web servers control panel. With that put a different username and password.<\/li>\n
  7. Protect your ftp account.<\/strong> Personally, I create multiple FTP accounts. My main FTP account is the one given to me by my hosting company. The sub-account is the one I create that only accesses the one folder. That’s the one I’ll use. Always.<\/li>\n
  8. Protect your content and plugin directory.<\/strong>This ones a bit more convoluted but you can set up the.htaccess so that it blocks any weird viewing and limits it only to calling pictures and what not. This isn’t a detailed post but others do have the necessary steps.<\/li>\n
  9. Rename your wordpress database prefixes. <\/strong>You don’t want people attacking your site just because they know you have the default info installed. This site here has the best instructions yet<\/a> if you can’t get it to be changed automatically<\/a>.<\/li>\n
  10. Install a plugin to block information call. <\/strong>You don’t want people to know your version number or what plugins you have installed: so block it to the public. Blogsecurity has some great helps<\/a>.<\/li>\n
  11. Install a plugin that stops certain attacks. <\/strong>The three that you need are here<\/a>.<\/li>\n
  12. Backup<\/strong>. Backup your blog. Backup your database. Save them by Date. Back them up again.<\/li>\n
  13. Go through the white papers. <\/strong>There is a checklist to make sure you’re hitting what needs to be done and that’s right over here<\/a>.<\/li>\n
  14. In fact, subscribe to Blogsecurity’s Feed<\/a>.<\/strong> They constantly have updates on plugins with security holes.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

    A couple of weeks ago my other site, the Bible Archive, was flagged by google for containing badware. I think its still listed as flagged: I’m just waiting for them to review it again to show that there’s no badware on it. I had a cache on my site that allowed quicker rendering of the […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"footnotes":""},"categories":[11],"tags":[76,78,75,77],"class_list":["post-477","post","type-post","status-publish","format-standard","hentry","category-links-n-junk","tag-blogs","tag-hackers","tag-security","tag-wordpress"],"_links":{"self":[{"href":"http:\/\/rreynoso.com\/reysapoint\/wp-json\/wp\/v2\/posts\/477","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/rreynoso.com\/reysapoint\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/rreynoso.com\/reysapoint\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/rreynoso.com\/reysapoint\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/rreynoso.com\/reysapoint\/wp-json\/wp\/v2\/comments?post=477"}],"version-history":[{"count":0,"href":"http:\/\/rreynoso.com\/reysapoint\/wp-json\/wp\/v2\/posts\/477\/revisions"}],"wp:attachment":[{"href":"http:\/\/rreynoso.com\/reysapoint\/wp-json\/wp\/v2\/media?parent=477"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/rreynoso.com\/reysapoint\/wp-json\/wp\/v2\/categories?post=477"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/rreynoso.com\/reysapoint\/wp-json\/wp\/v2\/tags?post=477"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}