Hundreds Of Servers Compromised In Hannaford BreachHundreds Of Servers Compromised In Hannaford Breach
More details about the credit breach at the Hannaford grocery chain are becoming known, and they aren't pretty.
March 28, 2008
More details about the credit breach at the Hannaford grocery chain are becoming known, and they aren't pretty.The Boston Globe reports that malware was installed on servers at every store in the Hannaford chain -- approximately 300 locations.
The details of the breach come from a letter sent by Hannaford's general counsel to authorities in Massachusetts.
According to the letter, the malware intercepted the credit card number and expiration date at the point of sale as it was being sent for authorization. The malware then sent batches of card numbers over the Internet to a foreign ISP.
The article calls the attack "new and sophisticated," but was it really? I'll grant that compromising hundreds of servers and then sniffing the point-of-sale traffic to gather the account data is pretty slick.
But it also seems to me that Hannaford's security processes failed in several areas where security processes just shouldn't these days.
First is the sheer number of servers compromised. There aren't any details in the Globe article about how the malware got onto the servers. If it was a remote intrusion, did the attackers exploit a known vulnerability? If so, how did Hannaford's vulnerability scanners miss it? The scale of the attack prompted some security professionals quoted in the article to speculate that it might have been an inside job.
And how about the malware? Perhaps this was a custom-written package, and so evaded anti-malware detection. But then there's fact that internal servers were transmitting outside the network to strange IPs. This should've raised flags somewhere -- server logs, IDS logs, firewall logs.
I realize it's easy to say the barn door should've been closed after the cow gets out, but server hardening and log review and analysis are Security 101.
PCI And The Law As if the breach weren't enough fun, Hannaford has to deal with two class-action lawsuits, including a suit filed by Berger & Montague, a firm that was also involved in a class action suit against TJX -- which TJX settled.
The suit alleges that Hannaford was "negligent for failing to maintain adequate computer data security of customer credit and debit card data."
Here's where things get interesting. Hannaford says it was certified PCI compliant in February 2008. If Hannaford is following industry best practices, that will make it harder, though not impossible, for the plaintiff to prove its case. (In fact, the lawyers don't really have to prove anything as they are probably gunning for a settlement. Given that every store in the chain was compromised and as many as 4.2 million card numbers could have been exposed, I'd wager they'll get it.)
Even more interesting is Hannaford's compliance status. The company says it was certified compliant a year ago, and was recertified compliant on Feb. 27 -- at the same time the breach was ongoing.
If Hannaford is a Level 1 merchant, that means a third-party assessor had to certify Hannaford as compliant. If this assessor certified Hannaford compliant while a breach was ongoing, does the assessor share any liability? You can bet the folks at Berger & Montague, and Hannaford's in-house lawyers, will be asking that question.
If Hannaford is Level 2 or 3, certification means filling out a self-assessment questionnaire and undergoing quarterly vulnerability scans. Maybe Hannaford's scanning vendor could get dragged in here.
We'll have to watch how these cases proceed. In any case, the whole mess should be very instructional to retailers everywhere.
About the Author(s)
You May Also Like
Hacking Your Digital Identity: How Cybercriminals Can and Will Get Around Your Authentication MethodsOct 26, 2023
Modern Supply Chain Security: Integrated, Interconnected, and Context-DrivenNov 06, 2023
How to Combat the Latest Cloud Security ThreatsNov 06, 2023
Reducing Cyber Risk in Enterprise Email Systems: It's Not Just Spam and PhishingNov 01, 2023
SecOps & DevSecOps in the CloudNov 06, 2023