Quantcast StorefrontBacktalk » Blog Archive » Secret Service Investigating Debit-Only Breach Of An Alabama Dairy Queen
advertisement
advertisement

Secret Service Investigating Debit-Only Breach Of An Alabama Dairy Queen

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

For the mysterious data breach crime folder, the U.S. Secret Service is investigating a series of payment card thefts—originating at an Alabama Dairy Queen—that has only been impacting debit cards. The Hanceville, Ga., police department’s Capt. Jimmy Rodgers is quoted in a local newspaper saying: “At that location, somebody has apparently tapped into the Internet server and hacked into the debit card system, and they’re printing out the customers’ debit card numbers and using them all over California and Georgia.”

This is a disturbing trend, as retailers see debit card approaches as a way to try and reduce interchange costs. It’s even more frightening when we factor in that debit cards are more likely to suffer a processing glitch—as Best Buy and Macy’s discovered last year–than credit cards and that consumers impacted by a debit card data breach are far more exposed than they would have been had they used a credit card.


advertisement

One Comment | Read Secret Service Investigating Debit-Only Breach Of An Alabama Dairy Queen

  1. Walt Conway Says:

    More than just suffering losses, the knock-on effect of these debit card breaches could be consumers finally having standing to sue a breached merchant. Enter the lawyers. At some point, I fear this could lead to a successful consumer class action against a retailer for a data breach. Compared to such a “doomsday scenario,” any PCI fines will seem like a pinprick.

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