3 ms·
> PCI compliance is an absolute nightmare, and is not something to be reasoned with, trust me. Logical thought and analysis has no place in PCI compliance. Foll
by tzs 10y ago
> PCI compliance is an absolute nightmare, and is not something to be reasoned with, trust me. Logical thought and analysis has no place in PCI compliance. Follow the rules or else.
It's amazing how much of a pain it can be to deal with PCI, at least if you try to strictly follow the rules as written.
For example, users will send email to support@yourcompany that says something like "I have a new credit card. Please update my subscription to bill using my VISA card 4111111111111434 with security code 123, expires 2020-03 instead of my current card, MasterCard 5111111111111506, security code 876, expires 2016-11. My account number is 123456. Thanks!".
Of course that automatically generates a ticket in your ticket tracking system, and so now you've got a couple plain text credit card numbers (with CSCs!) in the ticket tracking database...which you never intended to store credit cards and have outside the PCI network's firewall.
Is this a problem? It's a credit card number and it is stored on one of your servers, so one could certainly make a strong case that you need to get rid of it at the very least, and maybe you even need to have the ticket tracker inside the PCI network firewall and subject to all of the annoying PCI access restrictions. Ugh!
And what if you are using a ticket tracker product that you don't host yourself? It's hosted on the vendor's servers. If a user sends in a credit card number in a support request, who is responsible for dealing with it? You, or the ticket tracker server provider?
And it gets even worse. Suppose you've got anti-spam software running on your mail system. When that user mailed a credit card number to support@yourcompany, the anti-spam software saw the credit card number. It might now be stored in a token database for the anti-spam software's bayesian filters.
How the heck are you supposed to deal with that?
If you have any forums, they can also have this problem. Or if you have a company blog that allows users to comment. And what if you are outsourcing the comments to some place like Disqus?
Then there is the problem of telephones. Customer calls your support line after hours, and leaves a message letting you know of their new credit card number, and giving the details. Oops...now you've got a stored credit card number in the saved recording of that customer's message. Does this mean your whole damned phone system has to be on the secure network and is in scope for PCI? (And what if you've outsourced your phone system?)
- smallnamespace 10y agoAren't the rules functioning properly in this case by identifying a real problem? Namely, that you shouldn't have credit card numbers inside an insecure system, whether a ticket tracker or an answering machine.
- tzs 10y agoMy point is that credit card numbers can end up on almost any system that has data entered (directly or indirectly) by end users, even if it is not a system that is part of your actual credit card processing path. Heck, I've seen people somehow end up putting a credit card number in the address field when giving their shipping address, on a form that was nowhere near anything that actually asked for a credit card number.