Quantcast StorefrontBacktalk » Blog Archive » Some Banks Try Again For Class-Action Heartland Lawsuit
advertisement
advertisement

Some Banks Try Again For Class-Action Heartland Lawsuit

Written by Evan Schuman
January 21st, 2010
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

Shortly after Heartland tried to sweep away most of the lawsuits against it with a series of recent negotiated settlements, a group of banks is trying to persuade other banks to reject the settlement offer and support a class-action lawsuit instead.

The lawsuit, filed Tuesday (Jan. 19), hit Heartland hard for its “lack of Payment Card processing system security; its desire to use a ‘lowest bidder’ system of selecting its outsourced IT ‘auditors’; its reliance on a ’snapshot’ telling it that, at one identifiable point in time, its system supposedly complied with the bare minimum industry standards; its startlingly poor IT oversight in general; and (Heartland’s) complete and utter disregard of the oversight responsibilities they had to their fellow members of the Associations that allowed the intruders to make trip after trip in and out of the Heartland Payment Card processing system.”

The lawsuit also referenced Heartland’s initial response to the attack. “Thirteen months later, the ‘clean up’ efforts would be
seen for what they were—worthless.” (Pause. But other than that, Mrs. Lincoln, how was the play?)

Lawyers behind the new class-action attempt are painting the settlement as inadequate and implying that it lets Heartland and some Heartland partners off too easily. “There were more than 86 million Visa payment cards compromised by the data breach,” said Attorney Mike Caddell. “Once a financial institution factors in the costs it incurred to cancel and reissue the payment cards and the unauthorized charges it was forced to absorb, its share of the settlement most likely will be pennies on the dollar.”

But the attorneys saved some of their most direct comments for Heartland’s bank partners. “Perhaps the most egregious aspect of the proposed settlement is that Heartland’s acquiring banks—KeyBank and Heartland Bank—which also are potentially liable for the data breach damages, will receive a complete release of any liability even though they are contributing little, if anything, to the settlement,” said Interim Co-lead Counsel Richard Coffman. “The majority of the settlement funds are provided by Heartland, which is downplaying its ability to pay any more money. Yet, KeyBank has $97 billion of assets and Heartland Bank has over $1 billion of assets, which suggests that there are additional sources of money to compensate the issuers for their damages.”

Coffman pushed this point a bit further and started to question Visa’s agenda.


advertisement

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

Kill All The Passwords

This article does mention, but does not give enough attention to, the fact that the attacks discussed are only feasible when the encrypted password file can be copied and subjected to an offline attack. The trick is to have authentication performed on a separate, much more strongly secured host - such as an Active Directory Domain Controller, or a Kerberos server, or a NIS+ server, or even using something as banal as an LDAP-over-SSL authentication dialog. In these environments, the odds of the "password file" being stolen and subjected to an offline attack go to near zero, and only online attacks may be carried out by the attacker. With sensible exponential backoff between failed password attempts, lockout after a modest number of failed attempts on a single account, and pattern detection, that minimum 7 character password is quite secure enough. Passwords aren't dead yet for security purposes, and they will be with us for a very long while to come for practical purposes. The trick is to employ them correctly. Read more...
The possibilities you describe are years away from being implemented at best, so for the moment passwords are an ugly reality. Luckily, password managers can easily manage hundreds of passwords of any length. The only thing a user needs to remember is the master password. It seems like an easier task to educate users on how to use password managers rather than implement complex security technology on a global basis. Read more...