<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Breach Watch</title>
	<atom:link href="http://breachwatch.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://breachwatch.com</link>
	<description>Data breaches and regulatory activities</description>
	<lastBuildDate>Sun, 16 Jun 2013 21:40:42 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>News Group Newspapers</title>
		<link>http://breachwatch.com/2013/05/21/news-group-newspapers/</link>
		<comments>http://breachwatch.com/2013/05/21/news-group-newspapers/#comments</comments>
		<pubDate>Tue, 21 May 2013 18:04:16 +0000</pubDate>
		<dc:creator>BreachMaster</dc:creator>
				<category><![CDATA[ICO undertaking]]></category>
		<category><![CDATA[Newspaper]]></category>
		<category><![CDATA[Private sector]]></category>
		<category><![CDATA[Loss of Personal Data]]></category>
		<category><![CDATA[Malicious]]></category>
		<category><![CDATA[Website]]></category>

		<guid isPermaLink="false">http://breachwatch.com/?p=2996</guid>
		<description><![CDATA[Breach details How much &#8216;Thousands&#8217; according to some press reports , a &#8216;large amount&#8217; described in the undertaking and TechEye claimed 500,000. Why A server hosting part of The Sun newspaper&#8217;s website had, unnoticed by the data controller, been repurposed &#8230; <a href="http://breachwatch.com/2013/05/21/news-group-newspapers/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p id="top" />
<p id="top">
<h4 class="Breachdetails">Breach details</h4>
<table class="Breachdetails">
<tbody>
<tr>
<td " class="Breachdetailsleft">What</td>
<td class="Breachdetailsright">Customers&#8217; personal data, some several years old.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">How much</td>
<td class="Breachdetailsright"><a href="http://www.infosecurity-magazine.com/view/19818/sun-website-hack-ico-investigates-whilst-news-international-apologises/" target="_blank">&#8216;Thousands&#8217; according to some press reports </a>, a &#8216;large amount&#8217; described in the undertaking and <a href="http://news.techeye.net/security/lulzsec-hackers-jailed" target="_blank"> TechEye claimed 500,000</a>.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">When</td>
<td class="Breachdetailsright">July 2011</td>
</tr>
<tr>
<td "class="Breachdetailsleft">Why</td>
<td class="Breachdetailsright">A server hosting part of The Sun newspaper&#8217;s website had, unnoticed by the data controller, been repurposed several years earlier, and was subsequently compromised by a malicious attacker (Lulzsec). Further weaknesses had also been identified but remained unrectified prior to the attack.</td>
</tr>
</tbody>
</table>
<h4 class="BWComments">BW Comments</h4>
<table class="BWComments">
<tbody>
<tr>
<td class="BWComments"><em>It is surprising that a large organisation such as News Group Newspapers made such simple information security mistakes. Firstly in retaining data they no longer needed when they re-built a server for a new role, but more worryingly that they had previously had a penetration test but had not rectified the vulnerabilities identified by the tester.</em>
</td>
</tr>
</tbody>
</table>
<h4 class="Regulatoryaction">Regulatory action</h4>
<table class="Regulatoryaction">
<tbody>
<tr>
<td " class="Regulatoryactionleft">Regulator</td>
<td class="Regulatoryactionright"><acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym></td>
</tr>
<td " class="Regulatoryactionleft">Action</td>
<td class="Regulatoryactionright">Undertaking to comply with the fifth and seventh data protection principles</td>
</tr>
<tr>
<td class="Regulatoryactionleft">When</td>
<td class="Regulatoryactionright">9 November 2011</td>
</tr>
<tr>
<td class="Regulatoryactionleft">Details</td>
<td class="Regulatoryactionright">Along with the usual staff awareness and training, technical security controls on the web server were to be improved and implemented by 31 December 2011 (i.e. compliance with the seventh principle), and any customer data collected to be cleared regularly according to a defined retention and disposal policy (compliance with the fifth principle).</td>
</tr>
</tbody>
</table>
<h4 class="BWObservations">BW Observations</h4>
<table class="BWObservations">
<tbody>
<tr>
<td class="BWObservations"><em>This undertaking was not released until the <a href="http://www.bbc.co.uk/news/technology-22552753">criminal trial of the UK-based Lulzsec hackers</a> was concluded. It is interesting that the <acronym title='Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.'>ICO</acronym> didn&#8217;t see fit to consider a monetary penalty notice as the breach appears to meet the right criteria.<br />
<UL>
<li>There was a breach of the fifth and seventh principles.</li>
<li>There had been a previous penetration test, so the Sun knew of the vulnerability.</li>
<li>It seems that a significant volume of data was lost and then circulated on the Internet. Although it wasn&#8217;t sensitive personal data, the volume of the data should be enough to pass the &#8216;likely to cause distress&#8217; test especially given the data was posted to the Internet &#8212; i.e. the breach of confidentiality happened, it was not something that might happen if the lost data were exposed.</li>
</ul>
<p>This undertaking should be contrasted with the <a href="2013/01/24/sony-computer-entertainment-europe/">Sony MPN</a> that was also the result of Lulzsec&#8217;s activities and it will be informative to see if the <acronym title='Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.'>ICO</acronym>&#8216;s choice of an undertaking for the Sun is mentioned at Sony&#8217;s appeal to the Information Tribunal. Less charitable commentators may view this soft approach to News Group Newspapers as another example of the Commissioner&#8217;s fear of the UK press.<br />
</em></td>
</tr>
</tbody>
</table>
<h4 class="BWLinks">Links</h4>
<table class="BWLinks">
<tbody>
<tr>
<td class="BWLinks"><a href="http://breachwatch.com/wp-content/uploads/2013/05/news-group-newspapers-undertaking.pdf" target="_blank">View PDF of the News Group Newspapers Undertaking (Breach Watch Archive)</a></td>
</tr>
<tr>
<td class="BWLinks"><a href="http://www.ico.org.uk/enforcement/~/media/documents/library/Data_Protection/Notices/news-group-newspapers-undertaking.ashx" target="_blank">View PDF of the News Group Newspapers Undertaking (Via <acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym> Website)</a></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://breachwatch.com/2013/05/21/news-group-newspapers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Burnett Practice</title>
		<link>http://breachwatch.com/2013/05/13/the-burnett-practice/</link>
		<comments>http://breachwatch.com/2013/05/13/the-burnett-practice/#comments</comments>
		<pubDate>Mon, 13 May 2013 17:01:48 +0000</pubDate>
		<dc:creator>BreachMaster</dc:creator>
				<category><![CDATA[ICO undertaking]]></category>
		<category><![CDATA[Medical Practices]]></category>
		<category><![CDATA[Private sector]]></category>
		<category><![CDATA[Loss of Sensitive Personal Data]]></category>
		<category><![CDATA[Malicious]]></category>

		<guid isPermaLink="false">http://breachwatch.com/?p=2975</guid>
		<description><![CDATA[Breach details How much About 175 records. Why The email service provider that the practice used wasn&#8217;t suitable to send sensitive medical results because it didn&#8217;t provide the appropriate technical security measures. As a result the practice&#8217;s email account was &#8230; <a href="http://breachwatch.com/2013/05/13/the-burnett-practice/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p id="top" />
<p id="top">
<h4 class="Breachdetails">Breach details</h4>
<table class="Breachdetails">
<tbody>
<tr>
<td " class="Breachdetailsleft">What</td>
<td class="Breachdetailsright">Names and email addresses.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">How much</td>
<td class="Breachdetailsright">About 175 records.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">When</td>
<td class="Breachdetailsright">3 October 2012 or earlier</td>
</tr>
<tr>
<td "class="Breachdetailsleft">Why</td>
<td class="Breachdetailsright">The email service provider that the practice used wasn&#8217;t suitable to send sensitive medical results because it didn&#8217;t provide the appropriate technical security measures. As a result the practice&#8217;s email account was hacked.</td>
</tr>
</tbody>
</table>
<h4 class="BWComments">BW Comments</h4>
<table class="BWComments">
<tbody>
<tr>
<td class="BWComments"><em>Organisations should view this as an indication that if cloud-based, web-email services are used, services that offer two-factor authentication (e.g. Google Authenticator) should be selected.</em>
</td>
</tr>
</tbody>
</table>
<h4 class="Regulatoryaction">Regulatory action</h4>
<table class="Regulatoryaction">
<tbody>
<tr>
<td " class="Regulatoryactionleft">Regulator</td>
<td class="Regulatoryactionright"><acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym></td>
</tr>
<td " class="Regulatoryactionleft">Action</td>
<td class="Regulatoryactionright">Undertaking to comply with the seventh data protection principle</td>
</tr>
<tr>
<td class="Regulatoryactionleft">When</td>
<td class="Regulatoryactionright">26 April 2013</td>
</tr>
<tr>
<td class="Regulatoryactionleft">Details</td>
<td class="Regulatoryactionright">The practice must use secure means of communication for test results &#8211; email can only be used if its security can be guaranteed. A security policy that is adequate to transfer patient data securely must be put in place, and staff must be made aware of this and trained.</td>
</tr>
</tbody>
</table>
<h4 class="BWObservations">BW Observations</h4>
<table class="BWObservations">
<tbody>
<tr>
<td class="BWObservations"><em>Based on previous decisions, the loss of 175 medical records would seem to be a candidate for a Monetary Penalty rather than an undertaking. However, in this case the Commissioner would have struggled to satisfy the &#8216;known or should have known&#8217; test given that most people (incorrectly) assume their email is generally safe from third party attack.</em></td>
</tr>
</tbody>
</table>
<h4 class="BWLinks">Links</h4>
<table class="BWLinks">
<tbody>
<tr>
<td class="BWLinks"><a href="http://breachwatch.com/wp-content/uploads/2013/05/burnett-practice-undertaking.pdf" target="_blank">View PDF of The Burnett Practice Undertaking (Breach Watch Archive)</a></td>
</tr>
<tr>
<td class="BWLinks"><a href="http://www.ico.gov.uk/enforcement/~/media/documents/library/Data_Protection/Notices/burnett-practice-undertaking.ashx" target="_blank">View PDF of The Burnett Practice Undertaking (Via <acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym> Website)</a></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://breachwatch.com/2013/05/13/the-burnett-practice/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>East Riding of Yorkshire Council</title>
		<link>http://breachwatch.com/2013/04/16/east-riding-of-yorkshire-council/</link>
		<comments>http://breachwatch.com/2013/04/16/east-riding-of-yorkshire-council/#comments</comments>
		<pubDate>Tue, 16 Apr 2013 14:48:03 +0000</pubDate>
		<dc:creator>BreachMaster</dc:creator>
				<category><![CDATA[ICO undertaking]]></category>
		<category><![CDATA[Local Government]]></category>
		<category><![CDATA[Public sector]]></category>
		<category><![CDATA[Loss of Sensitive Personal Data]]></category>
		<category><![CDATA[Physical Records]]></category>
		<category><![CDATA[Subject Access Request]]></category>
		<category><![CDATA[Verbal remark]]></category>

		<guid isPermaLink="false">http://breachwatch.com/?p=2954</guid>
		<description><![CDATA[Breach details How much One record and one verbal remark. Why Sensitive personal data about one family was mistakenly included in the response to a subect access request made by another family; and in a seperate incident a student social &#8230; <a href="http://breachwatch.com/2013/04/16/east-riding-of-yorkshire-council/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p id="top" />
<p id="top">
<h4 class="Breachdetails">Breach details</h4>
<table class="Breachdetails">
<tbody>
<tr>
<td " class="Breachdetailsleft">What</td>
<td class="Breachdetailsright">Sensitive personal data was inappropriately disclosed.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">How much</td>
<td class="Breachdetailsright">One record and one verbal remark.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">When</td>
<td class="Breachdetailsright">April/May 2012</td>
</tr>
<tr>
<td "class="Breachdetailsleft">Why</td>
<td class="Breachdetailsright">Sensitive personal data about one family was mistakenly included in the response to a subect access request made by another family; and in a seperate incident a student social worker revealed to the parent of a child under assessmet the first name of the peron who had made an anonymous referral about that parent.</td>
</tr>
</tbody>
</table>
<h4 class="BWComments">BW Comments</h4>
<table class="BWComments">
<tbody>
<tr>
<td class="BWComments"><em>To follow.</em>
</td>
</tr>
</tbody>
</table>
<h4 class="Regulatoryaction">Regulatory action</h4>
<table class="Regulatoryaction">
<tbody>
<tr>
<td " class="Regulatoryactionleft">Regulator</td>
<td class="Regulatoryactionright"><acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym></td>
</tr>
<td " class="Regulatoryactionleft">Action</td>
<td class="Regulatoryactionright">Undertaking to comply with the seventh data protection principle</td>
</tr>
<tr>
<td class="Regulatoryactionleft">When</td>
<td class="Regulatoryactionright">4 April 2013</td>
</tr>
<tr>
<td class="Regulatoryactionleft">Details</td>
<td class="Regulatoryactionright">Both incidents indicated a general lack of data protection awareness and training, along with a lack of management or checking procedures relating to subject access requests and supervision of non-employees, such as students on placement. However in this instance, the risk of substantial damage or distress was considered remote. The data controller undertakes to comply with the Seventh Principle with special regard to training, checking responses to subject access requests, reviewing existing policies and implementing new security measures where necessary.</td>
</tr>
</tbody>
</table>
<h4 class="BWObservations">BW Observations</h4>
<table class="BWObservations">
<tbody>
<tr>
<td class="BWObservations"><em>To follow.</em></td>
</tr>
</tbody>
</table>
<h4 class="BWLinks">Links</h4>
<table class="BWLinks">
<tbody>
<tr>
<td class="BWLinks"><a href="http://breachwatch.com/wp-content/uploads/2013/04/east_riding_undertaking.pdf" target="_blank">View PDF of the East Riding of Yorkshire Council Undertaking (Breach Watch Archive)</a></td>
</tr>
<tr>
<td class="BWLinks"><a href="http://www.ico.org.uk/enforcement/~/media/documents/library/Data_Protection/Notices/east_riding_undertaking.ashx" target="_blank">View PDF of the East Riding of Yorkshire Council Undertaking (Via <acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym> Website)</a></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://breachwatch.com/2013/04/16/east-riding-of-yorkshire-council/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DM Design Bedrooms</title>
		<link>http://breachwatch.com/2013/03/18/dm-design-bedroom-ltd/</link>
		<comments>http://breachwatch.com/2013/03/18/dm-design-bedroom-ltd/#comments</comments>
		<pubDate>Mon, 18 Mar 2013 17:15:46 +0000</pubDate>
		<dc:creator>BreachMaster</dc:creator>
				<category><![CDATA[ICO monetary penalty]]></category>
		<category><![CDATA[ICO PECR]]></category>
		<category><![CDATA[Private sector]]></category>
		<category><![CDATA[Malicious]]></category>
		<category><![CDATA[Policy Breach]]></category>
		<category><![CDATA[Privacy and Electronic Communications Act]]></category>

		<guid isPermaLink="false">http://breachwatch.com/?p=2932</guid>
		<description><![CDATA[Breach details How much An unknown number of direct marketing calls resulting in 1,945 TPS complaints and an unspecified number of complaints directly to the ICO. Why Ignored requirement to screen call lists against the Telephone Preference Service (TPS) or &#8230; <a href="http://breachwatch.com/2013/03/18/dm-design-bedroom-ltd/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p id="top" />
<p id="top">
<h4 class="Breachdetails">Breach details</h4>
<table class="Breachdetails">
<tbody>
<tr>
<td " class="Breachdetailsleft">What</td>
<td class="Breachdetailsright">
Serious breach of the Privacy and Electronic Communications Regulations (PECR).<br />
A high volume of unsolicited marketing calls to consumers that had registered with the Telephone Preference Service (TPS) that continued despite customer complaints and requests to unsubscribe.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">How much</td>
<td class="Breachdetailsright">An unknown number of direct marketing calls resulting in 1,945 TPS complaints and an unspecified number of complaints directly to the <acronym title='Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.'>ICO</acronym>.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">When</td>
<td class="Breachdetailsright">June 2011 to November 2012</td>
</tr>
<tr>
<td "class="Breachdetailsleft">Why</td>
<td class="Breachdetailsright">Ignored requirement to screen call lists against the Telephone Preference Service (TPS) or maintain an opt-out register.</td>
</tr>
</tbody>
</table>
<h4 class="BWComments">BW Comments</h4>
<table class="BWComments">
<tbody>
<tr>
<td class="BWComments"><em>After initial contact from the <acronym title='Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.'>ICO</acronym>, the unsolicited calls continued and some reported to the Commissioner were described as aggressive.</em>
</td>
</tr>
</tbody>
</table>
<h4 class="Regulatoryaction">Regulatory action</h4>
<table class="Regulatoryaction">
<tbody>
<tr>
<td " class="Regulatoryactionleft">Regulator</td>
<td class="Regulatoryactionright"><acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym></td>
</tr>
<td " class="Regulatoryactionleft">Action</td>
<td class="Regulatoryactionright">Monetary penalty of £90,000</td>
</tr>
<tr>
<td class="Regulatoryactionleft">When</td>
<td class="Regulatoryactionright">20 March 2013</td>
</tr>
</tbody>
</table>
<h4 class="Whyregulatoracted">Why the regulator acted</h4>
<table class="Whyregulatoracted">
<tbody>
<tr>
<td " class="Whyregulatoractedleft">Breach of act</td>
<td class="Whyregulatoractedright">Breach of Regulation 21: repeatedly ignored provisions that marketing calls should not be made to individuals who had registered with TPS.</td>
</tr>
<tr>
<td class="Whyregulatoractedleft">Known or should have known</td>
<td class="Whyregulatoractedright">Concerns over PECR obligations were first raised by the Commissioner in 2004. The volume of complaints made before and after the Commissioner&#8217;s letter of May 2012 would have made the company aware that they were continually breaching regulations.</td>
</tr>
<tr>
<td class="Whyregulatoractedleft">Likely to cause damage or distress</td>
<td class="Whyregulatoractedright">The overall level of distress was assessed as substantial due to the very large numbers of individuals affected. A small number of individuals also personally suffered substantial levels of distress.</td>
</tr>
</tbody>
</table>
<h4 class="BWObservations">BW Observations</h4>
<table class="BWObservations">
<tbody>
<tr>
<td class="BWObservations"><em>That DM Design breached the PECR by not screening against the the TPS register and maintaining their own opt-out list is not debatable. The volume of calls and complaints are significant (although we are not told what the average or maximum level of complaints are to the TPS in respect of a company other than &#8220;they [DM Design] were one of the organisations about which the most complaints were received&#8221;). What&#8217;s interesting is the <acronym title='Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.'>ICO</acronym> again used the same justification as the <a href="/2012/11/28/tetrus-telecoms/">Tetrus Telecommunications MPN</a> to determine the s55A(1)(b) &#8216;substantial damage or distress test&#8217; &ndash; that although the distress in each individual case was not considerable, the cumulative effect of the distress caused by the totality of all calls made in contravention of PECR met the Commissioner&#8217;s threshold of substantial distress.</em></td>
</tr>
</tbody>
</table>
<h4 class="BWLinks">Links</h4>
<table class="BWLinks">
<tbody>
<tr>
<td class="BWLinks"><a href="http://breachwatch.com/wp-content/uploads/2013/03/dm_design_bedrooms_monetary_penalty_notice.pdf" target="_blank">View PDF of the DM Bedroom Design Ltd Monetary Penalty Notice (Breach Watch Archive)</a></td>
</tr>
<tr>
<td class="BWLinks"><a href="http://www.ico.gov.uk/enforcement/~/media/documents/library/Data_Protection/Notices/dm_design_bedrooms_monetary_penalty_notice.ashx" target="_blank">View PDF of the DM Bedroom Design Ltd Monetary Penalty Notice (Via <acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym> Website)</a></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://breachwatch.com/2013/03/18/dm-design-bedroom-ltd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nursing and Midwifery Council</title>
		<link>http://breachwatch.com/2013/02/15/nursing-and-midwifery-council/</link>
		<comments>http://breachwatch.com/2013/02/15/nursing-and-midwifery-council/#comments</comments>
		<pubDate>Fri, 15 Feb 2013 17:34:33 +0000</pubDate>
		<dc:creator>BreachMaster</dc:creator>
				<category><![CDATA[ICO monetary penalty]]></category>
		<category><![CDATA[NHS]]></category>
		<category><![CDATA[cd]]></category>
		<category><![CDATA[Loss of Sensitive Personal Data]]></category>
		<category><![CDATA[Lost in Post]]></category>
		<category><![CDATA[Unencrypted]]></category>

		<guid isPermaLink="false">http://breachwatch.com/?p=2868</guid>
		<description><![CDATA[Breach details How much Unspecified but small number of records including two vulnerable children&#8217;s details. Details and allegations against a medical practitioner. Why In an echo of the infamous HMRC breach of 2007, three DVDs containing unencrypted data relating to &#8230; <a href="http://breachwatch.com/2013/02/15/nursing-and-midwifery-council/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p id="top" />
<p id="top">
<h4 class="Breachdetails">Breach details</h4>
<table class="Breachdetails">
<tbody>
<tr>
<td " class="Breachdetailsleft">What</td>
<td class="Breachdetailsright">Loss of sensitive personal data (medical and details relating to legal proceedings).</td>
</tr>
<tr>
<td "class="Breachdetailsleft">How much</td>
<td class="Breachdetailsright">Unspecified but small number of records including two vulnerable children&#8217;s details. Details and allegations against a medical practitioner.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">When</td>
<td class="Breachdetailsright">07 October 2011</td>
</tr>
<tr>
<td "class="Breachdetailsleft">Why</td>
<td class="Breachdetailsright">In an echo of the infamous HMRC breach of 2007, three DVDs containing unencrypted data relating to a &#8216;fitness to practice hearing&#8217; went missing somewhere between the Nursing and Midwifery Council&#8217;s offices and the hotel where the hearing was due to take place. Although the package was sent by courier, the data on the DVDs was unencrypted.</td>
</tr>
</tbody>
</table>
<h4 class="BWComments">BW Comments</h4>
<table class="BWComments">
<tbody>
<tr>
<td class="BWComments"><em>Two of the fundamental lesons that every Data Controller should have learned from the HMRC breach were:</p>
<ol>
<li>Always use couriers when sending personal data on physical media.</li>
<p><Li>Always encrypt data on physical media such as CDs or DVDs.</li>
</ol>
<p>Although the Nursing and Midwifery Council use a courier, the sensitive personal data was not encrypted. As soon as anything went wrong, enforcement action was bound to follow. </em>
</td>
</tr>
</tbody>
</table>
<h4 class="Regulatoryaction">Regulatory action</h4>
<table class="Regulatoryaction">
<tbody>
<tr>
<td " class="Regulatoryactionleft">Regulator</td>
<td class="Regulatoryactionright"><acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym></td>
</tr>
<td " class="Regulatoryactionleft">Action</td>
<td class="Regulatoryactionright">Monetary penalty of £ 150,000</td>
</tr>
<tr>
<td class="Regulatoryactionleft">When</td>
<td class="Regulatoryactionright">12 February 2013</td>
</tr>
</tbody>
</table>
<h4 class="Whyregulatoracted">Why the regulator acted</h4>
<table class="Whyregulatoracted">
<tbody>
<tr>
<td " class="Whyregulatoractedleft">Breach of act</td>
<td class="Whyregulatoractedright"> Breach of the seventh principle: the Council failed to take appropriate organisational measures against unauthorised processing of personal data, such as encrypting the data on the DVDs.</td>
</tr>
<tr>
<td class="Whyregulatoractedleft">Known or should have known</td>
<td class="Whyregulatoractedright">The Council was used to dealing with sensitive data and was aware of the potential damage release of the data would cause. The Commissioner also highlighted his own <a href="http://www.ico.gov.uk/news/current_topics/Our_approach_to_encryption.aspx">guidance on the encryption of portable media</a>, dating back to 2007.</td>
</tr>
<tr>
<td class="Whyregulatoractedleft">Likely to cause damage or distress</td>
<td class="Whyregulatoractedright">The DVDs contained the medical information of third parties, including two vulnerable children. The Commissioner repeated his usual argument that data subjects would suffer from substantial distress knowing that their confidential and sensitive personal data has been disclosed to unauthorised third parties and that their data may be further disseminated and possibly misused.</td>
</tr>
</tbody>
</table>
<h4 class="BWObservations">BW Observations</h4>
<table class="BWObservations">
<tbody>
<tr>
<td class="BWObservations"><em> Receiving the report of DVDs that appeared to go missing between a sender and recipient will have caused a stressful outbreak of déjà vu in Wilmslow. Although the data lost related to very few individuals, the sensitivity of the data had a bearing on the amount of the penalty. Organisations should be under no illusions that sending any unencrypted personal data on physical media will attract a monetary penalty. </em></td>
</tr>
</tbody>
</table>
<h4 class="BWLinks">Links</h4>
<table class="BWLinks">
<tbody>
<tr>
<td class="BWLinks"><a href="http://breachwatch.com/wp-content/uploads/2013/02/nmc_monetary_penalty_notice.pdf" target="_blank">View PDF of the Nursing and Midwifery Council Monetary Penalty Notice (Breach Watch Archive)</a></td>
</tr>
<tr>
<td class="BWLinks"><a href="http://www.ico.gov.uk/enforcement/~/media/documents/library/Data_Protection/Notices/nmc_monetary_penalty_notice.ashx" target="_blank">View PDF of the Nursing and Midwifery Council Monetary Penalty Notice (Via <acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym> Website)</a></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://breachwatch.com/2013/02/15/nursing-and-midwifery-council/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Leeds City Council</title>
		<link>http://breachwatch.com/2013/01/27/leeds-city-council-2/</link>
		<comments>http://breachwatch.com/2013/01/27/leeds-city-council-2/#comments</comments>
		<pubDate>Sun, 27 Jan 2013 14:19:55 +0000</pubDate>
		<dc:creator>BreachMaster</dc:creator>
				<category><![CDATA[ICO undertaking]]></category>
		<category><![CDATA[Local Government]]></category>
		<category><![CDATA[Public sector]]></category>
		<category><![CDATA[Inappropriate Disclosure of Personal Information]]></category>
		<category><![CDATA[Loss of Personal Data]]></category>
		<category><![CDATA[Loss of Sensitive Personal Data]]></category>
		<category><![CDATA[Third party]]></category>
		<category><![CDATA[Website]]></category>

		<guid isPermaLink="false">http://breachwatch.com/?p=2730</guid>
		<description><![CDATA[Breach details How much An unknown number of records contained in seven Excel spreadsheets, including name, address, date of birth and disability details. Why During migration of the Leeds Initiative website from one server to another, a private area was &#8230; <a href="http://breachwatch.com/2013/01/27/leeds-city-council-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p id="top" />
<p id="top">
<h4 class="Breachdetails">Breach details</h4>
<table class="Breachdetails">
<tbody>
<tr>
<td " class="Breachdetailsleft">What</td>
<td class="Breachdetailsright">Personal and sensitive (health) personal data.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">How much</td>
<td class="Breachdetailsright">An unknown number of records contained in seven Excel spreadsheets, including name, address, date of birth and disability details.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">When</td>
<td class="Breachdetailsright">Not specified.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">Why</td>
<td class="Breachdetailsright">During migration of the Leeds Initiative website from one server to another, a private area was accessible to members of the public because a data processor failed to configure the new server identically to the old server. The site was then not sufficiently tested to identify the problem.</td>
</tr>
</tbody>
</table>
<h4 class="BWComments">BW Comments</h4>
<table class="BWComments">
<tbody>
<tr>
<td class="BWComments"><em>If there&#8217;s public and non-public information on any web server there&#8217;s always an increased risk of data loss, so any changes to internet-facing infrastructure should always be fully tested. Organisations that know the locations and classification of their data are less likely to suffer this type of breach.</em>
</td>
</tr>
</tbody>
</table>
<h4 class="Regulatoryaction">Regulatory action</h4>
<table class="Regulatoryaction">
<tbody>
<tr>
<td " class="Regulatoryactionleft">Regulator</td>
<td class="Regulatoryactionright"><acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym></td>
</tr>
<td " class="Regulatoryactionleft">Action</td>
<td class="Regulatoryactionright">Undertaking to comply with the seventh data protection principle</td>
</tr>
<tr>
<td class="Regulatoryactionleft">When</td>
<td class="Regulatoryactionright">30 November 2012</td>
</tr>
<tr>
<td class="Regulatoryactionleft">Details</td>
<td class="Regulatoryactionright">The data controller is to ensure that clear contractual arrangements are in place with a data processor; that data processors are monitored for compliance with the seventh principle; that technically proficient staff are included at all stages of procurement; and that appropriate security measures are in place to protect personal data.</td>
</tr>
</tbody>
</table>
<h4 class="BWObservations">BW Observations</h4>
<table class="BWObservations">
<tbody>
<tr>
<td class="BWObservations"><em>It looks like Leeds Council are following what appears to be a trend in reporting a breach, and also reporting sensible remedial action at the same time. It is interesting that the same council was also subject to a <a href="/2013/01/01/leeds-city-council/">recent monetary penalty</a>.</em></td>
</tr>
</tbody>
</table>
<h4 class="BWLinks">Links</h4>
<table class="BWLinks">
<tbody>
<tr>
<td class="BWLinks"><a href="http://breachwatch.com/wp-content/uploads/2013/01/leeds_city_council_undertaking.pdf" target="_blank">View PDF of the Leeds City Council Undertaking (Breach Watch Archive)</a></td>
</tr>
<tr>
<td class="BWLinks"><a href="http://www.ico.gov.uk/enforcement/~/media/documents/library/Data_Protection/Notices/leeds_city_council_undertaking.ashx" target="_blank">View PDF of the Leeds City Council Undertaking (Via <acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym> Website)</a></td>
</tr>
</tbody>
</table>
<h4 class="BWLinks">Follow Up</h4>
<table class="BWLinks">
<tbody>
<tr>
<td>The <acronym title='Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.'>ICO</acronym> conducted a follow up assessment on 20 May 2013</td>
</tr>
<tr>
<td class="BWLinks"><a href="http://breachwatch.com/wp-content/uploads/2013/06/undertaking-follow-up-leeds-cc-20130524.pdf" target="_blank">View PDF of the Leeds City Council Undertaking Follow Up (Breach Watch Archive)</a></td>
</tr>
<tr>
<td class="BWLinks"><a href="http://www.ico.org.uk/enforcement/~/media/documents/library/Data_Protection/Notices/undertaking-follow-up-leeds-cc-20130524.ashx" target="_blank">View PDF of the Leeds City Council Undertaking Follow Up (Via <acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym> Website)</a></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://breachwatch.com/2013/01/27/leeds-city-council-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mansfield District Council</title>
		<link>http://breachwatch.com/2013/01/25/mansfield-district-council/</link>
		<comments>http://breachwatch.com/2013/01/25/mansfield-district-council/#comments</comments>
		<pubDate>Fri, 25 Jan 2013 13:09:03 +0000</pubDate>
		<dc:creator>BreachMaster</dc:creator>
				<category><![CDATA[ICO undertaking]]></category>
		<category><![CDATA[Local Government]]></category>
		<category><![CDATA[Public sector]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Inappropriate Disclosure of Personal Information]]></category>
		<category><![CDATA[Multiple Breaches]]></category>
		<category><![CDATA[Policy Breach]]></category>
		<category><![CDATA[Training and education]]></category>

		<guid isPermaLink="false">http://breachwatch.com/?p=2848</guid>
		<description><![CDATA[Breach details How much An undisclosed number of records. Why Correspondence containing personal data was sent in error by the council&#8217;s Revenues and Benefits service to a Mansfield housing association over an extended period. BW Comments What is interesting about &#8230; <a href="http://breachwatch.com/2013/01/25/mansfield-district-council/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p id="top" />
<p id="top">
<h4 class="Breachdetails">Breach details</h4>
<table class="Breachdetails">
<tbody>
<tr>
<td " class="Breachdetailsleft">What</td>
<td class="Breachdetailsright">Personal data of housing benefit claimants was disclosed to the wrong housing association.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">How much</td>
<td class="Breachdetailsright">An undisclosed number of records.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">When</td>
<td class="Breachdetailsright">August 2009 to November 2012</td>
</tr>
<tr>
<td "class="Breachdetailsleft">Why</td>
<td class="Breachdetailsright">Correspondence containing personal data was sent in error by the council&#8217;s Revenues and Benefits service to a Mansfield housing association over an extended period.</td>
</tr>
</tbody>
</table>
<h4 class="BWComments">BW Comments</h4>
<table class="BWComments">
<tbody>
<tr>
<td class="BWComments"><em>What is interesting about this breach is that it was reported to the <acronym title='Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.'>ICO</acronym> by the housing authority that received the data in error, and not Mansfield Council. I suspect that the housing association will first have contacted the Council and after that had no effect on the incorrectly addressed correspondence (the breach continued for three years), alerted the Commissioner. The Council&#8217;s real failing was to not fix the problem when told about it.</em>
</td>
</tr>
</tbody>
</table>
<h4 class="Regulatoryaction">Regulatory action</h4>
<table class="Regulatoryaction">
<tbody>
<tr>
<td " class="Regulatoryactionleft">Regulator</td>
<td class="Regulatoryactionright"><acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym></td>
</tr>
<td " class="Regulatoryactionleft">Action</td>
<td class="Regulatoryactionright">Undertaking to comply with the seventh data protection principle</td>
</tr>
<tr>
<td class="Regulatoryactionleft">When</td>
<td class="Regulatoryactionright">25 January 2013</td>
</tr>
<tr>
<td class="Regulatoryactionleft">Details</td>
<td class="Regulatoryactionright">Employees and any other staff with access to personal data must be made aware of, and trained in, the policy for storage and use of personal data. Training must be provided to contractors as well as staff, and records of training to be maintained.</td>
</tr>
</tbody>
</table>
<h4 class="BWObservations">BW Observations</h4>
<table class="BWObservations">
<tbody>
<tr>
<td class="BWObservations"><em>The breach was almost certainly due to administrative human error; however our view is that the enforcement action was taken as a result of the council not fixing the problem when it was initially alerted. The core problem was that the council didn&#8217;t have a sufficiently robust plan to identify and rectify a data breach when it was first reported. The undertaking should have also included a requirement for the Council to develop and test a breach response plan, which identified data breaches and ensured they were rectified.</em></td>
</tr>
</tbody>
</table>
<h4 class="BWLinks">Links</h4>
<table class="BWLinks">
<tbody>
<tr>
<td class="BWLinks"><a href="http://breachwatch.com/wp-content/uploads/2013/02/mansfield_undertaking.pdf" target="_blank">View PDF of the Mansfield District Council Undertaking (Breach Watch Archive)</a></td>
</tr>
<tr>
<td class="BWLinks"><a href="http://www.ico.gov.uk/enforcement/~/media/documents/library/Data_Protection/Notices/mansfield_undertaking.ashx" target="_blank">View PDF of the Mansfield District Council Undertaking (Via <acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym> Website)</a></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://breachwatch.com/2013/01/25/mansfield-district-council/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sony Computer Entertainment Europe</title>
		<link>http://breachwatch.com/2013/01/24/sony-computer-entertainment-europe/</link>
		<comments>http://breachwatch.com/2013/01/24/sony-computer-entertainment-europe/#comments</comments>
		<pubDate>Thu, 24 Jan 2013 23:29:33 +0000</pubDate>
		<dc:creator>BreachMaster</dc:creator>
				<category><![CDATA[ICO monetary penalty]]></category>
		<category><![CDATA[Private sector]]></category>
		<category><![CDATA[Malicious]]></category>
		<category><![CDATA[Password Protection]]></category>
		<category><![CDATA[Risk Assessment]]></category>

		<guid isPermaLink="false">http://breachwatch.com/?p=2788</guid>
		<description><![CDATA[Breach details How much Redacted. Information Week stated 77 million records. Why In what was perhaps one of the most infamous breaches in recent times, attackers deliberately breached the Sony Playstation Network Platform security and compromised the confidentiality of the &#8230; <a href="http://breachwatch.com/2013/01/24/sony-computer-entertainment-europe/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p id="top" />
<p id="top">
<h4 class="Breachdetails">Breach details</h4>
<table class="Breachdetails">
<tbody>
<tr>
<td " class="Breachdetailsleft">What</td>
<td class="Breachdetailsright">Loss of personal data (names, addresses, email addresses, dates of birth, poorly-protected account passwords). Customers&#8217; payment card details also potentially at risk.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">How much</td>
<td class="Breachdetailsright"><b>Redacted.</b> <a href="http://www.informationweek.com/security/attacks/sony-slapped-with-390000-uk-data-breach/240146918" target="_blank">Information Week stated 77 million records</a>.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">When</td>
<td class="Breachdetailsright">Detected 19 April 2011</td>
</tr>
<tr>
<td "class="Breachdetailsleft">Why</td>
<td class="Breachdetailsright">In what was perhaps one of the most infamous breaches in recent times, attackers deliberately breached the Sony Playstation Network Platform security and compromised the confidentiality of the information stored.</td>
</tr>
</tbody>
</table>
<h4 class="BWComments">BW Comments</h4>
<table class="BWComments">
<tbody>
<tr>
<td class="BWComments"><em>This is the most heavily redacted monetary penalty notice published by the Commissioner. The details of the breach in the MPN are superficial, although there is much general information available elsewhere on the Internet. Essentially the attackers exploited a system vulnerability and extracted data including personal data, poorly-hashed passwords and encrypted payment card data. The MPN makes it clear that the exploited vulnerabilities were publicly known, and that &#8216;appropriate updates were available&#8217;.
<p>
The lessons that all organisations can learn are simple:
<ol>
<li>Patch systems regularly.</li>
<li>Run regular external vulnerability scans against systems.</li>
</ol>
<p> </em>
</td>
</tr>
</tbody>
</table>
<h4 class="Regulatoryaction">Regulatory action</h4>
<table class="Regulatoryaction">
<tbody>
<tr>
<td " class="Regulatoryactionleft">Regulator</td>
<td class="Regulatoryactionright"><acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym></td>
</tr>
<td " class="Regulatoryactionleft">Action</td>
<td class="Regulatoryactionright">Monetary penalty of £ 250,000</td>
</tr>
<tr>
<td class="Regulatoryactionleft">When</td>
<td class="Regulatoryactionright">14 January 2013</td>
</tr>
</tbody>
</table>
<h4 class="Whyregulatoracted">Why the regulator acted</h4>
<table class="Whyregulatoracted">
<tbody>
<tr>
<td " class="Whyregulatoractedleft">Breach of act</td>
<td class="Whyregulatoractedright">Breach of the seventh principle: the data controller failed to ensure appropriate technical measures were taken against unauthorised or unlawful processing of personal data stored on the Newwork Platform, such as additional cryptographic controls to protect passwords and regular patching of vulnerabilities.</td>
</tr>
<tr>
<td class="Whyregulatoractedleft">Known or should have known</td>
<td class="Whyregulatoractedright">Various Sony online networks had previously been the subjects of attacks from hacktivist organisations.<br />
Vast amounts of personal data including financial information were stored on the Network Platform, where system vulnerabilities had not been addressed. The data controller should have anticipated a further attack and, given Sony&#8217;s technical expertise, should have put the necessary technical measures in place.</td>
</tr>
<tr>
<td class="Whyregulatoractedleft">Likely to cause damage or distress</td>
<td class="Whyregulatoractedright">It should have been obvious to the data controller that the loss of the substantial volume of personal data held on the Network Platform was likely to cause substantial harm or substantial distress to the data subjects.</td>
</tr>
</tbody>
</table>
<h4 class="BWObservations">BW Observations</h4>
<table class="BWObservations">
<tbody>
<tr>
<td class="BWObservations"><em><br />
A lack of basic security practices such as poor vulnerability management and what can only be assumed to be weak password hashes (at a guess, unsalted MD5) are sufficient to justify a MPN, especially when you consider the number of accounts and the attractiveness to an attacker. The amount could be seen as excessive given that no sensitive personal data was compromised, however it has to be remembered that some 77 million records were compromised. It is the sheer volume of the data breach that influenced the Commissioner.</p>
<p>The <acronym title='Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.'>ICO</acronym> correctly observed that the poorly-hashed passwords may be able to be used by the attackers to compromise customer&#8217;s accounts at other sites where the customer used the same username and password. This appeared to influence his thoughts on the size of the monetary penalty. However it is interesting to consider whether the poor password management practices of consumers should affect how an organisation chooses to value, and therefore protect, stored passwords. Should passwords be valued as a credential for just the single site, or valued (and protected accordingly) because it is known that many customers&#8217; passwords will also be able to be used to access unrelated sites?</p>
<p><a href="http://www.computing.co.uk/ctg/news/2238805/ico-fines-sony-gbp250-000-for-playstation-network-hack">It has been reported</a> that Sony intends to appeal the MPN to the Information Tribunal.</p>
<p></em></td>
</tr>
</tbody>
</table>
<h4 class="BWLinks">Links</h4>
<table class="BWLinks">
<tbody>
<tr>
<td class="BWLinks"><a href="http://breachwatch.com/wp-content/uploads/2013/01/sony_monetary_penalty_notice.pdf" target="_blank">View PDF of the Sony Computer Entertainment Europe Limited  Monetary Penalty Notice</a> (Breach Watch Archive)</td>
</tr>
<tr>
<td class="BWLinks"><a href="http://www.ico.gov.uk/enforcement/~/media/documents/library/Data_Protection/Notices/sony_monetary_penalty_notice.ashx" target="_blank">View PDF of the Sony Computer Entertainment Europe Limited Monetary Penalty Notice (Via <acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym> Website)</a></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://breachwatch.com/2013/01/24/sony-computer-entertainment-europe/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Prospect</title>
		<link>http://breachwatch.com/2013/01/22/prospect/</link>
		<comments>http://breachwatch.com/2013/01/22/prospect/#comments</comments>
		<pubDate>Tue, 22 Jan 2013 21:25:02 +0000</pubDate>
		<dc:creator>BreachMaster</dc:creator>
				<category><![CDATA[ICO undertaking]]></category>
		<category><![CDATA[Private sector]]></category>
		<category><![CDATA[Trade Union]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Loss of Sensitive Personal Data]]></category>
		<category><![CDATA[Password Protection]]></category>

		<guid isPermaLink="false">http://breachwatch.com/?p=2768</guid>
		<description><![CDATA[Breach details How much About 19,000 records. Why Two files containing member data were sent as part of a tendering process to an unknown email address in error. The files were encrypted but the password was also sent seperately to &#8230; <a href="http://breachwatch.com/2013/01/22/prospect/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p id="top" />
<p id="top">
<h4 class="Breachdetails">Breach details</h4>
<table class="Breachdetails">
<tbody>
<tr>
<td " class="Breachdetailsleft">What</td>
<td class="Breachdetailsright">Loss of sensitive personal information (Union membership).</td>
</tr>
<tr>
<td "class="Breachdetailsleft">How much</td>
<td class="Breachdetailsright">About 19,000 records.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">When</td>
<td class="Breachdetailsright">08 Dec 2011</td>
</tr>
<tr>
<td "class="Breachdetailsleft">Why</td>
<td class="Breachdetailsright">Two files containing member data were sent as part of a tendering process to an unknown email address in error. The files were encrypted but the password was also sent seperately to the same address.</td>
</tr>
</tbody>
</table>
<h4 class="BWComments">BW Comments</h4>
<table class="BWComments">
<tbody>
<tr>
<td class="BWComments"><em>This breach illustrates two issues that all Data Controllers need to be aware of. The first is that test data should always be anonymised, not only does it increase the risk of breaching the seventh principle, but it will also breach the first and second principles; although interestingly the <acronym title='Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.'>ICO</acronym> only took action in respect of the seventh principle. Secondly, any encryption is only as good as the key (password) management &#8211; passwords should always be sent at a minimum by a separate channel.</em>
</td>
</tr>
</tbody>
</table>
<h4 class="Regulatoryaction">Regulatory action</h4>
<table class="Regulatoryaction">
<tbody>
<tr>
<td " class="Regulatoryactionleft">Regulator</td>
<td class="Regulatoryactionright"><acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym></td>
</tr>
<td " class="Regulatoryactionleft">Action</td>
<td class="Regulatoryactionright">Undertaking to comply with the seventh data protection principle</td>
</tr>
<tr>
<td class="Regulatoryactionleft">When</td>
<td class="Regulatoryactionright">16 Jan 2013</td>
</tr>
<tr>
<td class="Regulatoryactionleft">Details</td>
<td class="Regulatoryactionright">The data controller to ensure that adequate policies are in place to cover transfer of data to third parties, that such data is minimised and anonymised, that all staff receive data protection training, and that appropriate security measures are in place to protect personal data.</td>
</tr>
</tbody>
</table>
<h4 class="BWObservations">BW Observations</h4>
<table class="BWObservations">
<tbody>
<tr>
<td class="BWObservations"><em> Although this was a sizeable breach of some 19,000 records of sensitive personal data, the <acronym title='Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.'>ICO</acronym> obviously decided that an undertaking was more appropriate given the potential harm that could result.</em></td>
</tr>
</tbody>
</table>
<h4 class="BWLinks">Links</h4>
<table class="BWLinks">
<tbody>
<tr>
<td class="BWLinks"><a href="http://breachwatch.com/wp-content/uploads/2013/01/prospect_undertaking.pdf" target="_blank">View PDF of the Prospect Undertaking (Breach Watch Archive)</a></td>
</tr>
<tr>
<td class="BWLinks"><a href="http://www.ico.gov.uk/enforcement/~/media/documents/library/Data_Protection/Notices/prospect_undertaking.ashx" target="_blank">View PDF of the Prospect Undertaking (Via <acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym> Website)</a></td>
</tr>
</tbody>
</table>
<h4 class="BWLinks">Follow Up</h4>
<table class="BWLinks">
<tbody>
<tr>
<td>The <acronym title='Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.'>ICO</acronym> conducted a follow up assessment on 15 May 2013</td>
</tr>
<tr>
<td class="BWLinks"><a href="http://breachwatch.com/wp-content/uploads/2013/06/undertaking-follow-up-prospect-20130516.pdf" target="_blank">View PDF of the Leeds City Council Undertaking Follow Up (Breach Watch Archive)</a></td>
</tr>
<tr>
<td class="BWLinks"><a href="http://www.ico.org.uk/enforcement/~/media/documents/library/Data_Protection/Notices/undertaking-follow-up-prospect-20130516.ashx" target="_blank">View PDF of the Leeds City Council Undertaking Follow Up (Via <acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym> Website)</a></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://breachwatch.com/2013/01/22/prospect/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Isle of Anglesey County Council</title>
		<link>http://breachwatch.com/2013/01/22/isle-of-anglesey-county-council-2/</link>
		<comments>http://breachwatch.com/2013/01/22/isle-of-anglesey-county-council-2/#comments</comments>
		<pubDate>Tue, 22 Jan 2013 21:12:56 +0000</pubDate>
		<dc:creator>BreachMaster</dc:creator>
				<category><![CDATA[ICO undertaking]]></category>
		<category><![CDATA[Local Government]]></category>
		<category><![CDATA[Public sector]]></category>
		<category><![CDATA[Inappropriate Disclosure of Personal Information]]></category>
		<category><![CDATA[Lack of Policy]]></category>
		<category><![CDATA[Loss of Personal Data]]></category>
		<category><![CDATA[Loss of Sensitive Personal Data]]></category>
		<category><![CDATA[Physical Records]]></category>

		<guid isPermaLink="false">http://breachwatch.com/?p=2759</guid>
		<description><![CDATA[Breach details How much Unknown Why Documents containing personal data were inappropriately disclosed or disposed of, or put at risk of unauthorised access. The council had an out of date data protection policy, and provided insufficient data protection training. BW &#8230; <a href="http://breachwatch.com/2013/01/22/isle-of-anglesey-county-council-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p id="top" />
<p id="top">
<h4 class="Breachdetails">Breach details</h4>
<table class="Breachdetails">
<tbody>
<tr>
<td " class="Breachdetailsleft">What</td>
<td class="Breachdetailsright">Loss of personal data and in one case loss of sensitive personal data.</td>
</tr>
<tr>
<td "class="Breachdetailsleft">How much</td>
<td class="Breachdetailsright">Unknown</td>
</tr>
<tr>
<td "class="Breachdetailsleft">When</td>
<td class="Breachdetailsright">Several incidents in early 2012</td>
</tr>
<tr>
<td "class="Breachdetailsleft">Why</td>
<td class="Breachdetailsright">Documents containing personal data were inappropriately disclosed or disposed of, or put at risk of unauthorised access. The council had an out of date data protection policy, and provided insufficient data protection training.</td>
</tr>
</tbody>
</table>
<h4 class="BWComments">BW Comments</h4>
<table class="BWComments">
<tbody>
<tr>
<td class="BWComments"><em>The undertaking is very vague, and doesn&#8217;t provide specific details of what happened to cause the data losses, or why.</em>
</td>
</tr>
</tbody>
</table>
<h4 class="Regulatoryaction">Regulatory action</h4>
<table class="Regulatoryaction">
<tbody>
<tr>
<td " class="Regulatoryactionleft">Regulator</td>
<td class="Regulatoryactionright"><acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym></td>
</tr>
<td " class="Regulatoryactionleft">Action</td>
<td class="Regulatoryactionright">Undertaking to comply with the seventh data protection principle</td>
</tr>
<tr>
<td class="Regulatoryactionleft">When</td>
<td class="Regulatoryactionright">20 December 2012</td>
</tr>
<tr>
<td class="Regulatoryactionleft">Details</td>
<td class="Regulatoryactionright">The data conroller is to ensure that all policies and procedures are up to date and in place to support staff who handle personal data and that these will be communicated to all relevant staff along with information governance training.  </td>
</tr>
</tbody>
</table>
<h4 class="BWObservations">BW Observations</h4>
<table class="BWObservations">
<tbody>
<tr>
<td class="BWObservations"><em>It is almost as if the council, as part of its self-reporting, suggested the necessary remedial action.</em></td>
</tr>
</tbody>
</table>
<h4 class="BWLinks">Links</h4>
<table class="BWLinks">
<tbody>
<tr>
<td class="BWLinks"><a href="http://breachwatch.com/wp-content/uploads/2013/01/anglesey_cc_undertaking.pdf" target="_blank">View PDF of the Isle of Anglesey County Council Undertaking (Breach Watch Archive)</a></td>
</tr>
<tr>
<td class="BWLinks"><a href="http://www.ico.gov.uk/enforcement/~/media/documents/library/Data_Protection/Notices/anglesey_cc_undertaking.ashx" target="_blank">View PDF of the Isle of Anglesey County Council Undertaking (Via <acronym title="Information Commissioner’s Office. The UK’s independent authority set up to uphold information rights in the public interest, promoting openness by public bodies and data privacy for individuals.">ICO</acronym> Website)</a></td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://breachwatch.com/2013/01/22/isle-of-anglesey-county-council-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
