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
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
7/1/2017 | 12:53:37 PM
Re: out-of-pocket cost
@Ryan: Ah, so as I refresh myself from some notes, it seems that more than just health information was compromised. PII was compromised of both patients and employees.

Here's a piece I wrote at the time on the what and the how: enterprisenetworkingplanet.com/netsecur/anthem-could-face-legal-fallout-from-hack.html
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
7/1/2017 | 12:51:41 PM
Re: Ashley Madison comparison
@Ryan: This goes to my fundamental marketing philosophy: You don't define your brand; your audience does.

As people have started to use Tinder for less ephemeral relationships (i.e., using it for more than, er, what it has become best known for), the app's/company's brand has fundamentally changed.

Similarly, as people have become more interested in the immediacy that Tinder has to offer, competition like OKCupid has had to adjust.

Ashley Madison?  Soooo 2011.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/29/2017 | 10:00:00 AM
Re: Ashley Madison comparison
@Joe Just need to rebrand....I was told by some people I know that Tinder is a "dating service", which I guess on some levels is fundamentally true. Like Comcast with Xfinity, just change the overall branding and everyone will forget what happened in the past :)  
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
6/29/2017 | 9:49:26 AM
Re: out-of-pocket cost
@JoeStanganelli. Great response. I would be less likely to find concern over loss of my medical records than if my identity information were to be breached. But I very much understand where individuals may be concerned.

What were the individual data sets that were lost during this breach? Thanks,
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
6/29/2017 | 9:43:04 AM
Re: Ashley Madison comparison
@RyanSepe: Not that I'd be one to know (ahem), but it seems to me that Ashley Madison would need to make a major pivot (to say the least) to resume relevance in this, the age of Tinder -- security breach or no.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
6/29/2017 | 9:41:22 AM
Re: out-of-pocket cost
@Ryan: Sure, I agree with you...but look at it this way:

The damage the individual suffers potentially can be much higher -- but is often well mitigated with credit monitoring and similar services. Bought in bulk for thousands or millions of data-breach victims, that helps bring costs down.

The value the attacker gets for a single person's health credentials is probably on the order of about $25.

And then, of course, there are the additional statutory damages. And, of course, the overall cost to society as a whole.

Makes it all seem rather piddling, looked at this way. We're not talking about a toxic tort case like from A Civil Action or Erin Brockovich, after all.

But, of course, when you look at it more empathetically and/or subjectively, those numbers tend to become mentally adjusted much higher. How would you want to be compensated if your medical records were given to someone else?

Which is why settlements happen. Nobody in Anthem's position wants to go to a trial -- and probably not even arbitration.

(Incidentally, this is why official class representatives tend to get compensated far higher than Johnny-come-latelies who join the class afterwards upon learning of their eligibility -- because the class representatives are more directly involved in the litigation.)

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.
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? 
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.
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.

 
Page 1 / 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...