<?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>Freedom of Information Archives - International Finance</title>
	<atom:link href="https://internationalfinance.com/tag/freedom-of-information/feed/" rel="self" type="application/rss+xml" />
	<link>https://internationalfinance.com/tag/freedom-of-information/</link>
	<description>International Finance - Financial News, Magazine and Awards</description>
	<lastBuildDate>Fri, 15 Mar 2019 08:04:09 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://internationalfinance.com/wp-content/uploads/2020/08/favicon-1-75x75.png</url>
	<title>Freedom of Information Archives - International Finance</title>
	<link>https://internationalfinance.com/tag/freedom-of-information/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>ICO data breach reports late prior to GDPR: Redscan FOI</title>
		<link>https://internationalfinance.com/technology/ico-data-breach-reports-late-prior-gdpr-reveals-redscan-foi/#utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ico-data-breach-reports-late-prior-gdpr-reveals-redscan-foi</link>
					<comments>https://internationalfinance.com/technology/ico-data-breach-reports-late-prior-gdpr-reveals-redscan-foi/#respond</comments>
		
		<dc:creator><![CDATA[International Finance Desk]]></dc:creator>
		<pubDate>Fri, 15 Mar 2019 08:04:09 +0000</pubDate>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[data breach]]></category>
		<category><![CDATA[financial services]]></category>
		<category><![CDATA[FOI]]></category>
		<category><![CDATA[Freedom of Information]]></category>
		<category><![CDATA[GDPR]]></category>
		<category><![CDATA[ICO]]></category>
		<category><![CDATA[Information Commissioner Office]]></category>
		<category><![CDATA[legal firms]]></category>
		<category><![CDATA[redscan]]></category>
		<guid isPermaLink="false">https://internationalfinance.com/?p=23833</guid>

					<description><![CDATA[<p>Financial services (16 days) and legal firms (20 days) were also quicker to disclose breaches to the ICO than general businesses (27 days)</p>
<p>The post <a href="https://internationalfinance.com/technology/ico-data-breach-reports-late-prior-gdpr-reveals-redscan-foi/">ICO data breach reports late prior to GDPR: Redscan FOI</a> appeared first on <a href="https://internationalfinance.com">International Finance</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><u><a href="https://www.redscan.com/" target="_blank" rel="noopener noreferrer" data-saferedirecturl="https://www.google.com/url?q=https://www.redscan.com&amp;source=gmail&amp;ust=1552715242531000&amp;usg=AFQjCNGQSwmbz-tLNHa7-5pj4oz24Hj9Jw">Redscan</a></u>, the threat detection and response specialist,  released new Freedom of Information (FOI) request <span class="il">data</span> from the Information Commissioner’s Office (<span class="il">ICO</span>). It found that businesses routinely delayed <span class="il">data</span> <span class="il">breach</span> disclosure and failed to provide important details to the <span class="il">ICO</span> in the year prior to the GDPR’s enactment.</p>
<p>On average, businesses waited three weeks after discovery to report a <span class="il">breach</span> to the <span class="il">ICO</span>, while the worst offending organisation waited 142 days. The vast majority (91%) of reports to the <span class="il">ICO</span> failed to include important information such as the impact of the <span class="il">breach</span>, recovery process and dates. The FOI also revealed that hackers disproportionately targeted businesses at the weekend, while many reports would be issued to the <span class="il">ICO</span> on a Thursday or Friday—possibly in an attempt to minimise potential media coverage.</p>
<p>Redscan analysed 182 <span class="il">data</span> <span class="il">breach</span> reports triaged by the <span class="il">ICO</span> in the financial year ending April 2018 (relating to ‘general businesses’ as well as financial services and <span class="il">legal</span> <span class="il">firms</span>)*. Key findings include:</p>
<ul>
<li>On average, it took companies 60 days to identify they’d been a victim of a <span class="il">data</span> <span class="il">breach</span>, with one business taking as long as 1320 days</li>
<li>After identifying a <span class="il">breach</span>, it took businesses an average of 21 days to report it to the <span class="il">ICO</span>, while one took as long as 142 days</li>
<li>More than 9 out of 10 companies (93%) did not specify the impact of the <span class="il">breach</span>, or did not know the impact at the time it was reported</li>
<li>Less than a quarter (45 out of 182) of businesses would be compliant with current GDPR requirements, which demand organisations report a <span class="il">breach</span> within 72 hours of discovery</li>
<li>Nearly half of <span class="il">data</span> breaches were reported to the <span class="il">ICO</span> on a Thursday or Friday (87 of 181)</li>
<li>Saturday is the most common day for businesses to fall victim to a <span class="il">data</span> <span class="il">breach—</span>over a quarter of incidents were reported on a Saturday</li>
<li>Financial and <span class="il">legal</span> <span class="il">firms</span> identified and reported breaches more promptly than general businesses</li>
</ul>
<p>“<span class="il">Data</span> breaches are now an operational reality, but detection and response continue to pose a massive challenge to businesses”, said Mark Nicholls, Redscan director of cybersecurity.</p>
<p>“Most companies don’t have the skills, technology or procedures in place to detect breaches when they happen, nor report them in sufficient detail to the <span class="il">ICO</span>. This was a problem before the GDPR and is an even bigger problem now that reporting requirements are stricter.”</p>
<p><strong>On <span class="il">data</span> <span class="il">breach</span> identification/discovery</strong></p>
<p>Redscan’s FOI request <span class="il">reveals</span> that financial services and <span class="il">legal</span> <span class="il">firms</span> were far better at identifying and reporting breaches than general businesses—likely due to increased regulatory awareness and the highly sensitive nature of <span class="il">data</span> processed in these industries. On average, financial services <span class="il">firms</span> took 37 days to identify a <span class="il">breach</span>, <span class="il">legal</span> <span class="il">firms</span> took 25 days, while companies classified as ‘general business’ took 138 days.</p>
<p>38/181 (21%) organisations did not report a <span class="il">breach</span> incident date to the <span class="il">ICO</span>, suggesting they either lacked awareness of or knowingly withheld this important information. A further 46/181 (25%) organisations also failed to report a <span class="il">breach</span> discovery date.</p>
<p>Mark Nicholls: “The fact that so many businesses failed to provide critical details in their initial reports to the <span class="il">ICO</span> says a lot about their ability to pinpoint when attacks occurred and promptly investigate the impact of compromises.</p>
<p>“Without the appropriate controls and procedures in place, identifying a <span class="il">breach</span> can be like finding a needle in a haystack. Attacks are getting more and more sophisticated and, in many cases, companies don’t even know they’ve been hit.”</p>
<p>“In general, <span class="il">firms</span> operating across the financial and <span class="il">legal</span> sectors are among those better prepared to manage <span class="il">data</span> breaches. The fact that even businesses in these high-value sectors were taking two to three weeks to divulge incidents is a key reason why the reporting rules have since been tightened.”</p>
<p><strong>On the weekend threat / Friday disclosures</strong></p>
<p>Mark Nicholls: “Detecting and responding to breaches is now a 24/7 effort. Many organisations lack the technology and expertise they need, which is compounded by a global cybersecurity skills shortage. Resources are stretched even further at weekends, when many IT teams are off-duty—exactly why hackers chose to target businesses out of hours.</p>
<p>“It’s also interesting to note that nearly half of reports to the <span class="il">ICO</span> were submitted on a Thursday or a Friday, good days to bury bad news. This might be overly cynical but I suspect that in many cases,<span class="il">breach</span> disclosure on these days may have a deliberate tactic to minimise negative publicity.”</p>
<p><strong>The impact of the GDPR</strong></p>
<p>Mark Nicholls: “It’s incredibly optimistic to think that businesses are better at preventing and detecting <span class="il">data</span> breaches since the introduction of the GDPR. Despite the prospect of a larger penalty, many are still struggling to understand and implement the solutions they need to achieve compliance.”</p>
<p>The post <a href="https://internationalfinance.com/technology/ico-data-breach-reports-late-prior-gdpr-reveals-redscan-foi/">ICO data breach reports late prior to GDPR: Redscan FOI</a> appeared first on <a href="https://internationalfinance.com">International Finance</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://internationalfinance.com/technology/ico-data-breach-reports-late-prior-gdpr-reveals-redscan-foi/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
