<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Scaling your business globally using the cloud</title>
	<atom:link href="http://gigaom.com/2011/10/24/scaling-your-business-globally-using-the-cloud/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2011/10/24/scaling-your-business-globally-using-the-cloud/</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 16:02:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: SL</title>
		<link>http://gigaom.com/2011/10/24/scaling-your-business-globally-using-the-cloud/#comment-667679</link>
		<dc:creator><![CDATA[SL]]></dc:creator>
		<pubDate>Mon, 24 Oct 2011 20:28:42 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=423679#comment-667679</guid>
		<description><![CDATA[Something to consider is risk management, insurance, and privacy when using the cloud (I sent an email to GigaOm suggesting a webinar on the topic). For example, in British Columbia, Canada there is an obscure privacy law that states organizations must store all personal information on servers within Canada. 

Additionally, just because data is stored in a cloud doesn&#039;t mean it shouldn&#039;t be backed up locally. An organization should keep track of what information is stored in a cloud (or anywhere), why, and who has access. For example, I&#039;ve seen organizations collecting social security numbers &quot;because it might be useful&quot; or keeping credit card numbers when they don&#039;t have recurring billing. 

Does your organization have IT/Cloud use policies. For example, password requirements, only using secure connections, only using secure computers, etc. If it&#039;s not covered in a formal, written plan it&#039;s not risk management.

Any time you store any data anywhere (digitally or physically on paper) you are responsible for the safety and security of that data. The recent Sony and RSA SecureID breeches are perfect examples of worst case scenarios when data is lost. It can cost in terms of business interruption, rebuilding customer databases, changing all usernames &amp; passwords, public relations, reputation loss, etc.

Hope that helps and I hope risk management and insurance evolve with technology use.]]></description>
		<content:encoded><![CDATA[<p>Something to consider is risk management, insurance, and privacy when using the cloud (I sent an email to GigaOm suggesting a webinar on the topic). For example, in British Columbia, Canada there is an obscure privacy law that states organizations must store all personal information on servers within Canada. </p>
<p>Additionally, just because data is stored in a cloud doesn&#8217;t mean it shouldn&#8217;t be backed up locally. An organization should keep track of what information is stored in a cloud (or anywhere), why, and who has access. For example, I&#8217;ve seen organizations collecting social security numbers &#8220;because it might be useful&#8221; or keeping credit card numbers when they don&#8217;t have recurring billing. </p>
<p>Does your organization have IT/Cloud use policies. For example, password requirements, only using secure connections, only using secure computers, etc. If it&#8217;s not covered in a formal, written plan it&#8217;s not risk management.</p>
<p>Any time you store any data anywhere (digitally or physically on paper) you are responsible for the safety and security of that data. The recent Sony and RSA SecureID breeches are perfect examples of worst case scenarios when data is lost. It can cost in terms of business interruption, rebuilding customer databases, changing all usernames &amp; passwords, public relations, reputation loss, etc.</p>
<p>Hope that helps and I hope risk management and insurance evolve with technology use.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
