Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

1/4/2008
03:00 PM
Tom LaSusa
Tom LaSusa
Commentary
50%
50%

Let's Raise The Stakes For Data Loss Culpability

After a year of unbelievable (and in some cases incomprehensible) data loss among corporations both big and small, I propose we adopt a brand-new catchphrase for 2008. To borrow somewhat from culinary personality Emeril Lagasse: It's time to kick the penalties up a notch.

After a year of unbelievable (and in some cases incomprehensible) data loss among corporations both big and small, I propose we adopt a brand-new catchphrase for 2008. To borrow somewhat from culinary personality Emeril Lagasse: It's time to kick the penalties up a notch.Think about it -- what's a few million dollars in fines to a multibillion dollar company? We're talking a pittance here. What if instead, for every lost record, the business was charged a standardized fee? A recent study by the Ponemon Institute determined that every single lost, stolen, or compromised customer record costs about $200. Now let's see -- T.J. Maxx "misplaced" about 45 million customer records. Hmmm.

OK, OK, I'm not really suggesting they pony up a ridiculous, Doctor Evil-esque amount of $9,000,000,000. But how about $50 per record for Fortune 500 companies, with a lesser fine for companies in a smaller tax bracket? Depending on the total number of records lost, the fine wouldn't be enough to cause the business to collapse but would definitely hurt -- enough that security practices would start to be considered more than just an add-on or afterthought.

What about accountability? Shouldn't someone's head be on the chopping block for these transgressions? Sure, the guy who left his laptop unattended while he hit the airport bathroom will probably lose his job. The guy that sneaked in after hours and intentionally stole the data will get prosecuted. But what about the CEO or the CSO? Shouldn't they be taken to task for failed security measures or lack of policies? Shouldn't one of them be handed a pink slip? Or maybe a little time in prison would make these folks think twice before being so lax with customer data. I'm being too harsh, you say? Some things are just beyond our control? Perhaps you've never heard of gross negligence or breach of duty? Our courtrooms are full of cases where one party's conduct failed to uphold "the legal standard required of a reasonable person in protecting individuals against foreseeably risky, harmful acts of other members of society."

Simple Scenario: If the guy who runs the local deli fails to repair a broken sidewalk, he's held liable by the courts if someone is injured. The owner had a reasonable opportunity to correct the situation and chose not to. The injured party, on the other hand, is not responsible to know that there was a hazard. How is that any different than when a company fails to update its security policies (or neglects to implement any), resulting in the "injury" to thousands, if not millions, of customers' identities? Bottom line, companies are getting off light when it comes to being held accountable for data loss. It's time to take everyone responsible for these incidents to task. Higher penalties, loss of jobs, maybe even the threat of a little white-collar prison time might prompt the management to start caring a little more about the little guy.

What do you think -- do data loss punishments and fines fit the crimes? Or should we be hitting these companies -- and their officers -- harder ... a lot harder?

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26120
PUBLISHED: 2020-09-27
XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even witho...
CVE-2020-26121
PUBLISHED: 2020-09-27
An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an uploa...
CVE-2020-25812
PUBLISHED: 2020-09-27
An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML.
CVE-2020-25813
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users.
CVE-2020-25814
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> ...