<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: ISO 2700: Security Asleep?</title>
	<atom:link href="http://www.liquidmatrix.org/blog/2007/05/24/iso-2700-security-asleep/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.liquidmatrix.org/blog/2007/05/24/iso-2700-security-asleep/</link>
	<description>Bringing Fire To The Village: Your Source For Computer, Network &#38; Information Security News from Dave Lewis, Security Blogger</description>
	<pubDate>Sat, 22 Nov 2008 07:30:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Dave Lewis</title>
		<link>http://www.liquidmatrix.org/blog/2007/05/24/iso-2700-security-asleep/#comment-36664</link>
		<dc:creator>Dave Lewis</dc:creator>
		<pubDate>Fri, 25 May 2007 18:15:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/05/24/iso-2700-security-asleep/#comment-36664</guid>
		<description>I wasn't going for that. If you notice all of the postings like that will have "Article Link" at the bottom. I always reference my quotes that way. 

As for Google...not overly concerned with that particular posting. Thanks for the feedback nonetheless.

cheers</description>
		<content:encoded><![CDATA[<p>I wasn&#8217;t going for that. If you notice all of the postings like that will have &#8220;Article Link&#8221; at the bottom. I always reference my quotes that way. </p>
<p>As for Google&#8230;not overly concerned with that particular posting. Thanks for the feedback nonetheless.</p>
<p>cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Newby</title>
		<link>http://www.liquidmatrix.org/blog/2007/05/24/iso-2700-security-asleep/#comment-36663</link>
		<dc:creator>Rob Newby</dc:creator>
		<pubDate>Fri, 25 May 2007 17:22:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/05/24/iso-2700-security-asleep/#comment-36663</guid>
		<description>Yep, I just Googled it and found it straight away. If you type "ISO 2700" into Google, the first few links are to the article you quote and one is to this blog.
If you want to show up in the right searches, you could correct the error and tag it with the correct "ISO27000" and/or "ISO27001".</description>
		<content:encoded><![CDATA[<p>Yep, I just Googled it and found it straight away. If you type &#8220;ISO 2700&#8243; into Google, the first few links are to the article you quote and one is to this blog.<br />
If you want to show up in the right searches, you could correct the error and tag it with the correct &#8220;ISO27000&#8243; and/or &#8220;ISO27001&#8243;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Lewis</title>
		<link>http://www.liquidmatrix.org/blog/2007/05/24/iso-2700-security-asleep/#comment-36659</link>
		<dc:creator>Dave Lewis</dc:creator>
		<pubDate>Fri, 25 May 2007 16:25:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/05/24/iso-2700-security-asleep/#comment-36659</guid>
		<description>"ISO 2700" and the text was actually a direct quote from the CSO article. 

Thanks for your comment!</description>
		<content:encoded><![CDATA[<p>&#8220;ISO 2700&#8243; and the text was actually a direct quote from the CSO article. </p>
<p>Thanks for your comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Newby</title>
		<link>http://www.liquidmatrix.org/blog/2007/05/24/iso-2700-security-asleep/#comment-36654</link>
		<dc:creator>Rob Newby</dc:creator>
		<pubDate>Fri, 25 May 2007 15:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2007/05/24/iso-2700-security-asleep/#comment-36654</guid>
		<description>I've been jumping up and down and waving my arms about this for over ten years!

ISO 2700 is a new one on me, but assuming this means the ISO27000 series, 27000 - 27008, only 2 of them are actually ratified by ISO: 27000 and 27001. The rest are still only proposals as far as I'm aware. 

ISO17799 has been around for donkey's years in various forms, and it has changed regularly. It came from BS7799 created in 1995, which became ISO17799 in 2000, then split into ISO17799-1 and -2, the systems standard and the systems management standard. 

This is why everyone loves it, it's like a clear version of PCI DSS, one for techies and one for management, and never the twain shall meet. Oh yeah, ISO17799-2 became ISO27001 back in 2005.

The constant input and update is what makes it a good security standard which actually provides security rather than other standards which demand compliance. 

You certainly &lt;b&gt;can't&lt;/b&gt; stay asleep if you want to remain compliant with ISO27001.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been jumping up and down and waving my arms about this for over ten years!</p>
<p>ISO 2700 is a new one on me, but assuming this means the ISO27000 series, 27000 - 27008, only 2 of them are actually ratified by ISO: 27000 and 27001. The rest are still only proposals as far as I&#8217;m aware. </p>
<p>ISO17799 has been around for donkey&#8217;s years in various forms, and it has changed regularly. It came from BS7799 created in 1995, which became ISO17799 in 2000, then split into ISO17799-1 and -2, the systems standard and the systems management standard. </p>
<p>This is why everyone loves it, it&#8217;s like a clear version of PCI DSS, one for techies and one for management, and never the twain shall meet. Oh yeah, ISO17799-2 became ISO27001 back in 2005.</p>
<p>The constant input and update is what makes it a good security standard which actually provides security rather than other standards which demand compliance. </p>
<p>You certainly <b>can&#8217;t</b> stay asleep if you want to remain compliant with ISO27001.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
