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
DDoS And The Internet's Liability Problem
Oldest First  |  Newest First  |  Threaded View
Page 1 / 2   >   >>
Thomas Claburn
Thomas Claburn,
 User Rank: Ninja
11/18/2015 | 4:25:04 PM
Make it so
I agree. So what needs to happen to make this work?
PaulV378
PaulV378,
 User Rank: Strategist
11/19/2015 | 4:51:08 AM
Re: Make it so
my plan of the moment is to draft some proposed amendments to the computer fraud and abuse act (CFAA) and then go to DC and try to interest the US congress in this simple solution to the very vexing problem.
victorhotel
victorhotel,
 User Rank: Strategist
11/19/2015 | 2:17:13 PM
Re: Make it so
A good proposal, but will it fly?

Liability for insecure software has been proposed for well over decade, by Schneier and a host of others.  Nothing to show for it even though the law should be easy to formulate, as there is a direct contractual relationship between the victim (buyer of software) and the software vendor.  Of course, we do have liability written into individual contracts between corporate buyers and vendors.

Liability for DDoS is more difficult, as the victim is not the buyer of the defective product.  Then again, precedence does exist in tort law - if a car malfunctions and injures a pedestrian, the victim may have grounds to sue the car manufacturer.

Rather than lobbying Congress, your time may be better spent lobbying telecom regulators. They could fix the problem, partially, by mandating secure networks and servers in at least telecom providers and ISPs.  To be effective, the regulators would need to audit the providers.  (Do we need another PCI-DSS type audit scheme?)

How we fix the insecure IoT from being a party to DDoS I don't know.  Consumers don't care unless privacy or finances are at stake, so the politicians will certainly not care.
wcbonner
wcbonner,
 User Rank: Apprentice
11/19/2015 | 3:37:40 PM
DDoS Botnets
A growing trend in DDoS botnets is to use commercial cloud services and fresh, dedicated machines. Stolen credit card information is used to purchase the compute resources, and thousands of machines can be started up and dedicated to an attack before the fruadulent use has been detected.

This doesn't rely on existing weaknesses in open protocols, and new legislation is not going to fix things.

Wim.
PaulV378
PaulV378,
 User Rank: Strategist
11/21/2015 | 1:52:31 AM
Re: DDoS Botnets
those cloud providers are helping to create public hazards. the shift i'm looking for in liability will allow a ddos victim to recover damages from a cloud provider who sold the vm to a ddos-for-hire gang.


not everything that can be done, should be done. it's time everybody creating software or networks for the internet got that lesson taught to them.
UldisS421
UldisS421,
 User Rank: Apprentice
11/22/2015 | 2:00:23 PM
Re: Make it so
Liability for insecure software would make it hard for open source. Not because someone might try suing, they cant do that. But because of people getting afraid of liabilities on them, not the software creators, thus making them choose propriatary software just to stay safe themselves.

Another aspect. Getting liabilities on the senders would mean sending legal notices etc. to thousands of them, many in faraway lands with lots of legal problems, like "it is not illegal in my country" to "we dont care" and just stretching the time.

So, I dont know if this idea would work in real life as it sounds in theory. Still many obstacles.
Dr.T
Dr.T,
 User Rank: Ninja
11/25/2015 | 11:08:27 AM
DDoS without vulnerability
DDoS without vulnerability

Nice article, enjoyed reading it. There can be a real successful DDoS attach without ant vulnerability, that is what it is always successful form of attack. 
Dr.T
Dr.T,
 User Rank: Ninja
11/25/2015 | 11:11:11 AM
Re: Make it so
Anything involving government these days obviously not working, you never know tough. :--)).
Dr.T
Dr.T,
 User Rank: Ninja
11/25/2015 | 11:13:58 AM
Re: Make it so
I agree, also public is not aware of this situation, unless there is public support nobody will move or touch anything.
Dr.T
Dr.T,
 User Rank: Ninja
11/25/2015 | 11:16:56 AM
Re: DDoS Botnets
Agree, once you have the impact does not matter how it happened, this is like using target's resources to attack target itself. :--)).
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.