<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://gilzimmermann.ulitzer.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Gil Zimmermann</title>
 <link>http://gilzimmermann.ulitzer.com/</link>
 <description>Latest News from Gil Zimmermann</description>
 <language>en</language>
 <copyright>Copyright 2012 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Thu, 17 May 2012 05:26:02 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Five Ways to Protect Company Information in the Cloud</title>
 <link>http://gilzimmermann.ulitzer.com/node/1851360</link>
 <description>If you aren’t a complete technological Luddite, the odds are high that you have stored or worked with corporate information in some sort of cloud environment. Whether you’re using Facebook for marketing purposes or migrating the entire organization’s productivity suite to Google Apps, most – if not all – enterprises are operating in the cloud to some degree whether they know it or not. Given the cost savings and collaboration benefits of cloud productivity offerings, it’s easy to see why companies are making the switch. The one downside to this widespread migration is that organizations are entrusting cloud platforms to house sensitive information without a full understanding of the data security implications.
There are critical measures companies can take to enjoy the same level of security and control as their on-premise data, while taking advantage of the cost savings and collaboration features of the cloud. One caveat for readers: the best practices and terminology outlined below apply specifically to Google Apps and Google Docs. However, the actions that will be discussed can be broadly applied to all other cloud-based productivity apps. &lt;p&gt;&lt;a href=&quot;http://gilzimmermann.ulitzer.com/node/1851360&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 27 May 2011 10:45:00 EDT</pubDate>
 <guid isPermaLink="true">http://gilzimmermann.ulitzer.com/node/1851360</guid>
 <comments>http://gilzimmermann.ulitzer.com/node/1851360#feedback</comments>
</item>
</channel>
</rss>

