Major Chain Loses PCI Compliance When Data Center Moves
Written by Jeff HallJeff Hall is a Senior Security Consultant with FishNet Security and has been a QSA since 2007.
One of the nation’s 15 largest retail chains had done a tremendous job segmenting its network to reduce the scope of its PCI assessment. All of that was thrown away, though, during a simple data center transition, when Networking made a security change but no one ever bothered to tell senior IT management.
Late last year, the chain decided to move its data center from an in-house facility to a purpose-built data center campus in another part of the United States. The goal was to gain additional raised floor space, energy efficiency and to avoid significant natural disaster risks with the location of the existing data center. In the QSA’s review of the new data center, it was seen as a model of energy efficiency and modern design of data centers. So far, so good.
But when the QSA returned for the annual PCI assessment, a review of the core switch and the layer 3 ACLs (Access Control Lists) revealed that all of the switch’s ACLs have been disabled—commented out—for both data centers. The formerly segmented network was totally flat with no segmentation.
The situation had existed since the start of the migration process and would continue for at least another five or six months until the new data center was totally built out with equipment. The reason for this PCI compliance gaff? Networking did it to ensure that production outages did not occur as equipment was migrated from the old data center to the new data center.
The networking group decided to disable the ACLs on the firewalls, routers and switches to accommodate changes to the IP addressing and certain DNS naming conventions that were being implemented with the new data center. From Networking’s perspective, production was more sacred than security. And although a few IT people were informed, no one bothered to brief senior IT management.
From a security standpoint, this was a terrible move as it made the cardholder data environment extremely accessible because everything was suddenly in scope. As a result, the external firewall became the only barrier to the CDE (Cardholder Data Environment). The chain should have never disabled the ACLs. Instead, they should have planned better and adjusted the ACLs to work with the new data center.
Networking’s thinking was that this was a very temporary move. It was not that the network would run forever in this configuration. It was just to be in place during the transition.
From a PCI compliance standpoint, this temporary change was quite problematic. The timing would make the ACLs disabled well past the end of the annual PCI compliance reporting period. 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.
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”.