South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Bob screwed up, we know that. That's the usual feeling when a breach occured.That isn't even the point; the card numbers and expiry dates are compromised. Bob Shop knows that and is now placing the onus on its shoppers to protect their CVV. The CCV is but a twig. It doesn't matter whether their record held a CCV or not. All these users are exposed.
It actually does matter. Storing the CVV is forbidden under PCI DSS...encrypted or not.It doesn't matter whether their record held a CCV or not
Bob screwed up, we know that. That's the usual feeling when a breach occured.
All the scammers now need is the last leg auth, the cvv or otp. Bob simply stated not to share it with anyone. This is usually a perfect time for that to happen as users may think they are being helped by bob, when the scammer contact them.
To think that a simple warning after the fact is them trying to place the onus on shoppers is ridiculous.
It actually does matter. Storing the CVV is forbidden under PCI DSS...encrypted or not.
And no...its not necessarily "poor security". A zero day exploit, for example, is not your fault.
but it is their responsibility...even though bob didn't say that. The bearer of the card is in possesion of the CVV...but Bob Shop took the position that, though their users are exposed it is the users responsibility to protect their own CCV.
Now why would you want to do that? Just think of the damage that would've been done by now.There are merchants, many global ones, that make CCV optional.
Best option yes. Something a card user should always do. As for cost, yes...there's always a cost for convenience. Breaches do happen, and more now with the help of ai, so if a little cost, time, etc stand in one's way to protect yourself, then she/he must accept the consequences.Bob Shop should have been honest and instructed their users/shoppers to renew their bank cards where virtual ones weren’t in use, and that it will cost them time, money and inconvenience.
Come on now, you know i did not say that.So Bob Shop is in the clear; it could not possibly have been due to poor security.
As a merchant you are allowed to store CVV under PCI DSS, but only temporarily. It must be stored encrypted and securely erased once authorisation has completed.Bob screwed up, we know that. That's the usual feeling when a breach occured.
All the scammers now need is the last leg auth, the cvv or otp. Bob simply stated not to share it with anyone. This is usually a perfect time for that to happen as users may think they are being helped by bob, when the scammer contact them.
To think that a simple warning after the fact is them trying to place the onus on shoppers is ridiculous.
It actually does matter. Storing the CVV is forbidden under PCI DSS...encrypted or not.
And no...its not necessarily "poor security". A zero day exploit, for example, is not your fault.
Agreed. If your card data was exposed you need to disable your card (even if it's a virtual card) and get a new one. There are many merchants locally and globally that don't do 3D secure, and don't require a CVV to perform a transaction.That isn't even the point; the card numbers and expiry dates are compromised. Bob Shop knows that and is now placing the onus on its shoppers to protect their CVV. The CCV is but a twig. It doesn't matter whether their record held a CCV or not. All these users are exposed.
but it is their responsibility...even though bob didn't say that. The bearer of the card is in possesion of the CVV.
Now why would you want to do that? Just think of the damage that would've been done by now.
Best option yes. Something a card user should always do. As for cost, yes...there's always a cost for convenience. Breaches do happen, and more now with the help of ai, so if a little cost, time, etc stand in one's way to protect yourself, then she/he must accept the consequences.
Or rolling the luddite way and have no digital problems.
Come on now, you know i did not say that.
The only thing i blame them for, is...they took way too much time before they warn their users.
Didn't Bob Shop develop bobPay themselves? My guess is these are legacy card records from before their current payment integration.Storing the encryption key with the CC's - genius!
Why are they even processing CC's and not using a 3rd party provider.
Nope.As a merchant you are allowed to store CVV under PCI DSS, but only temporarily. It must be stored encrypted and securely erased once authorisation has completed.
It looks like the breach was limited to legacy payments or as they say "older partial payments".I still haven't received the notice. MyBroadband was my source.