Attacks/Breaches

11/17/2014
07:30 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

The Year Of The Retailer Data Breach

This year's wave of attacks was more dramatic in its widespread scope and seemingly constant battering of more than a dozen big box chains.
Previous
1 of 14
Next

Cybercriminals found their sweet spot this past year with the retail industry, where some of the biggest big-box brand names and franchises were infiltrated by malware that helped the bad guys steal millions of credit and debit-card account numbers of shoppers. 

(Image: Sean MacEntee)

(Image: Sean MacEntee)

Data breaches are nothing new for the retail industry -- think TJX in 2005, Dave & Buster's in 2007, to name a few -- but this year's wave of attacks was different and more dramatic in its widespread scope and seemingly constant battering of big box retailers, with more than a dozen of them disclosing data breaches, including Target, Home Depot, Michael's, Dairy Queen, and most recently, Kmart. 

Target became the poster child for how not to conduct an incident response operation, with more than 40 million payment cards pilfered from its computers after ignoring security alarms from the attack and then experiencing a public disclosure disaster that ultimately resulted in the departure of its CIO and CEO.

[The next Dark Reading Radio episode on Nov. 19 at 1:00 p.m. ET (10:00 a.m. PT) features retail security experts from Mandiant and the retail industry. Read Retail Hacking: What To Expect This Holiday Season.]

So just in time for the 2014 holiday shopping season, here's a look at 13 major retailers who revealed this past year that they had suffered data breaches. Don't be suprised if a few more come forward before we ring in 2015. 

 

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Previous
1 of 14
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
GaryG880
50%
50%
GaryG880,
User Rank: Apprentice
11/22/2014 | 8:22:49 PM
Re: So has the retail industry learned from all these high profile breaches?
One easy answer   NO!
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
11/18/2014 | 5:03:17 PM
Re: So has the retail industry learned from all these high profile breaches?
@TomT640, that's one of the issues I will be asking our retail security experts tomorrow on Dark Reading Radio. There was a study today from BitSight that found 1/3 of retail breaches originated from their 3rd party vendors. 
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
11/18/2014 | 4:28:44 PM
Re: So has the retail industry learned from all these high profile breaches?
That's a good point, @TomT640, (not to mention that I really liked the metaphor "pulling their socks up.")

I hope you'll bring your point of view to our Dark Reading Radio show tomorrow (Wed. 11/19 at 1 pm. EST). We have a great topic Retail Hacking: What To Expect This Holiday Season, with Kelly Jackson Higgins and her guests, Nick Pelletier, senior consultant, Mandiant, and Arthur Tisi, CIO, Natural Markets Food Group. They'll be  talking about what retailers can do to keep both their customers and their transactions safe.

Here's the link to the show: http://www.darkreading.com/radio.asp?webinar_id=162

 
TomT640
50%
50%
TomT640,
User Rank: Apprentice
11/18/2014 | 12:33:48 PM
So has the retail industry learned from all these high profile breaches?
It would seem that those that were breached are 'pulling up their socks' as they say in England but that is no easy task given that a lot of these profiled breaches were down to vulnerabilities in their supply chain.  It is one thing to put your own house in order, it is more challenging to figure out what 3rd parties can and should do, in order to make you more secure.
12 Free, Ready-to-Use Security Tools
Steve Zurier, Freelance Writer,  10/12/2018
Most IT Security Pros Want to Change Jobs
Dark Reading Staff 10/12/2018
Most Malware Arrives Via Email
Dark Reading Staff 10/11/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-1744
PUBLISHED: 2018-10-15
IBM Security Key Lifecycle Manager 2.5, 2.6, 2.7, and 3.0 could allow a remote attacker to traverse directories on the system. An attacker could send a specially-crafted URL request containing "dot dot" sequences (/../) to view arbitrary files on the system. IBM X-Force ID: 148423.
CVE-2018-1747
PUBLISHED: 2018-10-15
IBM Security Key Lifecycle Manager 2.5, 2.6, 2.7, and 3.0 is vulnerable to a XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 148428.
CVE-2018-18324
PUBLISHED: 2018-10-15
CentOS-WebPanel.com (aka CWP) CentOS Web Panel 0.9.8.480 has XSS via the admin/fileManager2.php fm_current_dir parameter, or the admin/index.php module, service_start, service_fullstatus, service_restart, service_stop, or file (within the file_editor) parameter.
CVE-2018-18322
PUBLISHED: 2018-10-15
CentOS-WebPanel.com (aka CWP) CentOS Web Panel 0.9.8.480 has Command Injection via shell metacharacters in the admin/index.php service_start, service_restart, service_fullstatus, or service_stop parameter.
CVE-2018-18323
PUBLISHED: 2018-10-15
CentOS-WebPanel.com (aka CWP) CentOS Web Panel 0.9.8.480 has Local File Inclusion via directory traversal with an admin/index.php?module=file_editor&file=/../ URI.