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
Anthem Agrees to $115 Million Settlement for 2015 Breach
Oldest First  |  Newest First  |  Threaded View
Page 1 / 2   >   >>
Joe Stanganelli
100%
0%
Joe Stanganelli,
User Rank: Ninja
6/26/2017 | 6:38:32 PM
Ashley Madison comparison
Of course, Anthem still has a profitable and viable business model -- unlike, in all likelihood, Ashley Madison these days. The Ashley Madison breach did FAR more damage to the company than the legal costs.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/27/2017 | 4:29:09 PM
Settlement
78.8 million individuals impacted and only $115 Million, this sounds not that much.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/27/2017 | 4:31:12 PM
out-of-pocket cost
"Class members who claim out-of-pocket costs may receive compensation of $36 to $50."

This is like a joke, lost my personal data and they pay me $50? Am I getting this right?
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/27/2017 | 4:34:12 PM
Re: Ashley Madison comparison
"Anthem still has a profitable and viable business model"

I would think so, they might also still be suing old technologies.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/27/2017 | 4:35:40 PM
Re: Ashley Madison comparison
"The Ashley Madison breach did FAR more damage"

And also embarrassment to the users of the site.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/27/2017 | 4:35:57 PM
medical information
 

"but likely not medical information."

Why is this still "likely", there is a settlement and we still do not know if medical data was breached. 
Sara Peters
50%
50%
Sara Peters,
User Rank: Author
6/28/2017 | 10:36:21 AM
Re: out-of-pocket cost
@Dr. T:  I'm with you. These settlements sound big at first, but once you factor in the number of people involved, it becomes pretty pitiful.

And yet this is a, comparatively, very big settlement, against a company that actually handled their breach response quite admirably. Other companies that did a lousy job from start to finish and showed no regard for their customers (Ashley-Madison) got away with smaller settlements.

 
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/28/2017 | 12:18:35 PM
Re: Ashley Madison comparison
@Joe Very much agree with your comparison. Ashley Madison would have tarnished their brand reputation as well. Similar to Arthur Andersen back in the Enron days, these indirect costs can cripple an organizaiton into extinction. We shall see how AM fairs in the years to come.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/28/2017 | 12:22:41 PM
Re: out-of-pocket cost
@Dr.T, as Sarah stated when the hard numbers are broken down the numbers aren't a good reflection of how an individual should be compensated for a loss of their information. The numbers are most definitely jokeworthy. But playing devil's advocate, what should the numbers be for a payout for losing personal data? Based on the amount of users would Anthem be able to support this claim and stay in business? 
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
6/29/2017 | 9:32:44 AM
Re: out-of-pocket cost
@Sara: But health data is a more legally protected class of information than whether one is looking to cheat on a partner. Plus, I daresay that Anthem has *waaaaay* more customers than Ashley Madison ever did. On a related note, potential HIPAA violations created tons of potential liability that Anthem wanted to avoid seeing a day in court over. So the difference in the settlement amounts makes sense for these reasons alone.

Also, as I understand it, the Ashley Madison breach involved an insider attack -- which, unfortunately, one can only do so much to prevent. The Anthem breach, however, involved a series of major security missteps. ( See, e.g., enterprisenetworkingplanet.com/netsecur/anthem-could-face-legal-fallout-from-hack.html ). And even then, months passed between the time evidence of a likely attack became known (thanks to independent security researchers) and Anthem actually did anything.
Page 1 / 2   >   >>


Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-14905
PUBLISHED: 2020-03-31
A vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craft the filename parameter to perform OS co...
CVE-2020-11441
PUBLISHED: 2020-03-31
phpMyAdmin 5.0.2 allows CRLF injection, as demonstrated by %0D%0Astring%0D%0A inputs to login form fields causing CRLF sequences to be reflected on an error page.
CVE-2020-1712
PUBLISHED: 2020-03-31
A heap use-after-free vulnerability was found in systemd before version v245-rc1, where asynchronous Polkit queries are performed while handling dbus messages. A local unprivileged attacker can abuse this flaw to crash systemd services or potentially execute code and elevate their privileges, by sen...
CVE-2019-10180
PUBLISHED: 2020-03-31
A vulnerability was found in all pki-core 10.x.x version, where the Token Processing Service (TPS) did not properly sanitize several parameters stored for the tokens, possibly resulting in a Stored Cross Site Scripting (XSS) vulnerability. An attacker able to modify the parameters of any token could...
CVE-2019-14880
PUBLISHED: 2020-03-31
A vulnerability was found in Moodle versions 3.7 before 3.7.3, 3.6 before 3.6.7, 3.5 before 3.5.9 and earlier. OAuth 2 providers who do not verify users' email address changes require additional verification during sign-up to reduce the risk of account compromise.