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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
Two More Health Insurers Report Data Breach
Threaded  |  Newest First  |  Oldest First
xmarksthespot
xmarksthespot,
 User Rank: Strategist
3/17/2015 | 9:34:47 PM
Your rights when critical data is stolen; demand fair compensation
I'll state my bias, since that's appropriate in this case.  I am an information security professional.  However, I am also a person very interested in consumer issues and consumer rights.

You have rights as a customer of organizations which failed basic security in their infrastructure.  Basic prevention techniques could have made exploitation much more difficult.  Do you think 1 year of credit monitoring will fully protect you?  The answer it is not even remotely close to even the basic protection required.   Identify theft may be the least of their worries.  In some of these cases there are bank account numbers floating around.

This is getting to be a major confidence issue on the banking system.

At a minimum, I feel lifetime credit protection should be mandated, and the ability to pay for lifetime credit locks.  That is the absolute most basic thing they should pay.  What would that cost?  Well, to lock credit reports is $5 or more for each one (at this time).  In addition, if you want a loan or needed a credit check, you have to pay for unlocks.  Is it your fault you need that unlock?  Demand an adequate amount of money to pay for lifetime credit locks and unlocks and credit monitoring.  Even with credit locks, the credit is opened for a window of time where others could exploit it.  This is serious and corporations shouldn't be trying to weasel their way out of their liability by offering one year of credit monitoring.
Sara Peters
Sara Peters,
 User Rank: Author
3/18/2015 | 8:54:02 AM
Re: Your rights when critical data is stolen; demand fair compensation
@xmarksthespot  Well, I agree with you, that one or two year/s of credit monitoring doesn't help all that much if Social Security numbers were compromised, because SSNs last forever. They might get stolen today and still be used fraudulently 10 years from now.

I doubt there will come a time when companies are required to do as you suggest, but maybe if they were, they would be inspired to invest in more security measures.
SgS125
SgS125,
 User Rank: Ninja
3/18/2015 | 10:48:01 AM
Lifetime?
I agree that the free monitoring will not really help for most cases of fraud and abuse of PII, but what about having to show damage if you require a company to provide you with lifetime protection?

 

There are many cases of data breach in 2014, not all lead to financial loss of identity theft.

 

Perhaps if someone wins a lawsuit showing some strong evidence of lifelong risk of loss then we can make the solution fit the problem.

 

You will always have the risk of Identity Theft even if your information was not lost in a data breach.  A dedicated foe can cause as much damage as a script kiddie using SQL injection. 
ajones980
ajones980,
 User Rank: Strategist
3/19/2015 | 1:48:05 PM
Not two companies - the same one, same breach.
Lifewise & Premera are basically the same company. Note that their careers links take you to a premera.com job site. This, combined with the same content at premeraupdate.com and lifewiseupdate.com, appears to show that this is one attack on one target.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Machine Learning, AI & Deep Learning Improve Cybersecurity
Machine intelligence is influencing all aspects of cybersecurity. Organizations are implementing AI-based security to analyze event data using ML models that identify attack patterns and increase automation. Before security teams can take advantage of AI and ML tools, they need to know what is possible. This report covers: -How to assess the vendor's AI/ML claims -Defining success criteria for AI/ML implementations -Challenges when implementing AI
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-42002
PUBLISHED: 2022-10-01
SonicJS through 0.6.0 allows file overwrite. It has the following mutations that are used for updating files: fileCreate and fileUpdate. Both of these mutations can be called without any authentication to overwrite any files on a SonicJS application, leading to Arbitrary File Write and Delete.
CVE-2022-39268
PUBLISHED: 2022-09-30
### Impact In a CSRF attack, an innocent end user is tricked by an attacker into submitting a web request that they did not intend. This may cause actions to be performed on the website that can include inadvertent client or server data leakage, change of session state, or manipulation of an end use...
CVE-2022-34428
PUBLISHED: 2022-09-30
Dell Hybrid Client prior to version 1.8 contains a Regular Expression Denial of Service Vulnerability in the UI. An adversary with WMS group admin access could potentially exploit this vulnerability, leading to temporary denial-of-service.
CVE-2022-34429
PUBLISHED: 2022-09-30
Dell Hybrid Client below 1.8 version contains a Zip Slip Vulnerability in UI. A guest privilege attacker could potentially exploit this vulnerability, leading to system files modification.
CVE-2022-40923
PUBLISHED: 2022-09-30
A vulnerability in the LIEF::MachO::SegmentCommand::virtual_address function of LIEF v0.12.1 allows attackers to cause a denial of service (DOS) through a segmentation fault via a crafted MachO file.