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


COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/23/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Russian Military Officers Unmasked, Indicted for High-Profile Cyberattack Campaigns
Kelly Jackson Higgins, Executive Editor at Dark Reading,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-24847
PUBLISHED: 2020-10-23
A Cross-Site Request Forgery (CSRF) vulnerability is identified in FruityWifi through 2.4. Due to a lack of CSRF protection in page_config_adv.php, an unauthenticated attacker can lure the victim to visit his website by social engineering or another attack vector. Due to this issue, an unauthenticat...
CVE-2020-24848
PUBLISHED: 2020-10-23
FruityWifi through 2.4 has an unsafe Sudo configuration [(ALL : ALL) NOPASSWD: ALL]. This allows an attacker to perform a system-level (root) local privilege escalation, allowing an attacker to gain complete persistent access to the local system.
CVE-2020-5990
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in the ShadowPlay component which may lead to local privilege escalation, code execution, denial of service or information disclosure.
CVE-2020-25483
PUBLISHED: 2020-10-23
An arbitrary command execution vulnerability exists in the fopen() function of file writes of UCMS v1.4.8, where an attacker can gain access to the server.
CVE-2020-5977
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in NVIDIA Web Helper NodeJS Web Server in which an uncontrolled search path is used to load a node module, which may lead to code execution, denial of service, escalation of privileges, and information disclosure.