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.

Comments
Be Careful Beating Up Target
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
Duane T
100%
0%
Duane T,
User Rank: Apprentice
4/1/2014 | 12:13:32 PM
False premise of manual processes
Target was certified via PCI DSS in September, so some might believe that they were doing what was necessary to secure their data. Unfortunately, Compliance ≠ Security, and malware detection is like a red flashing light and siren. If you do nothing about it, all you can say is that you were warned.

That's why it's about time that these companies all invested in automated incident response systems that lock down a detected threat. What's odd in this situation is that FireEye has an entire "mitigation" partner page for this on their website, and Target did not use any of them. Think about it - if they used automated detection tools, why not use automated incident response tools that reduce manual tasks and eliminate human error? This doesn't have to be that complicated.

Wait, in a few seconds I found NetCitadel, Bradford Networks, and ForeScout as mitigation options.
marcelbrown
100%
0%
marcelbrown,
User Rank: Apprentice
4/1/2014 | 11:43:41 AM
It's Windows, Stupid!
Target was better prepared than most of the industry, yet they still couldn't shake the one simple, inherent weakness that most of the industry still chooses to ignore - Microsoft Windows.

Until companies get serious about moving away from Windows, they aren't really serious about security. You can't be serious about protecting your company and your customers if you build your information technology infrastructure on top of a foundation that is full of security holes.

Sure, let's not blame Target because they seemed to do almost everything right - except the choice of their core technology.
speshul
100%
0%
speshul,
User Rank: Strategist
4/1/2014 | 9:52:31 AM
Seriously?
So we're supposed to take it easy on Target because other companies are just as bad? That's the most insane thing I've ever heard. So because other companies are just as bad at protecting our sensitive personal information, we should be nice?

 

We should be crucifying every last one of them. I can guarantee that all of these companies have I.T. teams that warn them about these problems, but the companies choose to ignore them due to budget or other reasons. Just like Target had been warned by it's team.

 

But yet, we are supposed to go easy on them. Because clearly Target's credit was screwed over right? Their negligence for their customers' information in some way hurt them financially right?! WRONG. The customers were the ones who lost in this, all because of corporate greed.

 

CRUCIFY THEM ALL!
<<   <   Page 2 / 2


COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.