Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

6/23/2014
11:15 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
100%
0%

P.F. Chang's Breach Went Undetected For Months

Early reports indicate that the compromise involved a large number of restaurant locations and dates as far back as September 2013.

On June 13, restaurateur P.F. Chang’s notified customers via email of a security breach, stating credit and debit card data had been stolen and the company only recently became aware of the breach -- on June 10, 2014. According to a dedicated website for communicating with the public, P.F. Chang’s officials said they learned of the breach from the US Secret Service and are currently working with PCI Forensics Investigators (PFI) to determine its scope.

Although it will take time for investigators to complete the investigation, Brian Krebs reports having a copy of a seemingly related alert sent by the card brands to banks indicating the compromise goes back at least as far as September 18, 2013. These alerts are sent by card brands as they receive fraud reports and look through transaction history to identify a common point of purchase (CPP) from which the cards were likely to have been stolen.

Additionally, Krebs notes that all P.F. Chang’s locations began using old-fashioned “knuckle busters” where a physical imprint of the card is made instead of relying on electronic payment processing. In my experience handling merchant breaches, switching to knuckle busters or standalone terminals where they’re not connected to the point of sale (POS) network is standard practice to continue credit card acceptance without disturbing the POS environment.

Between the information provided by P.F. Chang’s and the information received by Krebs, it’s likely that most, if not all, locations are affected. P.F. Chang’s is privately owned, which means it has control over the IT infrastructure at all locations. That makes this breach very similar to those at Neiman Marcus and Target in terms of potential scope. In all likelihood, a large percentage of its locations were indeed affected.

Who’s to blame?
First and foremost, let me make it clear that the criminals are to blame. P.F. Chang’s is a victim. Based on experience dealing with card data breaches of this magnitude, it’s likely that P.F. Chang’s or a third-party IT services provider overlooked one or more security controls when hardening its network. There could even be a shared responsibility between P.F. Chang’s and an IT services provider, depending on the dynamic of that relationship.

As the intrusion was in progress, it’s also possible that alerts went unnoticed or dismissed as understaffed and underequipped security teams were forced to pick and choose which alerts warranted action. Only in hindsight during the investigation will those alerts stand out. Finally, it could come to light that a seemingly unrelated third party was involved, as was the case in the Target breach where its HVAC service provider was compromised and used to gain initial access.

When seeking to point fingers, keep in mind that complex systems fail usually as a result of multiple points of failure. It’s a fool’s errand to seek out a single cause. Even if an initial entry point were better secured or alerts were investigated, determined and skilled attackers are smart enough to dodge and weave their way to their ultimate goal.

How did this breach unfold?
The public will never know. At best, one or two points of failure will be selectively disclosed as scapegoats. Speaking from first-hand experience, I can provide general information on the attack lifecycle true of most incidents.

The attackers first find an initial point of entry into the victim network such as SQL injection against a web server, remote access using stolen employee credentials, or backdoor access through common droppers or backdoors that made their way to employee systems. Those backdoors could have been deliberately planted by the attackers, or they could be from different opportunistic attackers that sell access on the black market. From that starting point, attackers focus on privilege escalation to get administrative access, lateral movement using built-in system commands to map out the environment, and additional backdoors to ensure access in the event they get busted. Then they locate pivot points into the card data environment (CDE).

Once in the CDE, attackers harvest card data for a long time using specially crafted malware that snags it from memory, LAN traffic, or through keystroke recording. Sometimes they can simply compromise encryption keys and query POS databases. The final step is periodically transmitting the stolen data out undetected. Common methods involve creating an encrypted archive, which bypasses systems designed to identify card data, then sending it out in small chunks to avoid systems monitoring for spikes in network traffic.

What are the lessons learned?
My advice to consumers and businesses continues to be the same. Consumers should monitor financial accounts for unauthorized transactions so they can report them quickly and avoid being held liable. They should prefer credit over other payment options because of laws protecting them from losses. My advice to businesses concerned with security incidents of any kind is to engage security staff in a discussion focused on risk. That will provide the data points needed to make an informed decision on budgeting and prioritization.

With budget and authority in hand, security teams should seek out ways to more effectively manage existing security investments and reduce the noise. Common approaches are fine-tuning current products and automating as much as possible. Next, they should look to improve rapid detection and response capabilities to stay on top of things and ensure that attacks are identified and thwarted before damage is done.

Lucas Zaichkowsky is the Enterprise Defense Architect at AccessData, responsible for providing expert guidance on the topic of cyber security. Prior to joining AccessData, Lucas was a technical engineer at Mandiant where he worked with Fortune 500 organizations, the Defense ...
View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
6/23/2014 | 12:42:53 PM
Hindsight is always 20/20
True, the  public may never know all the details about how this breach unfolded. But it sure will be instructive for securiy teams to learn about P.D. Chang's  errors and failed strategies so they can apply them to their own detection and response capabilities in the future. 
ShahA411
50%
50%
ShahA411,
User Rank: Apprentice
6/23/2014 | 1:18:16 PM
Apprecaited
The security team should take the resposibilities to make the situation calm and quit. It is tru that public do not have adequate concern regarding the issue what happened there. This essay service reviews help to understand more about this
Robert McDougal
50%
50%
Robert McDougal,
User Rank: Ninja
6/23/2014 | 7:02:30 PM
Re: Apprecaited
To me the issue of the security team is what I would like to know more about.  I have been hearing that PF Changs may not have had adequate security controls or personnel in place in the first place.  I would like more concrete infromation on the security posture of PF Changs pre-breach.
lucabranzi
50%
50%
lucabranzi,
User Rank: Apprentice
7/23/2014 | 1:55:39 PM
Interesting
Interesting, companies should do a penetration test like www.stockpairitalia.com
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7029
PUBLISHED: 2020-08-11
A Cross-Site Request Forgery (CSRF) vulnerability was discovered in the System Management Interface Web component of Avaya Aura Communication Manager and Avaya Aura Messaging. This vulnerability could allow an unauthenticated remote attacker to perform Web administration actions with the privileged ...
CVE-2020-17489
PUBLISHED: 2020-08-11
An issue was discovered in certain configurations of GNOME gnome-shell through 3.36.4. When logging out of an account, the password box from the login dialog reappears with the password still visible. If the user had decided to have the password shown in cleartext at login time, it is then visible f...
CVE-2020-17495
PUBLISHED: 2020-08-11
django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.
CVE-2020-0260
PUBLISHED: 2020-08-11
There is a possible out of bounds read due to an incorrect bounds check.Product: AndroidVersions: Android SoCAndroid ID: A-152225183
CVE-2020-16170
PUBLISHED: 2020-08-11
The Temi application 1.3.3 through 1.3.7931 for Android has hard-coded credentials.