<?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:go='http://ns.gigaom.com/'
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: Wanted: One Mobile Device, for a 24/7 Life</title>
	<atom:link href="http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/</link>
	<description></description>
	<lastBuildDate>Sat, 11 Feb 2012 02:47:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Mobile Virtualization Bringing One Phone for Both Work and Play: Tech News &#171;</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-541684</link>
		<dc:creator><![CDATA[Mobile Virtualization Bringing One Phone for Both Work and Play: Tech News &#171;]]></dc:creator>
		<pubDate>Tue, 07 Dec 2010 15:47:21 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-541684</guid>
		<description><![CDATA[[...] to surpass computer sales by the end of 2012. And as enterprise workers buy personal smartphones, they&#8217;re not likely to find it appealing to carry both their own phone and a work phone. I&#8217;d say Krishnamurti has found his use [...]]]></description>
		<content:encoded><![CDATA[<p>[...] to surpass computer sales by the end of 2012. And as enterprise workers buy personal smartphones, they&#8217;re not likely to find it appealing to carry both their own phone and a work phone. I&#8217;d say Krishnamurti has found his use [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gadgespec</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211149</link>
		<dc:creator><![CDATA[Gadgespec]]></dc:creator>
		<pubDate>Sun, 15 Nov 2009 16:17:58 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211149</guid>
		<description><![CDATA[Richard, this DiVitas solution sounds interesting but my question will be what about the battery challenge when it comes to any services that uses WIFI on these cellphones? I am using one of the &lt;a href=&quot;http://www.sakhumzantsi.co.za&quot; rel=&quot;nofollow&quot;&gt;Sakhumzantsi&lt;/a&gt; phones and also have tried a couple of WIFI serices on Nokia N80 and I think for every one WIFI challenges the battery capacity.]]></description>
		<content:encoded><![CDATA[<p>Richard, this DiVitas solution sounds interesting but my question will be what about the battery challenge when it comes to any services that uses WIFI on these cellphones? I am using one of the <a href="http://www.sakhumzantsi.co.za" rel="nofollow">Sakhumzantsi</a> phones and also have tried a couple of WIFI serices on Nokia N80 and I think for every one WIFI challenges the battery capacity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shut Up and Drive! How to Identify &#8212; and Deal With &#8212; Cell Phone Abuse</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211148</link>
		<dc:creator><![CDATA[Shut Up and Drive! How to Identify &#8212; and Deal With &#8212; Cell Phone Abuse]]></dc:creator>
		<pubDate>Sun, 30 Aug 2009 14:02:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211148</guid>
		<description><![CDATA[[...] will acknowledge. The most common productivity killers: obtrusive alerts at all hours of the day, cross-contamination of professional and personal correspondence, and multimedia diversions such as Facebook and [...]]]></description>
		<content:encoded><![CDATA[<p>[...] will acknowledge. The most common productivity killers: obtrusive alerts at all hours of the day, cross-contamination of professional and personal correspondence, and multimedia diversions such as Facebook and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: When the Cell Phone Is the Office Phone, Taxing It Is Wrong &#124; 123 All Reviews</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211147</link>
		<dc:creator><![CDATA[When the Cell Phone Is the Office Phone, Taxing It Is Wrong &#124; 123 All Reviews]]></dc:creator>
		<pubDate>Fri, 12 Jun 2009 17:51:52 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211147</guid>
		<description><![CDATA[[...] standard office hours; we conduct business everywhere, all the time. This makes cell phones a necessary tool for many employees 24/7 (we can debate the merits of that later). For example, I have a cell phone that GigaOM reimburses [...]]]></description>
		<content:encoded><![CDATA[<p>[...] standard office hours; we conduct business everywhere, all the time. This makes cell phones a necessary tool for many employees 24/7 (we can debate the merits of that later). For example, I have a cell phone that GigaOM reimburses [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: When the Cell Phone Is the Office Phone, Taxing It Is Wrong</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211146</link>
		<dc:creator><![CDATA[When the Cell Phone Is the Office Phone, Taxing It Is Wrong]]></dc:creator>
		<pubDate>Fri, 12 Jun 2009 17:29:16 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211146</guid>
		<description><![CDATA[[...] standard office hours; we conduct business everywhere, all the time. This makes cell phones a necessary tool for many employees 24/7 (we can debate the merits of that later). For example, I have a cell phone that GigaOM reimburses [...]]]></description>
		<content:encoded><![CDATA[<p>[...] standard office hours; we conduct business everywhere, all the time. This makes cell phones a necessary tool for many employees 24/7 (we can debate the merits of that later). For example, I have a cell phone that GigaOM reimburses [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211145</link>
		<dc:creator><![CDATA[Barry]]></dc:creator>
		<pubDate>Wed, 27 May 2009 23:10:09 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211145</guid>
		<description><![CDATA[Your point on Device Management companies need to be updated. MobileIron has Selective Wipe Feature allow you to browse the file structure and delete just a selected folder or just encrypted, or just email, and on and on.]]></description>
		<content:encoded><![CDATA[<p>Your point on Device Management companies need to be updated. MobileIron has Selective Wipe Feature allow you to browse the file structure and delete just a selected folder or just encrypted, or just email, and on and on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: McGuire&#8217;s Law &#187; Blog Archive &#187; Observations: Devices - May 23, 2009</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211144</link>
		<dc:creator><![CDATA[McGuire&#8217;s Law &#187; Blog Archive &#187; Observations: Devices - May 23, 2009]]></dc:creator>
		<pubDate>Sun, 24 May 2009 00:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211144</guid>
		<description><![CDATA[[...] Wanted: One Mobile Device, for a 24/7 Life [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Wanted: One Mobile Device, for a 24/7 Life [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211143</link>
		<dc:creator><![CDATA[Richard]]></dc:creator>
		<pubDate>Mon, 18 May 2009 16:00:37 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211143</guid>
		<description><![CDATA[Check out DiVitas Networks: http://blog.divitas.com/blog/divitas-networks/0/0/companies-are-turning-to-divitas-mobile-uc-during-belt-tightening-economy. DiVitas is FMC software that runs on a $99 Nokia E71x and addresses all of the issues mentioned above in addition to saving money (WiFi calls don&#039;t count against the carrier plan and are free of charge).

 - it has Dual Persona, which means you can place private calls and maintain a private database from the native (SIM card) number while business contacts are made from the corporate deskphone number (and reside in an corporate-managed contact database).
- It is IT managed
- You can use corporate Presence and IM directly from the E71x
- FMC enables seamless roaming between WiFi and cellular (free, uninterrupted calling from WiFi)
- WiFi calls have landline-like voice quality so no choppy cellphone calls when you are in WiFi range.
- your mobile phone behaves just like a deskphone (same number, call forward, extension dialing, etc.)]]></description>
		<content:encoded><![CDATA[<p>Check out DiVitas Networks: <a href="http://blog.divitas.com/blog/divitas-networks/0/0/companies-are-turning-to-divitas-mobile-uc-during-belt-tightening-economy" rel="nofollow">http://blog.divitas.com/blog/divitas-networks/0/0/companies-are-turning-to-divitas-mobile-uc-during-belt-tightening-economy</a>. DiVitas is FMC software that runs on a $99 Nokia E71x and addresses all of the issues mentioned above in addition to saving money (WiFi calls don&#8217;t count against the carrier plan and are free of charge).</p>
<p> &#8211; it has Dual Persona, which means you can place private calls and maintain a private database from the native (SIM card) number while business contacts are made from the corporate deskphone number (and reside in an corporate-managed contact database).<br />
- It is IT managed<br />
- You can use corporate Presence and IM directly from the E71x<br />
- FMC enables seamless roaming between WiFi and cellular (free, uninterrupted calling from WiFi)<br />
- WiFi calls have landline-like voice quality so no choppy cellphone calls when you are in WiFi range.<br />
- your mobile phone behaves just like a deskphone (same number, call forward, extension dialing, etc.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sharon Peleg</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211142</link>
		<dc:creator><![CDATA[Sharon Peleg]]></dc:creator>
		<pubDate>Mon, 18 May 2009 09:47:56 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211142</guid>
		<description><![CDATA[Guys, it looks the industry is on the verge of the right solution - Mobile Virtualization. One of the more interesting use-cases promised by all virtualization proponents and OEMs is the one that suggests a &#039;Trusted Domain&#039; for the IT of the organization, immune from any possible SW attack, possibly also storing encrypted data. In such a world, a lost device needs not erase even 1 single bit of data, assuming the right infrastructure will be in place. Even more, it could transmit the stored data (without the ability to block it). Similarly other stake holders can have their &#039;trusted domain&#039; such as operators offering their own managed content &amp; services.
Stretching further the imagination, we could even think of &#039;Occasional Management Authorities&#039; such as public place which require obeying some rule such as muting the ringer. If the user accepts it, the device could automatically temporarily change some function WITHOUT the ability to override it till the device leaves the premises (concert hall, hospital, Airplane, etc.)]]></description>
		<content:encoded><![CDATA[<p>Guys, it looks the industry is on the verge of the right solution &#8211; Mobile Virtualization. One of the more interesting use-cases promised by all virtualization proponents and OEMs is the one that suggests a &#8216;Trusted Domain&#8217; for the IT of the organization, immune from any possible SW attack, possibly also storing encrypted data. In such a world, a lost device needs not erase even 1 single bit of data, assuming the right infrastructure will be in place. Even more, it could transmit the stored data (without the ability to block it). Similarly other stake holders can have their &#8216;trusted domain&#8217; such as operators offering their own managed content &amp; services.<br />
Stretching further the imagination, we could even think of &#8216;Occasional Management Authorities&#8217; such as public place which require obeying some rule such as muting the ringer. If the user accepts it, the device could automatically temporarily change some function WITHOUT the ability to override it till the device leaves the premises (concert hall, hospital, Airplane, etc.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian McTavish</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211141</link>
		<dc:creator><![CDATA[Brian McTavish]]></dc:creator>
		<pubDate>Mon, 18 May 2009 08:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211141</guid>
		<description><![CDATA[Perhaps I&#039;m ignorant of some factor but this seems an inefficient road to go down.
Why does mixed personal/ business data functionality need hardware re-engineering, and why need it happen on the device itself?
Can it not be implemented more flexibly with existing capabilities - e.g. tagging files, directories, and individual records by their owner, determining differential access and remote synchronisation preferences? If I have an easily reinstated copy of my personal data off my phone, why would I care who owns my device or whether they feel the need to wipe it when I leave? I may even *want* that.
Having said that, it is a surprise that the two-lines on one phone option hasn&#039;t advanced further: calls to family via my personal number; boss on the work line. Half-hearted solutions exist: http://www.pixmania.co.uk/uk/uk/xx/16216/xx/25/6/criteresn.html  , and Orange UK used to offer a two-lines one-SIM option. But again, isn&#039;t this best handled centrally: incoming and outgoing routing via the personal/ business status of the contact/ time of day/ my location/ busy status? Exactly the track I understand Google Voice is going down.]]></description>
		<content:encoded><![CDATA[<p>Perhaps I&#8217;m ignorant of some factor but this seems an inefficient road to go down.<br />
Why does mixed personal/ business data functionality need hardware re-engineering, and why need it happen on the device itself?<br />
Can it not be implemented more flexibly with existing capabilities &#8211; e.g. tagging files, directories, and individual records by their owner, determining differential access and remote synchronisation preferences? If I have an easily reinstated copy of my personal data off my phone, why would I care who owns my device or whether they feel the need to wipe it when I leave? I may even *want* that.<br />
Having said that, it is a surprise that the two-lines on one phone option hasn&#8217;t advanced further: calls to family via my personal number; boss on the work line. Half-hearted solutions exist: <a href="http://www.pixmania.co.uk/uk/uk/xx/16216/xx/25/6/criteresn.html" rel="nofollow">http://www.pixmania.co.uk/uk/uk/xx/16216/xx/25/6/criteresn.html</a>  , and Orange UK used to offer a two-lines one-SIM option. But again, isn&#8217;t this best handled centrally: incoming and outgoing routing via the personal/ business status of the contact/ time of day/ my location/ busy status? Exactly the track I understand Google Voice is going down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amir Katz</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211140</link>
		<dc:creator><![CDATA[Amir Katz]]></dc:creator>
		<pubDate>Mon, 18 May 2009 08:00:25 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211140</guid>
		<description><![CDATA[Device management is the optimal solution, leveraging the OMA (Open Mobile Alliance) organization standards, thus ensuring a non-proprietary protocol and wide acceptance across different devices.
Data wiping is already supported by using the LAWMO (Lock And Wipe Management Object), but to fully support the enterprise data management, implementation is required both on the device side (LAWMO client) and on the server side (LAWMO server) - corporate data (documents, contacts, certificates, etc.) must be tagged as such when they are stored on the device and then the LAWMO implementation needs to find those tagged documents/items and delete them upon performing a data wipe operation.]]></description>
		<content:encoded><![CDATA[<p>Device management is the optimal solution, leveraging the OMA (Open Mobile Alliance) organization standards, thus ensuring a non-proprietary protocol and wide acceptance across different devices.<br />
Data wiping is already supported by using the LAWMO (Lock And Wipe Management Object), but to fully support the enterprise data management, implementation is required both on the device side (LAWMO client) and on the server side (LAWMO server) &#8211; corporate data (documents, contacts, certificates, etc.) must be tagged as such when they are stored on the device and then the LAWMO implementation needs to find those tagged documents/items and delete them upon performing a data wipe operation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Balaji Natarajan</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211139</link>
		<dc:creator><![CDATA[Balaji Natarajan]]></dc:creator>
		<pubDate>Mon, 18 May 2009 06:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211139</guid>
		<description><![CDATA[I thought Palm could have gone a step beyond too - in rounding off the Synergy Feature with more differentiators...Kudos on your Cobalt efforts.]]></description>
		<content:encoded><![CDATA[<p>I thought Palm could have gone a step beyond too &#8211; in rounding off the Synergy Feature with more differentiators&#8230;Kudos on your Cobalt efforts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Balaji Natarajan</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211138</link>
		<dc:creator><![CDATA[Balaji Natarajan]]></dc:creator>
		<pubDate>Mon, 18 May 2009 06:40:46 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211138</guid>
		<description><![CDATA[Good analysis Ken...

&quot;The corporate/private data is on a users mobile device, and backed up on a users or companies laptop, and if they’re following good backup processes at home, on a users home computer as well. Wiping a users mobile device with an expectation of removing proprietary corporate information, knowing that, is pointless&quot;

Although I agree it&#039;s common practice to backup corporate data on home computers, it&#039;s important to note whether your IT department is certifying such a move via the Policy document every employee signs off about maintaining the integrity of corporate data 24*7*365....(We can argue that we all do it everyday anyway - that&#039;s a different story..)

Regarding storing personal data on &quot;company-owned&quot; laptops, yes - Google Cloud, Amazon S3 can step up &amp; help - going forward, by storing the personal data on the cloud - but again, not sure if companies would be ready to pay for such tools (when usual IT Policy states usage of &quot;company-owned&quot; devices are restricted for company use only &amp; not personal use)....I do have some casual personal information stored on my company laptop - but i don&#039;t &quot;depend&quot; on it being the primary source of my personal information.

The situation is starkly different when the model = &quot;user-owned&quot; device + &quot;company-paid&quot; services , which seems to be a more prevalent model in smartphones....

Overall, I agree with the theme that this is definitely a broader-picture issue on data ownership models &amp; associated security, storage --- not limited to on-device only. Given the hybrid ownership model between user &amp; company (in terms of smartphones) - i think, this happens to be a key use-case for the broader-picture issue. So any solution should just be a step in the right direction!]]></description>
		<content:encoded><![CDATA[<p>Good analysis Ken&#8230;</p>
<p>&#8220;The corporate/private data is on a users mobile device, and backed up on a users or companies laptop, and if they’re following good backup processes at home, on a users home computer as well. Wiping a users mobile device with an expectation of removing proprietary corporate information, knowing that, is pointless&#8221;</p>
<p>Although I agree it&#8217;s common practice to backup corporate data on home computers, it&#8217;s important to note whether your IT department is certifying such a move via the Policy document every employee signs off about maintaining the integrity of corporate data 24*7*365&#8230;.(We can argue that we all do it everyday anyway &#8211; that&#8217;s a different story..)</p>
<p>Regarding storing personal data on &#8220;company-owned&#8221; laptops, yes &#8211; Google Cloud, Amazon S3 can step up &amp; help &#8211; going forward, by storing the personal data on the cloud &#8211; but again, not sure if companies would be ready to pay for such tools (when usual IT Policy states usage of &#8220;company-owned&#8221; devices are restricted for company use only &amp; not personal use)&#8230;.I do have some casual personal information stored on my company laptop &#8211; but i don&#8217;t &#8220;depend&#8221; on it being the primary source of my personal information.</p>
<p>The situation is starkly different when the model = &#8220;user-owned&#8221; device + &#8220;company-paid&#8221; services , which seems to be a more prevalent model in smartphones&#8230;.</p>
<p>Overall, I agree with the theme that this is definitely a broader-picture issue on data ownership models &amp; associated security, storage &#8212; not limited to on-device only. Given the hybrid ownership model between user &amp; company (in terms of smartphones) &#8211; i think, this happens to be a key use-case for the broader-picture issue. So any solution should just be a step in the right direction!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: One Mobile Device, for a 24/7 Life &#171; Innovation 2.0 and&#8230;</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211137</link>
		<dc:creator><![CDATA[One Mobile Device, for a 24/7 Life &#171; Innovation 2.0 and&#8230;]]></dc:creator>
		<pubDate>Mon, 18 May 2009 06:03:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211137</guid>
		<description><![CDATA[[...] From GIGAOM [...]]]></description>
		<content:encoded><![CDATA[<p>[...] From GIGAOM [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211136</link>
		<dc:creator><![CDATA[Ryan]]></dc:creator>
		<pubDate>Mon, 18 May 2009 04:48:27 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211136</guid>
		<description><![CDATA[I feel that a host-oriented, application-based solution is the best way to go.  While the iphone has its constraints, more phones are coming (Android, etc) that should resolve some of the issues.  Give me a phone that I own, but run apps that the corp deploys.]]></description>
		<content:encoded><![CDATA[<p>I feel that a host-oriented, application-based solution is the best way to go.  While the iphone has its constraints, more phones are coming (Android, etc) that should resolve some of the issues.  Give me a phone that I own, but run apps that the corp deploys.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Wallich</title>
		<link>http://gigaom.com/2009/05/16/wanted-one-mobile-device-for-a-247-life/#comment-211135</link>
		<dc:creator><![CDATA[Ken Wallich]]></dc:creator>
		<pubDate>Sun, 17 May 2009 16:43:47 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=48761#comment-211135</guid>
		<description><![CDATA[While trying to make data taggable on a mobile device might at first seem great in this scenario, as prior commenters have mentioned, the problem is far more general. The corporate/private data is on a users mobile device, and backed up on a users or companies laptop, and if they&#039;re following good backup processes at home,  on a users home computer as well. Wiping a users mobile device with an expectation of removing proprietary corporate information, knowing that, is pointless. Solving the problem of proprietary data at an endpoint is a partial solution. Companies are ultimately still relying on employees following their IP agreement, and removing such data on their own.

Consider the inverse problem, a corporate laptop with a users personal data on it. Upon separation, users would like to remove their private data, personal address book and email certainly, before returning company equipment, but in many scenarios, don&#039;t have the ability to do this.

If you generalize the problem of data tagging, a unified solution presents itself by jumping up and down and waving &quot;hey, over here, look over here&quot;... encrypted storage of data, decrypted on-the-fly with revokable access keys. Think S3. Enhanced with having data cachable on a device, with a timeout on re-authentication so one can work on a document on a plane, for instance, or anywhere 24x7 access to corporate authentication isn&#039;t available.

This also allows individuals to turn off access to personal data on a device after they&#039;ve surrendered it, and viola you&#039;ve also solved the problem for corporate and personal data, stolen mobile devices and laptops. Just revoke access to the data on the device!

A couple existing technologies? S3 from Amazon, and lastpass, a password manager that stores sensitive data encrypted on their servers. Mobile access to S3 exists through many apps on Android and the iPhone, lastpass has an iphone app in development. And, of course, the company who&#039;s building that very solution for all your data? Google. Surprise!

This method doesn&#039;t stop someone who really wants to steal and archive corporate data from doing so, but that&#039;s a significantly harder problem that companies have to deal with on any highly confidential need-to-know information.]]></description>
		<content:encoded><![CDATA[<p>While trying to make data taggable on a mobile device might at first seem great in this scenario, as prior commenters have mentioned, the problem is far more general. The corporate/private data is on a users mobile device, and backed up on a users or companies laptop, and if they&#8217;re following good backup processes at home,  on a users home computer as well. Wiping a users mobile device with an expectation of removing proprietary corporate information, knowing that, is pointless. Solving the problem of proprietary data at an endpoint is a partial solution. Companies are ultimately still relying on employees following their IP agreement, and removing such data on their own.</p>
<p>Consider the inverse problem, a corporate laptop with a users personal data on it. Upon separation, users would like to remove their private data, personal address book and email certainly, before returning company equipment, but in many scenarios, don&#8217;t have the ability to do this.</p>
<p>If you generalize the problem of data tagging, a unified solution presents itself by jumping up and down and waving &#8220;hey, over here, look over here&#8221;&#8230; encrypted storage of data, decrypted on-the-fly with revokable access keys. Think S3. Enhanced with having data cachable on a device, with a timeout on re-authentication so one can work on a document on a plane, for instance, or anywhere 24&#215;7 access to corporate authentication isn&#8217;t available.</p>
<p>This also allows individuals to turn off access to personal data on a device after they&#8217;ve surrendered it, and viola you&#8217;ve also solved the problem for corporate and personal data, stolen mobile devices and laptops. Just revoke access to the data on the device!</p>
<p>A couple existing technologies? S3 from Amazon, and lastpass, a password manager that stores sensitive data encrypted on their servers. Mobile access to S3 exists through many apps on Android and the iPhone, lastpass has an iphone app in development. And, of course, the company who&#8217;s building that very solution for all your data? Google. Surprise!</p>
<p>This method doesn&#8217;t stop someone who really wants to steal and archive corporate data from doing so, but that&#8217;s a significantly harder problem that companies have to deal with on any highly confidential need-to-know information.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

