The InformationWeek -- Blogs
Welcome Guest. | Log In| Register | Membership Benefits

Security

Topics:   Security

  • Email this page E-mail this page
  • Print this page Print this page
  • Bookmark and Share
  • icon

Making Up For A Data Breach


Posted by Jennifer Bosavage, Feb 22, 2007 02:51 PM

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.

    « We Heart Google | Main | S.D. Police Department Adds Treos To Its Arsenal Of Crime-Fighting Weapons »



    Sign Up Now
    For InformationWeek News Alerts




    This is a public forum. United Business Media and its affiliates are not responsible for and do not control what is posted herein. United Business Media makes no warranties or guarantees concerning any advice dispensed by its staff members or readers.

    Community standards in this comment area do not permit hate language, excessive profanity, or other patently offensive language. Please be aware that all information posted to this comment area becomes the property of United Business Media LLC and may be edited and republished in print or electronic format as outlined in United Business Media's Terms of Service.

    Important Note: This comment area is NOT intended for commercial messages or solicitations of business.




     
     

    1. Think Parallel 2010, Five Years of Multicore
    2. It's All In the Strategy, It's All About the Design
    3. How To Do Parallelism Without Getting Egg On Your Face


    Join The InformationWeek Group On LinkedIn


    1. Verizon Wireless Details Android 2.1 Update For Droid
    2. Why Microsoft Is The New Apple
    3. Flop Or Not, Nexus One Headed To AT&T
    4. No Copy And Paste For Windows Phone 7


    1. Google Nexus One Coming To Sprint
    2. AMD Announces Opteron 6100 Partners
    3. Hospital Supply System Improving Bill Accuracy
    4. Cloud Connect: Grappling With Economics
    5. Google Builds Microsoft Exchange Escape Route
    6. Cisco Accelerates Borderless Networks

     

      Ars Technica
    Boing Boing
    Channel 9 Forums
    CRN Blogs
    Dr.Dobb's Portal: Blogs
    Engadget
    Gizmodo
    GrokLaw
      Lifehacker
    Schneier on Security
    Slashdot
    TechCrunch
    Techdirt
    Techmeme
    Valleywag

      DECEMBER 2008
    NOVEMBER 2008
    OCTOBER 2008
    SEPTEMBER 2008
    AUGUST 2008
    JULY 2008
    JUNE 2008
    MAY 2008
      APRIL 2008
    MARCH 2008
    FEBRUARY 2008
    JANUARY 2008
    DECEMBER 2007
    NOVEMBER 2007
    OCTOBER 2007
    SEPTEMBER 2007