<?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: What Does Privacy Mean in the Information Age?</title>
	<atom:link href="http://secblog.symbian.org/2009/03/24/what-does-privacy-mean-in-the-information-age/feed/" rel="self" type="application/rss+xml" />
	<link>http://secblog.symbian.org/2009/03/24/what-does-privacy-mean-in-the-information-age/</link>
	<description>Keeping your phone, your data and your services safe</description>
	<lastBuildDate>Mon, 15 Feb 2010 15:28:03 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Behavioural Targeting &#171; Symbian Foundation Security Blog</title>
		<link>http://secblog.symbian.org/2009/03/24/what-does-privacy-mean-in-the-information-age/#comment-37</link>
		<dc:creator>Behavioural Targeting &#171; Symbian Foundation Security Blog</dc:creator>
		<pubDate>Thu, 21 May 2009 15:06:28 +0000</pubDate>
		<guid isPermaLink="false">http://sfsecurity.wordpress.com/?p=9#comment-37</guid>
		<description>[...] There was an interesting mix of participants, from government and the civil service (the Home Office had the largest representation of any one organisation) to privacy advocates (Open Rights Group), industry (notably Phorm) and journalists. I wasn&#8217;t the only one who thought this might be relevant to mobile &#8211; several mobile network operators were present. There is clear potential for monitoring significantly more personal information via a mobile device carried with you, compared to a work or home PC.  The first half of the seminar was largely concerned with the concept and value of online identity, and there was a good deal of discussion about how to enable informed consent by users to the use of their personal information. Predictably the regulator thought that regulation was the answer, and technologists thought that technology was the answer. The &#8220;data is the new currency&#8221; idea was wheeled out to justify a need for stronger controls. Personally, I still think that the most important thing is to provide people with simple privacy controls, as I previously mentioned. [...]</description>
		<content:encoded><![CDATA[<p>[...] There was an interesting mix of participants, from government and the civil service (the Home Office had the largest representation of any one organisation) to privacy advocates (Open Rights Group), industry (notably Phorm) and journalists. I wasn&#8217;t the only one who thought this might be relevant to mobile &#8211; several mobile network operators were present. There is clear potential for monitoring significantly more personal information via a mobile device carried with you, compared to a work or home PC.  The first half of the seminar was largely concerned with the concept and value of online identity, and there was a good deal of discussion about how to enable informed consent by users to the use of their personal information. Predictably the regulator thought that regulation was the answer, and technologists thought that technology was the answer. The &#8220;data is the new currency&#8221; idea was wheeled out to justify a need for stronger controls. Personally, I still think that the most important thing is to provide people with simple privacy controls, as I previously mentioned. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig H</title>
		<link>http://secblog.symbian.org/2009/03/24/what-does-privacy-mean-in-the-information-age/#comment-6</link>
		<dc:creator>Craig H</dc:creator>
		<pubDate>Wed, 25 Mar 2009 21:46:53 +0000</pubDate>
		<guid isPermaLink="false">http://sfsecurity.wordpress.com/?p=9#comment-6</guid>
		<description>Tymek, you make some very good points.  You are surely right that unless we have reliable underlying security mechanisms, any privacy controls we put in place would be easily defeated by bad guys looking to steal and exploit personal information.  I do think that it&#039;s still important to consider &lt;em&gt;why&lt;/em&gt; we&#039;re implementing the security mechanisms though, so we can make sure that they are understandable and usable.

A security mechanism that nobody uses is just a waste of space, and your device lock example is an excellent illustration of that.  I do use a device lock PIN on my phone, but I am well aware that I&#039;m an exception to the rule.  It&#039;s not just about ease of use, for people to turn it on they need to first know it&#039;s there and also recognise the value of it, but a device lock that was easier to use (like your gesture PIN example) would certainly be used more.

We are currently preparing the security technology roadmap for future &lt;a href=&quot;http://blog.symbian.org/2009/03/12/introducing-the-release-plan/&quot; rel=&quot;nofollow&quot;&gt;Symbian Platform releases&lt;/a&gt;, and I&#039;d love to give you a &quot;sneaky peek&quot; at the current draft but I&#039;d better not yet (at least until it&#039;s agreed with the contributors!)  All I&#039;ll say for now is, stay tuned and we may have something up our sleeves to help with that ;-)

I also take your point about wiping the device automatically if someone starts tinkering with it.  I think that&#039;s a good feature for devices where the majority of the data is synced with a server (corporate use, typically) but possibly dangerous for the average consumer who doesn&#039;t back up their phone.  They might, say, leave their phone on a table when they go for a comfort break, and if someone just picks it up and starts playing with it, they might not appreciate it being &quot;knackered&quot; and losing all their contacts / photos / bookmarks / etc.

Finally, is mobile technology ready for the responsibility?  Whether it is or not, people are going to be doing these critical things with their smartphones, so we&#039;d better make sure the technology &lt;em&gt;is&lt;/em&gt; good and ready!  I happen to think that the Symbian OS platform security architecture is a very good basis, but I&#039;m not foolish enough to imagine the job is done and we can all go and relax on a beach now :-)</description>
		<content:encoded><![CDATA[<p>Tymek, you make some very good points.  You are surely right that unless we have reliable underlying security mechanisms, any privacy controls we put in place would be easily defeated by bad guys looking to steal and exploit personal information.  I do think that it&#8217;s still important to consider <em>why</em> we&#8217;re implementing the security mechanisms though, so we can make sure that they are understandable and usable.</p>
<p>A security mechanism that nobody uses is just a waste of space, and your device lock example is an excellent illustration of that.  I do use a device lock PIN on my phone, but I am well aware that I&#8217;m an exception to the rule.  It&#8217;s not just about ease of use, for people to turn it on they need to first know it&#8217;s there and also recognise the value of it, but a device lock that was easier to use (like your gesture PIN example) would certainly be used more.</p>
<p>We are currently preparing the security technology roadmap for future <a href="http://blog.symbian.org/2009/03/12/introducing-the-release-plan/" rel="nofollow">Symbian Platform releases</a>, and I&#8217;d love to give you a &#8220;sneaky peek&#8221; at the current draft but I&#8217;d better not yet (at least until it&#8217;s agreed with the contributors!)  All I&#8217;ll say for now is, stay tuned and we may have something up our sleeves to help with that <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>I also take your point about wiping the device automatically if someone starts tinkering with it.  I think that&#8217;s a good feature for devices where the majority of the data is synced with a server (corporate use, typically) but possibly dangerous for the average consumer who doesn&#8217;t back up their phone.  They might, say, leave their phone on a table when they go for a comfort break, and if someone just picks it up and starts playing with it, they might not appreciate it being &#8220;knackered&#8221; and losing all their contacts / photos / bookmarks / etc.</p>
<p>Finally, is mobile technology ready for the responsibility?  Whether it is or not, people are going to be doing these critical things with their smartphones, so we&#8217;d better make sure the technology <em>is</em> good and ready!  I happen to think that the Symbian OS platform security architecture is a very good basis, but I&#8217;m not foolish enough to imagine the job is done and we can all go and relax on a beach now <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tymek Majewski</title>
		<link>http://secblog.symbian.org/2009/03/24/what-does-privacy-mean-in-the-information-age/#comment-5</link>
		<dc:creator>Tymek Majewski</dc:creator>
		<pubDate>Wed, 25 Mar 2009 15:17:35 +0000</pubDate>
		<guid isPermaLink="false">http://sfsecurity.wordpress.com/?p=9#comment-5</guid>
		<description>Re: other privacy issues
I like think about privacy as a the top of the security pyramid, for me they are in the same basket.

I always find it strange that &quot;pin to unlock&quot; approach is not the normal approach - basically anybody can access your whole phone if they can physically get it, and we store more and more sensitive data on our phones. The browser on the device will keep more an more passwords: to our bank account, password to the company&#039;s internal web page etc.
Not everybody will protect these passwords with a master password (if possible) etc.
BTW. With the touchscreen we could have a gesture pin rather than a number pin...

Plus the current OTA locking approach won&#039;t work if someone puts your phone in a Faraday cage - then they can play with it for hours:) The example does not make sense if you want to prevent people from using your phone, but it&#039;s is a valid (exaggerated a bit;) case when someone wants to access your data.

Going few years to the future - my smartphone will be my debit card, my home keys, my car keys etc. Is the mobile technology ready to deal with such responsibility? 

I can see two levels here:
1. Access to that information
2. &#039;If it&#039;s nicked, it&#039;s knackered&#039; approach needs to be applied on the data level.</description>
		<content:encoded><![CDATA[<p>Re: other privacy issues<br />
I like think about privacy as a the top of the security pyramid, for me they are in the same basket.</p>
<p>I always find it strange that &#8220;pin to unlock&#8221; approach is not the normal approach &#8211; basically anybody can access your whole phone if they can physically get it, and we store more and more sensitive data on our phones. The browser on the device will keep more an more passwords: to our bank account, password to the company&#8217;s internal web page etc.<br />
Not everybody will protect these passwords with a master password (if possible) etc.<br />
BTW. With the touchscreen we could have a gesture pin rather than a number pin&#8230;</p>
<p>Plus the current OTA locking approach won&#8217;t work if someone puts your phone in a Faraday cage &#8211; then they can play with it for hours:) The example does not make sense if you want to prevent people from using your phone, but it&#8217;s is a valid (exaggerated a bit;) case when someone wants to access your data.</p>
<p>Going few years to the future &#8211; my smartphone will be my debit card, my home keys, my car keys etc. Is the mobile technology ready to deal with such responsibility? </p>
<p>I can see two levels here:<br />
1. Access to that information<br />
2. &#8216;If it&#8217;s nicked, it&#8217;s knackered&#8217; approach needs to be applied on the data level.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
