Commentary

Patricia Keefe
 

It's Smackdown Time On Data Breaches

Is the tide beginning to turn on data security breaches? If so, IT can expect to be at the forefront of catching the brunt of any backlash, at least internally, if not externally.

Is the tide beginning to turn on data security breaches? If so, IT can expect to be at the forefront of catching the brunt of any backlash, at least internally, if not externally.Consider the case of TJX Companies Inc.'s "incident," as the company is fond of calling it, announced Jan. 17. Up until now, consumer outrage and legislative posturing aside, the fallout from security breaches involving identity theft or the loss of customer and employees' personal data has been minimal. A few days of bad press, a year of credit monitoring, a budget spike as security is bolstered, some cranky customers, and maybe, just maybe, a fine from Visa and MasterCard. But that was pretty much it, except for two high-profile explosions of market frustrations, which culminated in the public pillorying of the Veterans Administration and data aggregator ChoicePoint (who was also the recipient of the FTC's largest fine ever - $15 million.)

All in all, nothing to lose sleep over.


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

But this most recent publicized data theft is different. It's different in terms of the scope, the criminal investigation, and most important, the reactions from the public, partner, and political spheres. And none of this bodes well for future targets of data breaches.

From a business standpoint:

Consumer trust has been deeply violated on at least five levels:

  • That security was inadequate in the first place.
  • That the data appears not to have been encrypted (TJX's silence speaks volumes here).
  • That the company kept parts of the transaction data for far longer than it was supposed to. (More TJX silence.)
  • That the company remained silent about the breach for a month.
  • That the company's response has amounted to little more than a meaningless apology buttressed by happy sounds about the new security now in place, a refusal to monitor credit reports, and consumer tips that add up to, "You're on your own, kids."
  • Business-to-business frustrations have boiled over:

  • The credit card companies are assessing fines for noncompliance with PCI, or the Payment Card Industry Data Security Standard. This could lead to trouble with TJX's bankers since they face fines if their merchants are not in compliance with PCI. Meanwhile, those merchants not in compliance are not supposed to be able to process Visa or MasterCard payments.
  • AmeriFirst Bank has filed a class-action lawsuit charging TJX and it's card-processing bank, Fifth Third bank, with negligence and breach of contract. It expects other financial institutions will join the suit.
  • Hundreds, maybe thousands, of banks are talking about seeking restitution as consumers nationwide have canceled debit and credit cards in the wake of this breach -- including yours truly. (Why take the chance? When I called my credit card issuer, I was told that they had received "many, many" calls seeking new cards.)
  • TJX's stock has taken a hit -- slowly, but surely.
  • Government agencies are starting to stir:

    Some sectors of the government appear ready to drop the hammer, with calls for the FTC to investigate, and a committee to be formed to write a data protection standard.

    And at the company itself? It has paid IBM and General Dynamics to come in and audit, bolster, and monitor its defenses, shelled out money to run full-page newspaper ads in a bid to repair it's badly tarnished reputation, put together a Webcast and other data and tips on its Web site, and most likely, assembled an army of lawyers on monster retainers.

    Which it will need, given that one class-action lawsuit has been filed, and more could be on the way from consumers, banks, perhaps credit card issuers, and maybe even the feds and various consumer protection arms of state AG offices.

    In short, it's going to take a lot of time, money, technology, public humiliation and, heaven knows, a lot better PR, before TJX can wriggle out of this one.

    This brings me back to my initial point -- that the tide is turning on public reaction to data breaches. So consider the TJX "incident" to be a screaming wake-up call for IT and the businesses they serve: The world will no longer look the other way.

    Hopefully, this will scare some businesses straight. If you are in IT, don't wait for the business side to come to its senses.

    You need to find out what your customer data consists of, what your business counterparts are doing with it, what it's expiration date is, in what form it is stored, where it is stored, and who has access -- any access -- to it, and where they are.

    You need to check and recheck your defenses and think long and hard about how up to snuff they are. You need to check your agreements with third-party processors, bankers, and credit card issuers. Are you all on the same page, are you following policy to the letter? Are you each doing your part?

    You need to make sure your transaction processing software isn't retaining or collecting data it shouldn't be.

    You need to have a disaster readiness plan worked out with the business side in case something happens. It needs to cover all aspects of a disaster -- investigation, recovery, consumer aid, publicity, and legal issues.

    You need to do a cost assessment. What is the cost of taking these steps, (and documenting them) versus the cost of cleaning up the aftermath of a data breach? At least, then, if the business chooses to stick its head in the sand, you'll be covered.

    And you'll want to be. Because if IT and businesses do not work together to do these things, new laws are going to be written, fines are going to be assessed, heads will roll, careers will be dead-ended, business relationships will be severed, customers will be lost, stocks will drop and some people may even go to jail.


    Related Reading




    Currently we allow the following HTML tags in comments:

    Single tags

    These tags can be used alone and don't need an ending tag.

    <br> Defines a single line break

    <hr> Defines a horizontal line

    Matching tags

    These require an ending tag - e.g. <i>italic text</i>

    <a> Defines an anchor

    <b> Defines bold text

    <big> Defines big text

    <blockquote> Defines a long quotation

    <caption> Defines a table caption

    <cite> Defines a citation

    <code> Defines computer code text

    <em> Defines emphasized text

    <fieldset> Defines a border around elements in a form

    <h1> This is heading 1

    <h2> This is heading 2

    <h3> This is heading 3

    <h4> This is heading 4

    <h5> This is heading 5

    <h6> This is heading 6

    <i> Defines italic text

    <p> Defines a paragraph

    <pre> Defines preformatted text

    <q> Defines a short quotation

    <samp> Defines sample computer code text

    <small> Defines small text

    <span> Defines a section in a document

    <s> Defines strikethrough text

    <strike> Defines strikethrough text

    <strong> Defines strong text

    <sub> Defines subscripted text

    <sup> Defines superscripted text

    <u> Defines underlined text

    InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

    Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
    T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
    Subscribe to RSS

    Resource Links