Now Available:

line

Featured Resources:

line

Newsletter

Email Address:


line

Ask the Expert

Have a question for our resident expert? Email your questions to Rebecca.

« Whose PII Is Covered Under the EU Data Protection Directive? | Main | Social Engineering, Ethics, and Why You Should Never Put Anything Online That You Don't Want Others To See »

40+ Million Credit Cards Stolen Using Wardriving...This Is Nothing New, Folks!

Okay, lots and LOTS has already been written about the DoJ press release yesterday, "Retail Hacking Ring Charged for Stealing and Distributing Credit and Debit Card Numbers from Major U.S. Retailers: More Than 40 Million Credit and Debit Card Numbers Stolen."

But, I still want to put a few thoughts out about this...

First, how they stole the credit card numbers...OVER 40 MILLION...was by exploiting the lack of security in wireless networks.

"The Boston indictment alleges that during the course of the sophisticated conspiracy, Gonzalez and his co-conspirators obtained the credit and debit card numbers by "wardriving" and hacking into the wireless computer networks of major retailers -- including TJX Companies, BJ's Wholesale Club, OfficeMax, Boston Market, Barnes & Noble, Sports Authority, Forever 21 and DSW. Once inside the networks, they installed "sniffer" programs that would capture card numbers, as well as password and account information, as they moved through the retailers' credit and debit processing networks."

Come on, folks! This could have been prevented so easily! This type of hacking is nothing new.

And it's not like this is any type of new way to steal information. Ever since wireless has been used, it has been possible to steal the information from the wireless transmissions. Back in 2002 Best Buy made the news for having their credit card transactions stolen from their stores in basically the same way.

It would be interesting to see how many physical retail stores actually have effective security in place. Earlier this year I blogged about how many unsecured wireless access points my 8- and 11-year-old sons found just by driving to their day camps; see here and here.

Too little attention to security is given within physical stores and small to medium sized businesses (SMBs).

Second, too many business owners and business execs are willing to gamble that they will not be targetted, so they choose to not invest in security.

Since the mid-1990's I've heard CxOs, and SMBs, often use the argument, "How likely is it for something to happen if we don't install the you want us to invest in? If it's not that likely, then why waste the money?"

Use this wireless hacking case, which stole OVER 40 MILLION CREDIT CARD NUMBERS, as an example of how easy it is for the bad guys to commit crime when security...basic, simply implemented security...is not put into place. The execs whose card numbers were taken should now understand the need for security better...you would think.

Third, this also shows that, while the PCI DSS is good for contractually trying to ensure security is addressed, and places responsibility for implementing security upon the businesses processing credit card payments, PCI DSS, in and of itself, is not a panacea.

Too many execs say, "We're following PCI DSS. We're secure; we're invulnerable."

PCI DSS is a security standard. It is not the *actual practice* of security that is required within all businesses. This case demonstrates this.

PCI DSS is a good set of general rules for organizations to follow, but it does not address the day-to-day execution of security within all locations where credit cards are processed. Just because an organization is certified as being PCI DSS at one point in time does not mean that security is addressed and being actively enforced by all personnel on an ongoing basis. More reason why training and ongoing awareness must be provided.

All these merchants were supposed to have been PCI DSS compliant. However, apparently 100's, if not 1000's, of the retail locations either...

1) simply did not understand security enough to know that wireless transmissions of payments must be strongly encrypted, or (probably more likely),

2) chose not to spend the time and comparatively low dollar investment to actually implement the security controls with the belief that it wasn't likely that bad things would happen, or

3) stopped addressing security once they got their PCI DSS seal of approval.

TrackBack

TrackBack URL for this entry:
http://www.realtime-itcompliance.com/type/mt-tb.cgi/780

Comments

Okay, so that is totally terrifying! I can't believe it's still easy to steal cc numbers.

It's getting to the point where it's really frightening to give out personal information, or to even use the credit card. You just never know what can happen once the information is transmitted into cyberspace, right?

Post a comment

(All comments are approved by site leader before appearing here. Thanks for commenting!)

line

Rebecca Herold's Bio:

Rebecca Herold,CISSP, CIPP, CISM, CISA, FLMI, has been providing information security, privacy and regulatory assistance and services to organizations from a wide range of industries for over 18 years. Rebecca was instrumental in building the information security and privacy program while at Principal Financial Group, which was awarded the CSI Information Security Program of the Year Award in 1998. IT Security ranked Rebecca as one of the top 59 IT security influencers, and Computerworld put Rebecca their list of the 25 top privacy experts and on their list of the 9 best privacy consulting firms. Rebecca has been CPO for two consulting organizations, and has had her own information privacy, security and compliance business since 2004. Rebecca has written chapters for several books, dozens of articles, and has been writing a monthly privacy column for the CSI Alert newsletter since the beginning of 2001, and is working on her 11th book. Some of her other books include The Privacy Papers, Managing an Information Security and Privacy Awareness and Training Program, The Definitive Guide to Security Inside the Perimeter (Realtime Publishers), The Shortcut Guide to Improving IT Service Support through ITIL (Realtime Publishers), and The Practical Guide to HIPAA Privacy and Security Compliance. In addition, Rebecca is the leader of The Realtime IT Compliance Community where she posts to her IT Compliance weblog. You can contact Rebecca at: rebecca_herold@realtimepublishers.net.