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

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.

     

    Recommended Reading:

    Comment  | 
    Print  | 
    More Insights
    Comments
    Newest First  |  Oldest First  |  Threaded View
    COVID-19: Latest Security News & Commentary
    Dark Reading Staff 7/2/2020
    Ripple20 Threatens Increasingly Connected Medical Devices
    Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
    DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
    Dark Reading Staff 6/30/2020
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon
    Current Issue
    How Cybersecurity Incident Response Programs Work (and Why Some Don't)
    This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
    Flash Poll
    The Threat from the Internetand What Your Organization Can Do About It
    The Threat from the Internetand What Your Organization Can Do About It
    This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2020-9498
    PUBLISHED: 2020-07-02
    Apache Guacamole 1.1.0 and older may mishandle pointers involved inprocessing data received via RDP static virtual channels. If a userconnects to a malicious or compromised RDP server, a series ofspecially-crafted PDUs could result in memory corruption, possiblyallowing arbitrary code to be executed...
    CVE-2020-3282
    PUBLISHED: 2020-07-02
    A vulnerability in the web-based management interface of Cisco Unified Communications Manager, Cisco Unified Communications Manager Session Management Edition, Cisco Unified Communications Manager IM & Presence Service, and Cisco Unity Connection could allow an unauthenticated, remote attack...
    CVE-2020-5909
    PUBLISHED: 2020-07-02
    In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, when users run the command displayed in NGINX Controller user interface (UI) to fetch the agent installer, the server TLS certificate is not verified.
    CVE-2020-5910
    PUBLISHED: 2020-07-02
    In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the Neural Autonomic Transport System (NATS) messaging services in use by the NGINX Controller do not require any form of authentication, so any successful connection would be authorized.
    CVE-2020-5911
    PUBLISHED: 2020-07-02
    In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the NGINX Controller installer starts the download of Kubernetes packages from an HTTP URL On Debian/Ubuntu system.