DataBreaches.Net

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

What They Didn’t Know: Big Brother Watch report on breaches highlights why we need mandatory disclosure

Posted on November 23, 2011 by Dissent

Mainstream media in the U.K. have picked up on a new report based on data obtained under freedom of information requests by Big Brother Watch (BBW).  The Guardian reports, ” Councils breached personal data 1,035 times over three years,” while BBC’s headline is “Personal data ‘lost by 132 councils,” and eWeek’s headline is  “132 Councils Named And Shamed For Data Loss.”

BBW  requested information from 433 local authorities  on the number of incidents and number of individuals affected.  The request covered a three-year timeframe of August 3, 2008 thru August 3, 2011. BBW received full or partial responses from 395  entities (91%).  The report appends results by council with descriptions of the incidents.

I think that one of the most significant findings was how few of the incidents were reported to the Information Commissioner’s Office.  BBW writes:

Of the 1030 incidents we uncovered, councils specified that in just 55 cases was an official notification to the ICO made. Such a low figure suggests that local authorities make different judgements on what should be reported and what does not need to be. Indeed, the fact that so many authorities reported no incidents – while other similar authorities reported several incidents –questions the threshold for reporting and logging of data incidents between authorities.

Extrapolating from what we have seen in this country, what the ICO learns about is clearly only the tip of the iceberg there.  I view the numbers in the BBW report as a significant underestimate of the number of breaches that actually occurred because not only are we not hearing from 9% of entities, but many authorities that did report probably did not detect or learn of all of the breaches they actually experienced. BBC notes, “For  example,  it  does  seem  surprising  that  in  263  local  authorities,  not  even  a  single  mobile   phone  or  memory  stick  was  lost.”   “Surprising” is a very diplomatic word.

Also of note, the wording of the request asked only about breaches where the data were in the custody of a council employee.  The request did not cover breaches where the data were in the custody of a contractor.  Contractors and vendors are involved in a significant minority of breaches and represent 19% of all breaches currently included in DataLossDB.

As more states here imposed mandatory notification and disclosure, we learned more.  The power to audit aside, the U.K. also needs a mandatory disclosure and notification law.  Without it, breaches will continue to be swept under rugs.  But we need not to penalize those who do disclose while others hide their breaches. One of the councils with the worst record, Telford & Wrekin, has responded to the report and illustrates the point about how naming and shaming reactions may discourage honest report and proactive councils.  The council said ” it encouraged staff to report data breaches so it could “learn from and not repeat” mistakes. ” And isn’t that exactly what we want?  Yet those who do may take a reputation hit that those who do not even respond will not suffer.

The BBW report should serve to inform the conversation in the U.K., and I commend them for their yeoman service.  Isn’t it a shame, however, that the government itself did not or could  request and demand these data?

Related posts:

  • Reports of data protection breaches doubled for Welsh councils last year — BBC
  • Health Data Breaches in 2017: The Year in Review
Category: Breach IncidentsCommentaries and AnalysesGovernment SectorNon-U.S.

Post navigation

← ManTech Awarded $7 Million Task Order to Provide Cyber Defense Support to the U.S. Air Force
MassBay employee database is compromised →

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

  • CMS warns Medicare providers of fraud scheme
  • Ex-student charged with wave of cyber attacks on Sydney uni
  • Detaining Hackers Before the Crime? Tamil Nadu’s Supreme Court Approves Preventive Custody for Cyber Offenders
  • Potential Cyberattack Scrambles Columbia University Computer Systems
  • 222,000 customer records allegedly from Manhattan Parking Group leaked
  • Breaches have consequences (sometimes) (1)
  • Kansas City Man Pleads Guilty for Hacking a Non-Profit
  • British national “IntelBroker” charged with causing $25 million in damages; U.S. seeks his extradition from France
  • France issues press statement about arrest of ShinyHunters members
  • Patients Allege Home Delivery Pharmacy Failed to Timely Notify Them of Data Breach

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

  • Justices nix Medicaid ‘right’ to choose doctor, defunding Planned Parenthood in South Carolina
  • European Commission publishes its plan to enable more effective law enforcement access to data
  • Sacred Secrets: The Biblical Case for Privacy and Data Protection
  • Microsoft’s Departing Privacy Chief Calls for Regulator Outreach
  • Nestle USA Settles Suit Over Job-Application Medical Questions
  • NY Attorney General James Affirms Hospitals Must Provide Access to Emergency Abortion Care
  • How Internet of Things devices affect your privacy – even when they’re not yours

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.