Australian Credit Breach Culprit: Google Cache
Written by Evan SchumanMarch 25th, 2009
The ability of Google's cache capture to memorialize anything found on a Web site—including credit card information—is hardly new, but some Australian IT execs have been given a concrete reminder, as they found that data from some 19,000 credit cards—including including CVVs, expiration dates, names and addresses—in a routine Google search.
This incident was limited and the damage seems to be minimal. But the bigger issue is why has this hole not been adequately plugged by now? Was this sloppy work done by the online equivalents of the guys that dump credit card files in front of the store when a location is shut down? Or is this problem hitting those who are otherwise security sensitive?
This Story Is Only Available For Premium Subscribers. Click Or Login In Below To Read The Rest Of This Story.
Already a Subscriber? Login Here
Leave a Reply
Readers, specifically those who want to comment on a story:
Our Comment SPAM system is getting very aggressive these days and has been blocking legitimate comments. If you post a comment and don't see it appear within 2 hours or so, can you please send a heads-up to customer-service@storefrontbacktalk? Ideally, please include the time you posted the comment. That will allow us to try and hunt for it. Thanks! P.S. We're working on fixing the system, but we don't want to lose any valuable comments in the meantime.
Our Comment SPAM system is getting very aggressive these days and has been blocking legitimate comments. If you post a comment and don't see it appear within 2 hours or so, can you please send a heads-up to customer-service@storefrontbacktalk? Ideally, please include the time you posted the comment. That will allow us to try and hunt for it. Thanks! P.S. We're working on fixing the system, but we don't want to lose any valuable comments in the meantime.
Is there really an improvement between a mag swipe and contactless tap if multi-factor authentication is required?
-Ed
