<?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>John Crumpton &#187; security</title>
	<atom:link href="http://www.johncrumpton.com/category/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johncrumpton.com</link>
	<description></description>
	<lastBuildDate>Tue, 11 May 2010 20:57:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Website security checklist</title>
		<link>http://www.johncrumpton.com/website-security-checklist/</link>
		<comments>http://www.johncrumpton.com/website-security-checklist/#comments</comments>
		<pubDate>Fri, 29 May 2009 11:07:56 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://www.johncrumpton.com/?p=93</guid>
		<description><![CDATA[A quick security checklist for your website, whether you&#8217;re running Joomla, Zencart or a bespoke content management system.

Choose a complicated password, at least 10 characters alpha-numeric including letters, numbers and upper-and-lower-case. Use Goodpassword.com to generate it
Create a new login for each person that needs to administer the site and don&#8217;t share login details. That way [...]]]></description>
			<content:encoded><![CDATA[<p>A quick security checklist for your website, whether you&#8217;re running Joomla, Zencart or a bespoke content management system.</p>
<ol>
<li>Choose a complicated password, at least 10 characters alpha-numeric including letters, numbers and upper-and-lower-case. Use <a href="http://www.goodpassword.com/" target="_blank">Goodpassword.com</a> to generate it</li>
<li>Create a new login for each person that needs to administer the site and don&#8217;t share login details. That way you have an audit trail to track down the source of the compromise</li>
<li>Use encrypted connections for accessing server files, such as <a href="http://filezilla-project.org/" target="_blank">FileZilla</a> which supports SFTP or <a href="http://winscp.net/eng/index.php" target="_blank">WinSCP</a></li>
<li>Create a administrator user account with unique name and delete your administrator user</li>
<li>Rename your administrator or admin folder to something unique and include numbers in the name</li>
<li>Once your content management system is configured, change the configure.php file to chmod 444 (read only)</li>
<li>On folders you&#8217;d like to protect from being accessed, for example the images folder, use a .htaccess to stop browsing with the following code:
<pre lang="Javascript" line="n" colla="+">Options -Indexes</pre>
</li>
<li>Keep all files CHMOD 644. If you need to edit the files, set to read-write before making changes.</li>
<li>Keep all folders CHMOD 755</li>
<li>Stay up-to-date with the  latest software and patches for your CMS</li>
<li>Check log files for suspicious activity regularly</li>
<li>Remove unneeded templates</li>
<li>Backup regularly</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.johncrumpton.com/website-security-checklist/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
