Quantcast StorefrontBacktalk » Blog Archive » Heartland Fearless: Sets Aside No Reserve For Breach
advertisement
advertisement

Heartland Fearless: Sets Aside No Reserve For Breach

Written by Evan Schuman
March 19th, 2009
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

Facing dozens of civil lawsuits and almost as many government probes because of a major data breach, Heartland remained Stoic with the SEC this week, telling the financial agency that it had decided to set aside zero funds as a contingency.

“While we have determined that the Processing System Intrusion has triggered a loss contingency, to date an unfavorable outcome is not believed by us to be probable on those claims that are pending or have been threatened against us, or that we consider to be probable of assertion against us, and we do not have sufficient information to reasonably estimate the loss we would incur in the event of an unfavorable outcome on,” Heartland reported. “As more information becomes available, if we should determine that an unfavorable outcome is probable on such a claim and that the amount of such unfavorable outcome is reasonably estimable, we will record a reserve for the claim in question any such claim.”

The Form 10-K also listed a wide range of agencies probing the breach, including quite a few whose Heartland probes had not been public. The list now includes the Federal Financial Institutions Examination Council, the Federal Trade Commission, the Louisiana Department of Justice Office of the Attorney General, the Canadian Privacy Commission and quite a few state Attorneys General.

Heartland also referenced Visa’s decision last week to remove Heartland from the PCI compliant list.

Heartland in the document confirmed the Visa move and added a critical piece of new information. Visa had said that Heartland was suspended until they could be recertified. Heartland’s SEC filing said that Visa intends to keep Heartland as “probationary” for two years after they’ve been recertified, during which time they would risk “our disconnection from VisaNet or our disqualification from the Visa payment system.”


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...