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.

ABTV //

Vulnerability

5/30/2017
06:45 PM
Curtis Franklin
Curtis Franklin
Curt Franklin
50%
50%

Lessons From Chipotle's Big Customer Data Breach

Burritos with a side of delicious guacamole and potential identity theft.

The merry month of May couldn't end without another data breach and everyone's favorite fast-casual burrito company was the unlucky victim. Chipotle Mexican Grill has provided more details on a breach they first hinted at in April. For those who always read to the end, first: The breach was real, and it was everywhere.

This latest in the ongoing series of corporate data breaches has a familiar ring to it because it contains the three major elements seen in many such breaches in the last few years:

Internet of Things -- The malware used to steal customer information didn't live on the servers or the network, Instead, it was planted on the point-of-sale (POS) terminals used to capture payment information at the restaurants. This is important because most IoT devices, including virtually all POS terminals are assumed to have software and firmware that never changes, or changes only when the vendor pushes a specific update. That assumption means that most of these terminals aren't covered by the same sort of change-management regimen enforced on other, more general-purpose endpoint, allowing hacks to take place and go unnoticed. Which leads to the next element...

Long duration -- Chipotle says that the malware was in place from March 24 until April 18 of this year. That's nearly a month of unfettered access to customer payment information. What kind of information? On a blog post aimed at investors, Chipotle said, "The malware searched for track data (which sometimes has cardholder name in addition to card number, expiration date, and internal verification code) read from the magnetic stripe of a payment card as it was being routed through the POS device."

Most security experts say that effective layered security includes the ability to quickly understand when a breach has occurred so that remediation can begin immediately. While a month is certainly less than the months-long excursion hackers undertook inside Sony's systems, it's still a very long time in the internet era.

Ubiquity -- Thought Chipotle initially said that the breach hit "some" of their stores, more recent reports indicated that "most" stores felt the impact. As a result, Chipotle is facing regulatory pressure to alert all affected customers, even though the company doesn't really know who they might be. At this point, Chipotle is left to provide a website with affected locations and dates, with customers left to worry whether their information is among that purloined by thieves.

Chipotle's customers are now concerned about data theft, while the company's management is concerned about losses of reputation (especially following the food safety issues of previous years) and money (to regulators eager to teach a lesson to the industry.) For companies eager to avoid following in the burrito giant's footsteps, there are three lessons that can be taken from this incident that might well be applied:

  • Secure your IoT -- Add IoT devices to your change management regimen even if you never intend to update software. Change default passwords. And put IoT devices behind a firewall or UTM that shields them from the beginner-level hacks that seem too common in this part of the computing world.
  • Watch your traffic -- Before you install IoT device understand what normal traffic from them will look like and where it will be going. That way you will have a chance of being warned earlier if something untoward is happening.
  • Protect network segments -- It's so easy to put every device of a given type on the same (or on highly similar) network(s). But keep endpoint devices on network segments that can be separately monitored for traffic and protected from easy hacks. At the very least, you'll reduce your background noise and increase your chances of understanding quickly when something terrible has been done to your IoT.

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
News
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
News
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: George has not accepted that the technology age has come to an end.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2009-20001
PUBLISHED: 2021-03-07
An issue was discovered in MantisBT before 2.24.5. It associates a unique cookie string with each user. This string is not reset upon logout (i.e., the user session is still considered valid and active), allowing an attacker who somehow gained access to a user's cookie to login as them.
CVE-2020-28466
PUBLISHED: 2021-03-07
This affects all versions of package github.com/nats-io/nats-server/server. Untrusted accounts are able to crash the server using configs that represent a service export/import cycles. Disclaimer from the maintainers: Running a NATS service which is exposed to untrusted users presents a heightened r...
CVE-2021-27364
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. drivers/scsi/scsi_transport_iscsi.c is adversely affected by the ability of an unprivileged user to craft Netlink messages.
CVE-2021-27365
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. Certain iSCSI data structures do not have appropriate length constraints or checks, and can exceed the PAGE_SIZE value. An unprivileged user can send a Netlink message that is associated with iSCSI, and has a length up to the maximum length...
CVE-2021-27363
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. A kernel pointer leak can be used to determine the address of the iscsi_transport structure. When an iSCSI transport is registered with the iSCSI subsystem, the transport's handle is available to unprivileged users via the sysfs file system...