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

3/9/2009
06:44 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Do Breach Notification Laws Work? Yes

Apparently a good number of consumers who receive letters notifying them that their financial or credit card information has been breached are tossing the notifications without taking action. Does this mean these notices are worthless?

Apparently a good number of consumers who receive letters notifying them that their financial or credit card information has been breached are tossing the notifications without taking action. Does this mean these notices are worthless?I don't think so. Kim Zetter at Wired's Threat Level blog penned an interesting post covering some of the discussions at the Security Breach Notification seminar, which was held in Berkeley, Calif., this past Friday.

From Zetter's post:

And though most states now have laws requiring companies to warn breach victims, some serious breaches are still showing up on customer credit and bank statements before any official warning has been issued. It all begs the question: are the notification laws working?

Zetter then accurately details benefits of transparency brought by these breach notifications.

However, it's with this point of view that was expressed at the conference that I take issue:

Breach notifications should, theoretically, reduce the number of incidents of identity theft or fraudulent charges to credit cards if consumers take proper precautions once they receive a notification -- such as placing a fraud alert or freeze on their credit account and monitoring their account bills and statements for suspicious transactions.

But in some cases, customers discover fraudulent charges on their cards or become victims of identity theft before a company is even aware its computers have been breached, making the breach notification redundant for those consumers.

Some other points include the issue that a portion, apparently the majority, of notice recipients actually ignore the notifications.

First, just because someone notices a fraudulent transaction on a financial statement, and then later gets a breach notification letter, that does not make that notification "redundant," as it's quite reasonable to expect that most credit card users will not know where a thief got their credit card data. Was it the restaurant I was at last week? The bookstore? Gas station? Or that online purchase?

You won't know for sure. But the breach notification would certainly give you a good idea.

Second, it's possible someone would use several different credit cards at the same online retailer over a period of months. Should this be the case, it would now be a good idea (following a notification) to change the credit card number for all of the cards used at that retailer over the affected period of time.

Third, it gives consumers the option to no longer shop at that merchant.

Helping consumers avoid identity theft and fraudulent transactions is only part of the benefit of data breach notification laws. The other is that it embarrasses companies to do the right thing and get the proper security controls in place. If they don't, the world may eventually know how little care they take with their customers' information. This in itself may have helped to improve the security at many organizations. Not make it perfect, but improve it.

And any consumer who ignores these notices does so at his own peril. And if people don't take any action, such as getting a fraud alert posted, that's their fault.

Before July 2003, when the California breach disclosure law went into effect, the big argument was whether or not there really were numerous serious data breaches occurring. "Where's the proof?" naysayers would ask.

Today, thanks to these laws, at least we have that proof and know what's going on. And wise consumers can take the simple action of changing the card number used at the breach company and placing a fraud alert on their profiles at the major reporting agencies.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Browsers to Enforce Shorter Certificate Life Spans: What Businesses Should Know
Kelly Sheridan, Staff Editor, Dark Reading,  7/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
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
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17366
PUBLISHED: 2020-08-05
An issue was discovered in NLnet Labs Routinator 0.1.0 through 0.7.1. It allows remote attackers to bypass intended access restrictions or to cause a denial of service on dependent routing systems by strategically withholding RPKI Route Origin Authorisation ".roa" files or X509 Certificate...
CVE-2020-9036
PUBLISHED: 2020-08-05
Jeedom through 4.0.38 allows XSS.
CVE-2020-15127
PUBLISHED: 2020-08-05
In Contour ( Ingress controller for Kubernetes) before version 1.7.0, a bad actor can shut down all instances of Envoy, essentially killing the entire ingress data plane. GET requests to /shutdown on port 8090 of the Envoy pod initiate Envoy's shutdown procedure. The shutdown procedure includes flip...
CVE-2020-15132
PUBLISHED: 2020-08-05
In Sulu before versions 1.6.35, 2.0.10, and 2.1.1, when the "Forget password" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a `400` error code is returned, along with a error message saying that th...
CVE-2020-7298
PUBLISHED: 2020-08-05
Unexpected behavior violation in McAfee Total Protection (MTP) prior to 16.0.R26 allows local users to turn off real time scanning via a specially crafted object making a specific function call.