<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Clearing the Cloud Part II &#124;A Ray of Sunshine On A Cloudy Day  &#124;&#124; Cloud Computing Security</title>
	<atom:link href="http://arielsilverstone.com/cloud-computing-security/clearing-the-cloud-ii-cloud-computing-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://arielsilverstone.com/cloud-computing-security/clearing-the-cloud-ii-cloud-computing-security/</link>
	<description>Intelligent Business Security</description>
	<lastBuildDate>Mon, 16 Jan 2012 04:58:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tweets that mention Clearing the Cloud Part II &#124;A Ray of Sunshine On A Cloudy Day &#124;&#124; Cloud Computing Security &#124; The Security Blog -- Topsy.com</title>
		<link>http://arielsilverstone.com/cloud-computing-security/clearing-the-cloud-ii-cloud-computing-security/comment-page-1/#comment-444</link>
		<dc:creator>Tweets that mention Clearing the Cloud Part II &#124;A Ray of Sunshine On A Cloudy Day &#124;&#124; Cloud Computing Security &#124; The Security Blog -- Topsy.com</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://arielsilverstone.com/?p=3282#comment-444</guid>
		<description>[...] This post was mentioned on Twitter by Jaime Chanaga, SilverstoneA. SilverstoneA said: RT @jaimechanaga: @SilverstoneA Good article on cloud security, thanks for sharing http://bit.ly/3quUtn TY for RT! [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Jaime Chanaga, SilverstoneA. SilverstoneA said: RT @jaimechanaga: @SilverstoneA Good article on cloud security, thanks for sharing <a href="http://bit.ly/3quUtn" rel="nofollow">http://bit.ly/3quUtn</a> TY for RT! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christofer Hoff</title>
		<link>http://arielsilverstone.com/cloud-computing-security/clearing-the-cloud-ii-cloud-computing-security/comment-page-1/#comment-443</link>
		<dc:creator>Christofer Hoff</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://arielsilverstone.com/?p=3282#comment-443</guid>
		<description>Ariel:

Good piece overall. However, as I mentioned to you previously, your comment regarding the &quot;CSA model&quot; being divergent and &quot;exceedingly complex&quot; in comparison to NIST&#039;s is both inaccurate and unfortunate.

The SaaS, PaaS and IaaS delivery models in the CSA document were all taken from NISTs paper as were the bulk of the deployment models (public, private and hybrid) with the difference being NIST&#039;s community cloud versus CSA&#039;s managed cloud.

You&#039;re comparing apples to donkeys inasmuch as you are trying to compare the underlying semantics of cloud composition/architectural definition (NIST&#039;s/CSA&#039;s) to a security reference model featuring confidentiality, integrity, availability, etc.

They are orthogonal. 

The reason we have the architecture chapter is to define the context. The other 14 domains explore the security ramifications related to such.

I&#039;m still unclear as to what makes any of the CSA/NIST definitions &quot;exceedingly complex.&quot;

Perhaps the v2 document which is coming will make it less so.

Regards,

/Hoff</description>
		<content:encoded><![CDATA[<p>Ariel:</p>
<p>Good piece overall. However, as I mentioned to you previously, your comment regarding the &#8220;CSA model&#8221; being divergent and &#8220;exceedingly complex&#8221; in comparison to NIST&#8217;s is both inaccurate and unfortunate.</p>
<p>The SaaS, PaaS and IaaS delivery models in the CSA document were all taken from NISTs paper as were the bulk of the deployment models (public, private and hybrid) with the difference being NIST&#8217;s community cloud versus CSA&#8217;s managed cloud.</p>
<p>You&#8217;re comparing apples to donkeys inasmuch as you are trying to compare the underlying semantics of cloud composition/architectural definition (NIST&#8217;s/CSA&#8217;s) to a security reference model featuring confidentiality, integrity, availability, etc.</p>
<p>They are orthogonal. </p>
<p>The reason we have the architecture chapter is to define the context. The other 14 domains explore the security ramifications related to such.</p>
<p>I&#8217;m still unclear as to what makes any of the CSA/NIST definitions &#8220;exceedingly complex.&#8221;</p>
<p>Perhaps the v2 document which is coming will make it less so.</p>
<p>Regards,</p>
<p>/Hoff</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Served from: arielsilverstone.com @ 2012-02-08 08:26:18 by W3 Total Cache -->
