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
Privacy: Do We Need a National Data Breach Disclosure Law?
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
3/30/2018 | 6:42:18 PM
Re: Victim Shaming
@Dallas: On this "victim shaming", I'm going to suggest that in some cases it's well deserved. Facebook deserves it now and deserved it in 2012 because of how they have disrespected users and their data for so long. Uber deserves it too, for similar reasons. The healthcare industry DEFINITELY deserves it because they are lagging behind so much -- and because people don't have as much choice about their healthcare providers or insurance carriers. And it's a huge motivator for e-commerce -- because they know that the brand damage will simply cause people to move to another platform (unlike with, say, a bank; people aren't going to en masse move investment accounts and mortgages and credit cards because of a little breach -- especially considering the consumer protections in financial services).
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
3/30/2018 | 6:36:55 PM
Re: Web
Sure, but we ALREADY HAVE numerous state laws here. Federal law on data-breach notification specifically isn't going to add any meaningfully significant privacy protections (unless there was to be a severe cracking down, with far stricter requirements and shorter deadlines than even the strictest states require -- which would have its own drawbacks) except to further confuse compliance officers and confound compliance efforts -- the cost of which get passed on to customers, meaning that these companies now need to sell even MORE user data.
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
3/30/2018 | 6:33:37 PM
Let's leave it alone.
I understand the concerns, but at this point, it doesn't matter much. Almost all the states have their own laws here, and the strictest states (effectively MA, CA, and -- where PCI-DSS is concerned -- MN, NV, and WA) effectively create "floors" for national/regional organizations. To put federal law/regulation on top of this all would seriously muck things up even more for compliance efforts, IMHO.



(Disclaimer: This post is provided for informational, educational and/or entertainment purposes only. Neither this nor other posts here constitute legal advice or the creation, implication or confirmation of an attorney-client relationship. For actual legal advice, personally consult with an attorney licensed to practice in your jurisdiction.)
DallasBishoff
DallasBishoff,
 User Rank: Author
3/28/2018 | 9:00:13 PM
Re: Victim Shaming
It is important to note that most people who provide their privacy information to a third party are doing so for the purpose of receiving a service, or participating in a collective social forum. Many organizations cannot provide the service to an individual without collecting personal information. For instance, any transaction that involves a credit card payment. In that regard, there is no basis for "victim sharing." The individual has done nothing more than picked a service provider. Unfortunately, sometimes these types of data sets are compromised. 

Now, if you are referring to an independent vendor with a data set that includes privacy data, many of them are already very sensitive to the reputation risk associated with a data breach. In a breach, they too are a victim, noting that a compromise may involve a criminal act. However, not all breach scenarios involve criminal acts. There is a long history of data disclosures that are a result of simple human error - an access control mechanism was not implemented properly, and the ability to freely discover and access the data was both possible, and actually occurred. 

In summary, victim shaming is not going to make the landscape better. Problems are solved through addressing the root cause, and not symptomatic attributes. However, thank you for your thoughts. As the author of the article, I hope that you benefited from the perspective presented.

 
Dr.T
Dr.T,
 User Rank: Ninja
3/28/2018 | 7:09:35 PM
Re: Victim Shaming
“Yes, we need to do more to protect the data and privacy.” I agree. There is a shared responsibility everybody needs to pay attention and do their parts, and then there is criminals we need to go after.
Dr.T
Dr.T,
 User Rank: Ninja
3/28/2018 | 7:06:21 PM
Re: Victim Shaming
“Easier to go after the victim and blame them for what they could have/should have/might have done differently. ” This make sense, at the same time when it comes to security it is everybody’s responsibility.
Dr.T
Dr.T,
 User Rank: Ninja
3/28/2018 | 7:03:59 PM
Re: Victim Shaming
“Maybe it's time that we return to criminalizing the criminal instead of the victim” This is a good point to raise. Holding the criminal responsible is the way to go.
Dr.T
Dr.T,
 User Rank: Ninja
3/28/2018 | 7:02:29 PM
Standard
“They contend a federal standard would simplify compliance and make the threshold for disclosure clear to businesses and consumers alike.” This may be good to get early notification when there is a breach, if you remember yahoo, they reported it 4 years later.
Dr.T
Dr.T,
 User Rank: Ninja
3/28/2018 | 6:59:10 PM
Two seconds
“In the US, an identity is compromised every two seconds. ” This is really very scary to hear. There has to be a better way to manage security of our indentity
Dr.T
Dr.T,
 User Rank: Ninja
3/28/2018 | 6:55:43 PM
PII
“We have healthcare laws that address privacy, but only when the privacy data is protected health information, a form of PII.” PII may apply outside of healthcare as far as I understood, for healthcare there is PHI protection.
Page 1 / 2   >   >>


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
The 10 Most Impactful Types of Vulnerabilities for Enterprises Today
Managing system vulnerabilities is one of the old est - and most frustrating - security challenges that enterprise defenders face. Every software application and hardware device ships with intrinsic flaws - flaws that, if critical enough, attackers can exploit from anywhere in the world. It's crucial that defenders take stock of what areas of the tech stack have the most emerging, and critical, vulnerabilities they must manage. It's not just zero day vulnerabilities. Consider that CISA's Known Exploited Vulnerabilities (KEV) catalog lists vulnerabilitlies in widely used applications that are "actively exploited," and most of them are flaws that were discovered several years ago and have been fixed. There are also emerging vulnerabilities in 5G networks, cloud infrastructure, Edge applications, and firmwares to consider.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-1142
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use URL decoding to retrieve system files, credentials, and bypass authentication resulting in privilege escalation.
CVE-2023-1143
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use Lua scripts, which could allow an attacker to remotely execute arbitrary code.
CVE-2023-1144
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 contains an improper access control vulnerability in which an attacker can use the Device-Gateway service and bypass authorization, which could result in privilege escalation.
CVE-2023-1145
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 are affected by a deserialization vulnerability targeting the Device-DataCollect service, which could allow deserialization of requests prior to authentication, resulting in remote code execution.
CVE-2023-1655
PUBLISHED: 2023-03-27
Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.4.0.