<?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: Response to &#8220;Assessing the Security Benefits of Cloud Computing&#8221;</title>
	<atom:link href="http://cloudfeed.net/2008/08/27/response-to-assessing-the-security-benefits-of-cloud-computing/feed/" rel="self" type="application/rss+xml" />
	<link>http://cloudfeed.net/2008/08/27/response-to-assessing-the-security-benefits-of-cloud-computing/</link>
	<description>Cloud Computing, Infrastructure-as-a-service, Platform-as-a-Service, Software-as-a-Service</description>
	<pubDate>Wed, 07 Jan 2009 16:59:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Jian Zhen</title>
		<link>http://cloudfeed.net/2008/08/27/response-to-assessing-the-security-benefits-of-cloud-computing/#comment-47</link>
		<dc:creator>Jian Zhen</dc:creator>
		<pubDate>Wed, 27 Aug 2008 22:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://onsaas.net/?p=89#comment-47</guid>
		<description>Thanks Craig for responding. Maybe I didn't really get my point across in the post so I apologize for that. What I was trying to say is that these security benefits are not really about the cloud being more secure, but rather how to use the cloud for performing security tasks. That's all good and I agree with that. I simply had a different expectation when I saw the title.

As for the Cloud == Elastic, I would say elasticity is definitely one of the key properties of cloud computing. I am not sure how I was contradicting myself. My point is that using the cloud for password cracking is a good testament of the elasticity of the cloud, but not a security benefit of the cloud.</description>
		<content:encoded><![CDATA[<p>Thanks Craig for responding. Maybe I didn&#8217;t really get my point across in the post so I apologize for that. What I was trying to say is that these security benefits are not really about the cloud being more secure, but rather how to use the cloud for performing security tasks. That&#8217;s all good and I agree with that. I simply had a different expectation when I saw the title.</p>
<p>As for the Cloud == Elastic, I would say elasticity is definitely one of the key properties of cloud computing. I am not sure how I was contradicting myself. My point is that using the cloud for password cracking is a good testament of the elasticity of the cloud, but not a security benefit of the cloud.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Balding</title>
		<link>http://cloudfeed.net/2008/08/27/response-to-assessing-the-security-benefits-of-cloud-computing/#comment-46</link>
		<dc:creator>Craig Balding</dc:creator>
		<pubDate>Wed, 27 Aug 2008 21:36:01 +0000</pubDate>
		<guid isPermaLink="false">http://onsaas.net/?p=89#comment-46</guid>
		<description>It seems IANITL (I Am Not Immune To Linkbait) ;-).

You seem to be assuming that virtualization implies storage on demand.  In my experience this isn't the case - provisioning cannot be taken for granted - additional storage or CPU isn't available on tap (or if it is, the tap runs dry when there are multiple requests).  So if I want to test security patches, I can't assume I have double the diskspace available (or triple if I'm testing combinations). Maybe I do, maybe I don't but its not predictable.  With the Cloud I can assume that (or its broken ;-).  The point I'm trying to make here is its the coupling of virtualization and pay per drink (read: instant availability and metered resourcing) that gives rise to many of these benefits; i.e. the Cloud.  As an example, when you write that the password cracking benefit isn't a benefit of the cloud per se, rather of the elasticity property of the cloud, aren't you kinda contradicting yourself in the sense that Cloud == Elastic?

Also, re: "the flip side"....if you are going to quote me, at least quote the whole sentence :-).  I wrote: "Also, for space reasons, I’m purposely not including the ‘flip side’ to these benefits, however if you read this blog regularly you should recognise some."  If you read the rest of the blog you'll find I mostly comment on the flip side ;-).

P.S The 'potential' in potential benefits was not a disclaimer - it was a call to action.  These benefits are not implied by default - some you have to take action to gain entitlement (e.g. forensics).</description>
		<content:encoded><![CDATA[<p>It seems IANITL (I Am Not Immune To Linkbait) ;-).</p>
<p>You seem to be assuming that virtualization implies storage on demand.  In my experience this isn&#8217;t the case - provisioning cannot be taken for granted - additional storage or CPU isn&#8217;t available on tap (or if it is, the tap runs dry when there are multiple requests).  So if I want to test security patches, I can&#8217;t assume I have double the diskspace available (or triple if I&#8217;m testing combinations). Maybe I do, maybe I don&#8217;t but its not predictable.  With the Cloud I can assume that (or its broken ;-).  The point I&#8217;m trying to make here is its the coupling of virtualization and pay per drink (read: instant availability and metered resourcing) that gives rise to many of these benefits; i.e. the Cloud.  As an example, when you write that the password cracking benefit isn&#8217;t a benefit of the cloud per se, rather of the elasticity property of the cloud, aren&#8217;t you kinda contradicting yourself in the sense that Cloud == Elastic?</p>
<p>Also, re: &#8220;the flip side&#8221;&#8230;.if you are going to quote me, at least quote the whole sentence :-).  I wrote: &#8220;Also, for space reasons, I’m purposely not including the ‘flip side’ to these benefits, however if you read this blog regularly you should recognise some.&#8221;  If you read the rest of the blog you&#8217;ll find I mostly comment on the flip side ;-).</p>
<p>P.S The &#8216;potential&#8217; in potential benefits was not a disclaimer - it was a call to action.  These benefits are not implied by default - some you have to take action to gain entitlement (e.g. forensics).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
