This is page 2 of:

Did Retailers Learn Any Lessons From Gonzalez?

April 29th, 2010

Had the group, for example, chosen to use codewords instead of the retailers’ names, it would have had to share those codewords amongst its members. In that case, the codewords would have been irrelevant. The confiscated laptops and passwords would likely have revealed the codewords, making their use silly. It would be like encrypted data that is captured together with the encryption key: The encryption won’t do much good.

Had the operation been much smaller—with just a couple of people and much less lofty goals in the number of payment card numbers to be stolen—it might have fared better, from a “not getting caught” perspective. But with the anti-fraud systems in place today at Visa and other brands, cyberthieves really need to grab huge quantities of card numbers to have enough survive to make a profit.

The trick, Peretti suggests, is to take few enough card numbers from any one victim to not make it worth the efforts of a major law enforcement agency. The Gonzalez investigations took a lot of Secret Service hours—along with untold time by at least three U.S. Attorney Offices, the Justice Department and quite a few overseas law enforcement groups.

If the number of card numbers stolen was much lower, it’s unlikely anyone could have justified spending so much time chasing the thieves. To quote the title character from Butch Cassidy and the Sundance Kid, that law enforcement effort “has got to cost him more than we ever took. If he’d just pay me what he’s spending to make me stop robbing him, I’d stop robbing him.”

But what could retailers have done to prevent Gonzalez’s crew from penetrating their systems? The SQL Injection attacks used were well known, and those holes could have been plugged. The bigger issue, though, was the lack of thorough event log monitoring.

Is that situation better or worse today? Frustratingly, it’s probably both. The problem has always been that this type of monitoring is hard for some retail IT folk to justify when profit-oriented projects—such as getting new site functionality in place before the holidays hit—are backlogged. Do you start cutting back the time spent reviewing logs?

On the plus side, the Gonzalez attacks have given retailers a strict reminder of why such logs needs to be carefully examined every day, no matter what.

On the down side, part of what amazed prosecutors in this case was how the thieves could divert so much data out of a system without it being noticed. That particular problem is getting even more complicated by the soaring number of outsourced services that are constantly grabbing data off of retail servers.

The plethora of data departures include updated information leaving to fuel mobile sites and services that handle customer comments, product shipments and purchases being processed locally on social sites. One side effect of all of those communications is that improper data transfers are obscured. Administrators have chased down so many such data exchanges and learned of yet another partner altering its procedures that a clever piece of malware could easily escape detection, if it doesn’t get too greedy.

Peretti fears, though, that the next generation of Gonzalezes will likely target smaller and midsize retailers, which ostensibly have less stringent security and probably watch their event logs even less often than their larger competitors. Still, with less going on, even a small errant data transmission might stand out more at a smaller merchant.


Comments are closed.


StorefrontBacktalk delivers the latest retail technology news & analysis. Join more than 17,000 retail IT leaders who subscribe to our free weekly email. Sign up today!
Our apologies. Due to legal and security copyright issues, we can't facilitate the printing of Premium Content. If you absolutely need a hard copy, please contact customer service.