Risk
2/22/2007
02:51 PM
50%
50%

Making Up For A Data Breach

Do companies really care about the security of their customers' data? Quite frankly, not as much as they should, based on what's in the news.

Do companies really care about the security of their customers' data? Quite frankly, not as much as they should, based on what's in the news.Lately, it seems, we've been hearing about all types of data breaches: retailer TJX, the state of Connecticut, Stop & Shop, and the Department of Veterans Affairs. It's an epidemic, but don't turn to Johns Hopkins; an outside contractor to that health facility lost nine backup tapes that held sensitive personal information on 52,000 workers and 83,000 patients. The data is "thought" to have been destroyed. That's not really very comforting if you are one of those 135,000 people. And that's a pretty big number.

One big problem is that executives give data protection a lot of lip service these days. But if you think about it, what choice do companies have? Shareholders aren't going to be really happy with "Part of our cost-cutting measures includes neglecting our customer data." In fact, these companies probably invested quite a bit in some type of business intelligence product. Data mining is all the rage, and for good reason. There are plenty of lucrative marketing opportunities out there, if you can make sense out of all that data collected. Identifying repeat customers, buying trends, and other information that can better your business justifies collecting some types of data in the first place.

But some of what's collected seems odd: For example, TJX stored the license numbers of people who returned items without a receipt. Now, what is done with that information? How often does a retailer track someone down using the driver's license number? Seems to me companies could simply refuse to take a return without a receipt (like Toys "R" Us has recently done). The point is, how much information is necessary, and how much is overkill? Companies are opening themselves to more exposure by collecting too much information. It's all the more to worry about if there's a breach.

So, here are my Common Sense Rules.

  • First, companies ought to only hang on to information that is absolutely necessary. That way, if it's stolen (TJX), lost (Johns Hopkins), or otherwise compromised (Stop & Shop), there's less to worry about, plain and simple.

  • Second, companies should have possession of that data for only a specified period of time -- something that is currently mandated for credit card information but apparently was ignored by some of the parties involved.
  • Finally, there should be a Customer's Bill of Rights regarding what happens if your data goes astray. The JetBlue debacle of last week in which airline passengers were stranded on the tarmac for hours -- and the resultant Passenger Bill of Rights -- could act as a model for this. If companies must make reparations for lax data security, it's more likely that they will pay attention to keeping it locked up to begin with.
  • Massachusetts is taking note: A bill in the Legislature would make businesses pay for poor data security. Companies would be mandated to pay to cancel or reissue cards, stop payments, or block transactions. That may be too complicated; all that might be needed is a financial penalty, payable to the victim. For example, $100 would be payable to the person whose data has been breached. It's then up to that person if he or she even wants the credit card reissued. This system is straightforward and can be easily calculated. But whatever remedy is chosen, the time has come for some "incentive" to be invoked.

    Comment  | 
    Print  | 
    More Insights
    Register for Dark Reading Newsletters
    White Papers
    Cartoon
    Current Issue
    Flash Poll
    Video
    Slideshows
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2014-8617
    Published: 2015-03-04
    Cross-site scripting (XSS) vulnerability in the Web Action Quarantine Release feature in the WebGUI in Fortinet FortiMail before 4.3.9, 5.0.x before 5.0.8, 5.1.x before 5.1.5, and 5.2.x before 5.2.3 allows remote attackers to inject arbitrary web script or HTML via the release parameter to module/re...

    CVE-2015-0891
    Published: 2015-03-04
    Cross-site scripting (XSS) vulnerability in Maroyaka CGI Maroyaka Simple Board allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

    CVE-2015-0892
    Published: 2015-03-04
    Cross-site scripting (XSS) vulnerability in Maroyaka CGI Maroyaka Image Album allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

    CVE-2015-0893
    Published: 2015-03-04
    Cross-site scripting (XSS) vulnerability in Maroyaka CGI Maroyaka Relay Novel allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

    CVE-2015-2209
    Published: 2015-03-04
    DLGuard 4.5 allows remote attackers to obtain the installation path via the c parameter to index.php.

    Dark Reading Radio
    Archived Dark Reading Radio
    How can security professionals better engage with their peers, both in person and online? In this Dark Reading Radio show, we will talk to leaders at some of the security industry’s professional organizations about how security pros can get more involved – with their colleagues in the same industry, with their peers in other industries, and with the IT security community as a whole.