Re:IAmA a malware coder and botnet operator, AMA
by smackfu on Friday May 11, 2012 @03:28PM
(#3960902)
The point is that even if someone steals your order database with credit card numbers and expiration dates, they need to try every number 1000 times. That's a decent speedbump.
If you store CVV2 in your database against your merchant agreement, and someone steals it, I'm sure the credit card comp will come after you for the losses.
Re:IAmA a malware coder and botnet operator, AMA
by bediger4000 on Friday May 11, 2012 @04:12PM
(#3961142)
If you're a "Carder", and you've got 1,000 cards, you just try them once a day. You'll get 2 CVV2's a day, average. And a bet that a once-a-day wrong CVV2 doesn't trip very many, if any, fraud checks. How much more is a card worth to a carder with CVV2/CVC than one without? Another niche service to provide in the cybercriminal underground, I guess.
As far as being non-PCI compliant, you as a merchant are only compliant right at the time of the audit. And maybe not even then, given Heartland's experience. The whole PCI thing is to give Visa and MasterCard a way to do some CYA.
Not only will they be sued, but they'll no longer be able to accept credit cards. They'll most likely go out of business. It's a serious matter to be non-PCI compliant.
Re:IAmA a malware coder and botnet operator, AMA
by dangrossman on Friday May 11, 2012 @03:26PM
(#3960890)
> Someone who really wanted to could get a CVV2 value in only 500 auth attempts on average.
That's going to trip a fraud check at the bank and get the card frozen long before 500 attempts.
How many failed CVV2 checks before your account is locked? Something tells me less than 500.
Re:IAmA a malware coder and botnet operator, AMA
by jacquesm on Friday May 11, 2012 @04:24PM
(#3961198)
There is a bit of a difference between an in-flight transaction and a database with historical information.
That company passed PCI-DSS because these were in-flight transactions, if that had been a historical database they would not have passed.
Given that there's only 1,000 CVV2 values (10,000 for Amex) isn't putting so much into CVV2 value a bit ridiculous? Someone who really wanted to could get a CVV2 value in only 500 auth attempts on average.