This is page 2 of:
Major Chain Loses PCI Compliance When Data Center Moves
A conference call was quickly scheduled with the merchant’s acquiring bank and key card brands to discuss the PCI compliance reporting options. And, yes, there were some serious differences of opinion between the retailer and the QSA. Those options were: (1) mark the network flat and not segmented and reference the new data center project as the reason for the situation and non-compliance or, (2) develop a compensating control for the flat network. The reason that the current network configuration results in non-compliance is that not all of the devices on the network are properly configured and controlled to ensure PCI compliance because these devices have been out of scope in past PCI assessments.
If marked non-compliant, this will require that the acquiring bank monitor the data center project through completion and then ensure that the ACLs are placed back in operation to properly segment the network. Although this is the QSA’s preferred option, the chain does not want to be flagged as non-compliant, so they are pushing for a compensating control.
During the acquiring bank conference call, the reporting options are discussed. Although the QSA and internal audit push for the non-compliant Report On Compliance option, the merchant’s management pushes for a compensating control. The QSA discusses the fact that the controls the merchant intends to rely upon do not appear to meet the “above and beyond” requirement.
At the end of the call, the acquiring bank decides they also do not want to deal with a non-compliant ROC, and they tell the QSA to prepare a compensating control that they will evaluate prior to submission of the ROC. A few weeks later, the QSA submits the compensating control for the acquiring bank’s review. Except for a few wording changes, the compensating control is accepted and the merchant’s ROC is completed.
What are the lessons that can be learned from this incident?
Jeff can be reached at pciguru@gmail.com.
-Marc
July 16th, 2013 at 7:07 pm
Many companies are loosing PCI compliance when they move to the cloud. Not because of data center standards but because of not properly securing their sensitive customer data.
July 17th, 2013 at 10:05 am
“Real world” PCI news is precisely why I keep coming here and I love case studies like this. Please keep ’em coming!
July 18th, 2013 at 9:09 am
So….. who is this major chain retailer?
July 18th, 2013 at 10:07 am
A simple data center transition? Ha!
July 18th, 2013 at 1:45 pm
I’d like to know… who is the acquiring bank.
July 18th, 2013 at 7:53 pm
“PCI compliance is all in the eyes of the beholder”
Well then maybe the beholder had better take off his rose-colored glasses, huh?
July 19th, 2013 at 10:51 pm
This real-world example demonstrates the complexities of maintaining PCI compliance and the importance of the QSA’s relationship with the merchant. Another lesson learned here is that retailers should work with their QSA throughout the year and develop a trusting relationship, as opposed to communicating only during assessment activities.
July 22nd, 2013 at 3:35 am
I’d like to know what the compensating control was/is so that I can apply that to my flat network to “win out over a non-compliant ROC”.