Quantcast StorefrontBacktalk » Blog Archive » Tesco IT Glitch Shuts Down POS, Spares Self-Checkout
advertisement
advertisement

Tesco IT Glitch Shuts Down POS, Spares Self-Checkout

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

The 4,308-store Tesco grocery chain, one of Europe’s largest retailers and the largest in the U.K., suffered some sort of a systems glitch during “an IT update overnight” that shut down POS systems for about 100 stores on Monday (May 11), but spared all self-checkout stations, Tesco officials said. Given that a retail self-checkout system typically runs its own application separate from the POS app, said IHL President Greg Buzek, this suggests the problem was internal to the POS software, not the payment application or database.

“Tesco said that all types of payments, including credit and debit cards and cash via normal tills, had been affected. However, self-service systems in affected stores and in Tesco garages had not been affected,” reported ZDNet. “An investigation into the cause of the outage will be launched shortly, the spokesperson said, noting that the problem was probably caused by software updates that had been sent out on Sunday night. The issues were unlikely to have been caused by a hacking attack, the spokesperson added.”


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