DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

DPA fines – why ICO got it right

Posted on November 25, 2010 by Dissent

Stewart Room writes about the first fines imposed by the U.K.’s Information Commissioner’s Office:

I’ve heard two arguments that are critical of the ICO fines. They go something like this: (1) the fines were too low and (2) it’s wrong of ICO to fine a Local Authority when it didn’t fine Google. Let me try to explain why these arguments are misconceived and why I believe that ICO got it right.

Regarding the level of the fines, the point to remember is that Parliament has determined that ICO must operate within a capped regime of fines, of up to £500,000. The top bracket must therefore be preserved for the worst offenders. Clearly, Herts and A4e behaved badly, but ICO will see much worse and they know it. If ICO had fined at the top of the cap, their decisions would have been vulnerable to legal challenge. ICO has limited ammunition and they need to preserve bullets for future cases.

Read more on Stewart Room.

Robin Wilton of Gartner also blogs about the recent fines.

I agree with Stewart Room that the ICO got it right.  What I especially liked about the selection of the local council is that the fine serves as a powerful warning that it doesn’t have to be a large breach to result in a fine.  A serious breach involving the data of only person can result in heavy penalties if an entity was negligent and very sensitive data are exposed as a result.  And taking n=1 breaches seriously has been a recurring theme on this blog and the mothership, PogoWasRight.org.

Category: Breach IncidentsCommentaries and AnalysesGovernment SectorNon-U.S.

Post navigation

← Former Sprint-Nextel employee sentenced for improper disclosure of phone records to cocaine dealer
NHS Choices criticised for leaking information to Facebook →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • CoinMarketCap Hacked, Scrambles to Remove Malicious Wallet Verification Popup
  • Montana Attorney General launches investigation into Lee Enterprises data breach
  • AT&T gets preliminary approval for $177 million data breach settlement
  • Aflac notifies SEC of breach suspected to be work of Scattered Spider
  • Former JBLM soldier pleads guilty to attempting to share military secrets with China
  • No, the 16 billion credentials leak is not a new data breach — a wake-up call about fake news (Updated)
  • Tonga’s health system hit by cyberattack (1)
  • Russia Expert Falls Prey to Elite Hackers Disguised as US Officials
  • Proposed class action settlement in In re Netgain Technology litigation
  • Qilin Offers “Call a lawyer” Button For Affiliates Attempting To Extort Ransoms From Victims Who Won’t Pay

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • The Markup caught 4 more states sharing personal health data with Big Tech
  • Privacy in the Big Sky State: Montana’s Consumer Privacy Law Gets Amended
  • UK Passes Data Use and Access Regulation Bill
  • Officials defend Liberal bill that would force hospitals, banks, hotels to hand over data
  • US Judge Invalidates Biden Rule Protecting Privacy for Abortions
  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities
  • 23andMe fined £2.31 million for failing to protect UK users’ genetic data

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.
Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report