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

10/6/2017
09:45 AM
Simon Marshall
Simon Marshall
Simon Marshall
50%
50%

SONIC Quiet on Data Breach Details

Drive-in restaurant chain SONIC has suffered a breach but customers and the public are still looking for critical details.

For consumers, this is the Year of Living Dangerously. First Yahoo, followed by Equifax and then SONIC Drive-in. Both Yahoo and Equifax released statements this week that showed they'd underestimated (Yahoo, wildly) the scope of damage. Consumers either already do, or will soon know, if their drive-thru burger, fries and shake had an undisclosed big price ticket attached.

We still don't know the number of SONIC outlets affected, how many cards were compromised, or how much pain consumers are feeling. But we can guess. The biggest drive-in burger chain in America is tight-lipped, and as we've seen with other similar breaches, that's not always the best strategy.

SONIC's perspective is that all of this is subject to legal requirement. "The investigation by law enforcement and third-party forensic firms continues, which limits the information we can share," said Christi Woodworth, VP public relations, SONIC Drive-in, not commenting beyond that.

Others have a different view. "SONIC has been strangely and dangerously quiet in the wake of its recent credit card hack," Steve Morgan, founder at market research firm Cybersecurity Ventures told SecurityNow. "If we've learned anything from the aftermath of the world's two largest hacks -- on Yahoo and Equifax -- it's that senior executive and IT management should come clean early. The best post-hack practice is to get loud, quick."

SONIC has upped the volume on one front: offering generic security advice to consumers. It's fair to assume that since SONIC scanned the credit and debit cards of its customers -– and stored that data on its own servers -- that SONIC is responsible for it. And yes, SONIC is likely a victim here too. But offering reminders to customers to check their statements, freeze their credit reports and in general be more vigilant is closing the stable door after the horse has bolted.

Interestingly, SONIC has been offering advice about potential ID theft and that may indicate that more than just card numbers and names were stolen. But again, it's just not clear. In our book, if there's no suggestion consumers did anything to expose themselves, the onus is on the businesses to make good.

Meantime, we're left to take an educated guess at what happened.

To begin with, it may have been perpetrated by a SONIC insider, not necessarily a staff member. Historically, hackers have used third party contractors to a retail outlet to get them inside. It's also fair to speculate that the target was a central server, since a compromise at this level could have driven the scale to compromise a huge number of locations.

"In similar attacks, you see criminals going after servers that either distribute the software to POS systems or collect the transactional data from them," Fernando Montenegro, a senior info-sec analyst at 451 Group, told Security Now. The card details have indeed been harvested and already been dropped onto at least one card dump site and sold on to buyers. Usually from there, the strategy is to use those details to purchase big-ticket retail items using stolen details, and then launder these through online auction sites.

This type of attack could have been prevented by some commonly used controls including stronger authentication requirements for administrative functions, and the use of tighter application controls on the POS devices themselves. There are also upgrades to payment systems that restrict where and how the card data resides and flows, but those upgrades are usually a relatively complex process that takes time and cost.

451's Montenegro thinks that SONIC's franchisee structure may hamper prevention. "It certainly adds a layer of complexity, both in terms of having to potentially coordinate not only day-to-day operations but also long-term updates" he said. "It's one more thing for the business to address in their franchising agreements."

As SONIC presumably moves into repairing its security administration and systems after forensics, consumer groups are becoming angry at what they see as weak regulation and protection in cases of cybertheft.

John Simpson, privacy project director at consumer advocacy group, Consumer Watchdog, said of current provisions, that they're "completely inadequate. Many businesses make a calculated assessment that it's cheaper to run the risk of a break or hack than to provide adequate security."

Consumer Watchdog lobbies for improvements in requirements for consumer security protections at both the national and state level, but it's an uphill battle. "It's very frustrating in the current anti-regulatory mindset of the Trump Administration and Republican Congress. It's always a David versus Goliath battle when consumer groups confront businesses about necessary regulatory reforms," said Simpson.

So, where's the weak spot, who's to blame, who's accountable? Consumers? Businesses? The regulatory system?


Want to learn more about the tech and business cases for deploying virtualized solutions in the cable network? Join us in Denver on October 18 for Light Reading's Virtualizing the Cable Architecture event – a free breakfast panel at SCTE/ISBE's Cable-Tec Expo featuring speakers from Comcast and Charter.

"We're seeing a lot more consumer anger rightfully directed at mismanagement related to breaches and their responses, [at firms such as] Equifax and Yahoo," said 451's Montenegro. One can speculate that if the upper echelons are out of touch with today's security requirements, then we're all in very big trouble.

Watchdog's Simpson says that the situation is conceptually akin to when debit and credit cards first become more secure through chip and pin authentication; almost overnight more than a decade ago, Europeans gained a couple of layers of further protection against anyone unscrupulously nabbing their details. Meanwhile in the US today, magnetic strips are still prominent and a four-digit pin and written signature is all that's needed to authenticate.

"Chip-and-pin costs more and American businesses are too cheap to use it," he said.

Related posts:

— Simon Marshall, Technology Journalist, special to Security Now

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.