<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title> &#187; how to secure wordpress blog</title>
	<atom:link href="http://eitwebguru.com/tag/how-to-secure-wordpress-blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://eitwebguru.com</link>
	<description></description>
	<lastBuildDate>Thu, 09 Feb 2012 05:54:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Steps to Secure WordPress</title>
		<link>http://eitwebguru.com/steps-to-secure-wordpress/</link>
		<comments>http://eitwebguru.com/steps-to-secure-wordpress/#comments</comments>
		<pubDate>Wed, 18 Jan 2012 00:13:06 +0000</pubDate>
		<dc:creator>Milind</dc:creator>
				<category><![CDATA[Softwares]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[how to secure wordpress blog]]></category>
		<category><![CDATA[secure wordpress]]></category>
		<category><![CDATA[wordpress security]]></category>

		<guid isPermaLink="false">http://eitwebguru.com/?p=751</guid>
		<description><![CDATA[Recently I found that many wordpress based websites got hacked or compromised. So, I started searching Internet for security measures which can be took to protect WordPress based websites. Following are some points which I found common on various websites. 1. Vulnerabilities in the WordPress Vulnerabilities of WordPress could be defined as program or script [...]]]></description>
			<content:encoded><![CDATA[<!-- google_ad_section_start --><p style="text-align: justify;"><span style="font-family: Verdana; font-size: small;">Recently I found that many wordpress based websites got hacked or compromised. So, I started searching Internet for security measures which can be took to protect WordPress based websites. Following are some points which I found common on various websites.</span></p>
<p style="text-align: justify;"><span style="font-family: Verdana; font-size: small;"><strong>1. Vulnerabilities in the WordPress</strong><br /> <span style="font-family: Verdana; font-size: small;">Vulnerabilities of WordPress could be defined as program or script that allows an attacker to bypass normal wordpress settings. To avoid such problems, keep your blog updated to latest versions. Older version of WordPress contains old functions and scripts which can be easily hacked.</span></span></p>
<p style="text-align: justify;"><span style="font-family: Verdana; font-size: small;">Also keep your all plugins updated and if you are not using any specific plug-in, delete it from the system.</span></p>
<p style="text-align: justify;"><strong><span style="font-family: Verdana; font-size: small;">2. Secure wp-config.php</span></strong><br /> <span style="font-family: Verdana; font-size: small;">wp-config.php file contains database information like database name, database username, password. By default wp-config.php has 644 permission which means a normal user can easily read your wp-config.php. So, set the permission of the file to 750 which will disable other users to read it.</span></p>
<p style="text-align: justify;"><strong><span style="font-family: Verdana; font-size: small;">3. Rename the administrative account</span></strong><br /> <span style="font-family: Verdana; font-size: small;">When WordPress is installed on a System by default, it uses and sets username &#8220;admin&#8221; as the administrator of the blog. For better security it&#8217;s not suggested to use &#8220;admin&#8221;. After installation you can create a new user with administrator rights and delete &#8220;admin&#8221;.</span></p>
<p style="text-align: justify;"><strong><span style="font-family: Verdana; font-size: small;">4. Hide WordPress version</span></strong><br /> <span style="font-family: Verdana; font-size: small;">If you are running a wordpress version which has know vulnerabilities, then its not a good option to keep your wordpress version open to public. There are many plugins which hide the wordpress version from public OR you can simply add  &#8220;</span><strong>&lt;? php remove_action(&#8216;wp_head&#8217;, &#8216;wp_generator&#8217;.; ?&gt;</strong><span style="font-family: Verdana; font-size: small;">&#8221; in function.php of your theme.</span></p>
<p style="text-align: justify;"><strong><span style="font-family: Verdana; font-size: small;">5. Protect WP-* Folders</span></strong><br /> <span style="font-family: Verdana; font-size: small;">Block wp-* folders from being crawled and index by search engines. This can be done by blocking access to wp-* from robot.txt. Add following line in your robot.txt</span></p>
<p style="text-align: justify;"><strong><span style="font-family: Courier; font-size: small;">Disallow: /wp-*</span></strong></p>
<p style="text-align: justify;"><strong><span style="font-family: Verdana; font-size: small;">6. Firewall Plugins</span></strong><br /> <span style="font-family: Verdana; font-size: small;">There are a few plugins that scans suspicious-looking requests based on rule databases and/or white-lists. BlogSecurity&#8217;s WPIDS plug-in installs &#8220;PHPIDS&#8221;, a generic security layer for PHP applications, while &#8220;WordPress Firewall&#8221; uses some WordPress-tuned pre-configured rules along with a whitelist to screen out attacks without much configuration</span></p>
<p style="text-align: justify;"><strong><span style="font-family: Verdana; font-size: small;">7. Secure WordPress Database</span></strong><br /> <span style="font-family: Verdana; font-size: small;">WordPress is database dependent application for which you need to have a database and database user. For WordPress installation, you simply create a database with user but securing database is also useful for securing you WordPress Blog.</span></p>
<p style="text-align: justify;"><span style="font-family: Verdana; font-size: small;">Following are a few tweaks to secure database<br /><strong>7.1. Grant limited access to a database user:</strong> Create a user to access this database only and grant limited access to SQL commands on this database (select, insert, delete, update, create, drop and alter).</span><br /> <strong><span style="font-family: Verdana; font-size: small;">7.2. Pick a strong database password</span></strong></p>
<p style="text-align: justify;"><strong><span style="font-family: Verdana; font-size: small;">8. Backups</span></strong><br /> <span style="font-family: Verdana; font-size: small;">Always make habit of taking backup of your blog and database at regular intervals and do not depend upon your hosting company&#8217;s backups as it might be possible that the backup they have contains the hacked data. (if the backup run after your blog was hacked) There are many plugins provided by WordPress with the help of which one can take backups.</span></p>
<p style="text-align: justify;"><strong><span style="font-family: Verdana; font-size: small;">9. Strong Passwords</span></strong><br /> <span style="font-family: Verdana; font-size: small;">Creating a Strong Password is another option to protect your blog from getting hacked. Also changing the passwords on weekly or monthly basis will be added protection.</span></p>
<p style="text-align: justify;"><strong><span style="font-family: Verdana; font-size: small;">10. Monitoring Blogs</span></strong><br /> <span style="font-family: Verdana; font-size: small;">As a user/admin of the blogs you will have to regularly monitor your blogs for changes, like any suspicious user get registered or any file of your blog gets changed or you find any suspicious activity contact our support team for deep investigation.</span></p>
<!-- google_ad_section_end -->]]></content:encoded>
			<wfw:commentRss>http://eitwebguru.com/steps-to-secure-wordpress/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

