<?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>Wordpress Security &#187; Fundamentals</title>
	<atom:link href="http://wpsecure.org/category/fundamentals/feed/" rel="self" type="application/rss+xml" />
	<link>http://wpsecure.org</link>
	<description>How to Secure Your WordPress Blog</description>
	<lastBuildDate>Mon, 05 Oct 2009 05:47:50 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The Basics of Blog Security</title>
		<link>http://wpsecure.org/the-basics-of-blog-security/</link>
		<comments>http://wpsecure.org/the-basics-of-blog-security/#comments</comments>
		<pubDate>Sun, 04 Oct 2009 12:59:13 +0000</pubDate>
		<dc:creator>David Turnbull</dc:creator>
				<category><![CDATA[Fundamentals]]></category>

		<guid isPermaLink="false">http://wpsecure.org/?p=74</guid>
		<description><![CDATA[I&#8217;m doubtful that I&#8217;ll cover every Wordpress security trick within this guide. There&#8217;s simply too many options available. What I can do though is provide you with some fundamentals that can then be applied towards your own efforts in securing your blog.
Unpredictability
Hackers thrive on predictability. They predict that many peoples passwords are in fact &#8220;password&#8221;, [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m doubtful that I&#8217;ll cover every Wordpress security trick within this guide. There&#8217;s simply too many options available. What I can do though is provide you with some fundamentals that can then be applied towards your own efforts in securing your blog.</p>
<h3>Unpredictability</h3>
<p>Hackers thrive on predictability. They predict that many peoples passwords are in fact &#8220;password&#8221;, or that their username is probably their real name or some default value such as &#8220;admin&#8221;. Be unpredictable.</p>
<h3>Common sense</h3>
<p>Use complex passwords. Don&#8217;t submit sensitive information to dodgy sites. Scan your computer for viruses (or just use a Mac). The common sense side of things may be dull and unsexy but it works (otherwise it wouldn&#8217;t be common sense).</p>
<h3>Prevent</h3>
<p>Put security measures in place <em>today</em>, so you don&#8217;t need to worry about fixing anything tomorrow.</p>
<h3>&#8230;and Cure</h3>
<p>But no security system is perfect, so make sure you have a comprehensive backup system in place in case you need to recover.</p>
<h3>Simplify</h3>
<p><strong>Have less to secure</strong>. Delete unnecessary online accounts, and share as little data as you can via social networks.</p>
<h3  class="related_post_title">You might also want to read...</h3><ul class="related_post"><li><a href="http://wpsecure.org/wp-db-backup/" title="WP DB Backup">WP DB Backup</a></li><li><a href="http://wpsecure.org/delete-the-default-administrator/" title="Delete the Default Administrator">Delete the Default Administrator</a></li><li><a href="http://wpsecure.org/secure-wordpress/" title="Secure WordPress">Secure WordPress</a></li><li><a href="http://wpsecure.org/hide-login-errors/" title="Hide Login Errors">Hide Login Errors</a></li><li><a href="http://wpsecure.org/move-wp-config-php/" title="Move wp-config.php">Move wp-config.php</a></li><li><a href="http://wpsecure.org/updating-wordpress/" title="Updating WordPress">Updating WordPress</a></li><li><a href="http://wpsecure.org/plugin-wp-spamfree/" title="Plugin: WP-SpamFree">Plugin: WP-SpamFree</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://wpsecure.org/the-basics-of-blog-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->