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.

Attacks/Breaches

6/26/2017
05:16 PM
50%
50%

Anthem Agrees to $115 Million Settlement for 2015 Breach

If approved, it will dwarf settlements paid by Target, Home Depot, and Ashley Madison.

On Friday, June 23, Anthem Healthcare agreed to settle a series of lawsuits related to the company's 2015 data breach, which impacted 78.8 million individuals. The settlement includes a payment of $115 million and three years of additional security protections.

Most of the money will be allotted to an additional two years of credit monitoring and identity protection services, and $15 million will be allocated to pay out-of-pocket costs, up to a certain amount. Class members who claim out-of-pocket costs may receive compensation of $36 to $50. 

If approved by the judge, who is scheduled to hear the motion on Aug. 17, the settlement would be far larger than other recent settlements made for large-scale data breaches: Target agreed to pay $18.5 million last month for a 2013 breach of 41 million customer records, Ashley Madison agreed to pay $17.5 million in December for the doxing attack that affected 37 million customers, and Home Depot paid $43.5 million over two separate settlements (to banks and customers) for a 2014 breach affecting 50 million customers.

According to a statement on the Anthem website, "as part of the settlement, Anthem has agreed to continue the significant information security practice changes that we undertook in the wake of the cyber attack, and we have agreed to implement additional protections over the next three years." According to a preliminary motion filed by attorneys, many details of these protections will remain confidential.

The Anthem attack was reported in February 2015 and leaked customers' income data and Social Security numbers, but likely not medical information. A report by the California Department of Insurance, released in January of this year, stated that an investigation found "with a significant degree of confidence" that a foreign government was behind the attack. Earlier research specifically implicated threat actors operating from China.

Read more details here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
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. 
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: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: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:29:09 PM
Settlement
78.8 million individuals impacted and only $115 Million, this sounds not that much.
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.
<<   <   Page 2 / 2
The Cold Truth about Cyber Insurance
Chris Kennedy, CISO & VP Customer Success, AttackIQ,  11/7/2019
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
6 Small-Business Password Managers
Curtis Franklin Jr., Senior Editor at Dark Reading,  11/8/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16863
PUBLISHED: 2019-11-14
STMicroelectronics ST33TPHF2ESPI TPM devices before 2019-09-12 allow attackers to extract the ECDSA private key via a side-channel timing attack because ECDSA scalar multiplication is mishandled, aka TPM-FAIL.
CVE-2019-18949
PUBLISHED: 2019-11-14
SnowHaze before 2.6.6 is sometimes too late to honor a per-site JavaScript blocking setting, which leads to unintended JavaScript execution via a chain of webpage redirections targeted to the user's browser configuration.
CVE-2011-1930
PUBLISHED: 2019-11-14
In klibc 1.5.20 and 1.5.21, the DHCP options written by ipconfig to /tmp/net-$DEVICE.conf are not properly escaped. This may allow a remote attacker to send a specially crafted DHCP reply which could execute arbitrary code with the privileges of any process which sources DHCP options.
CVE-2011-1145
PUBLISHED: 2019-11-14
The SQLDriverConnect() function in unixODBC before 2.2.14p2 have a possible buffer overflow condition when specifying a large value for SAVEFILE parameter in the connection string.
CVE-2011-1488
PUBLISHED: 2019-11-14
A memory leak in rsyslog before 5.7.6 was found in the way deamon processed log messages are logged when $RepeatedMsgReduction was enabled. A local attacker could use this flaw to cause a denial of the rsyslogd daemon service by crashing the service via a sequence of repeated log messages sent withi...