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
How Not To Respond To A DDoS Attack
Newest First  |  Oldest First  |  Threaded View
Kelly Jackson Higgins
Kelly Jackson Higgins,
 User Rank: Strategist
6/17/2014 | 2:09:31 PM
Re: Defending Against a DDoS Attack
That would definitely make things a lot more interesting!
RetiredUser
RetiredUser,
 User Rank: Ninja
6/17/2014 | 2:07:35 PM
Re: Defending Against a DDoS Attack
 @Kelly Jackson Higgins

Yes, it is controversial.  I wouldn't even get into the difficulties of how that could be navigated legally.  I do support it, still, but understand the risks and complexities involved.  If only we could get government-sanctioned teams that could "turn the tables" under one large umbrella that would represent businesses and the interests of everyday citizens, but with the ability to act immediately without the red tape...
Whoopty
Whoopty,
 User Rank: Ninja
6/17/2014 | 12:20:14 PM
Re: Defending Against a DDoS Attack
Indeed, especially when you consider that most members of a botnet that's performing a DDOS attack have no idea they've been recruited, since malware has made them an unwitting member. 
Randy Naramore
Randy Naramore,
 User Rank: Ninja
6/17/2014 | 10:08:03 AM
Re: Defending Against a DDoS Attack
Good article, should always plan and test for the worst case scenario. DDOS planning is something that should be tested periodically. 
Kelly Jackson Higgins
Kelly Jackson Higgins,
 User Rank: Strategist
6/17/2014 | 9:24:01 AM
Re: Defending Against a DDoS Attack
Turning the tables on DDoSers sounds like the ultimate revenge. But it's really not something most organizations can/should do. Even security researchers have had to tread carefully when using this tactic. Like any offensive security approach, it's controversial and comes with some risks of its own. 
andrewboon2739
andrewboon2739,
 User Rank: Apprentice
6/17/2014 | 8:10:17 AM
Two common Web application attacks illustrate security concerns
The issue of cybersecurity is a major and growing concern for the business community. Its time organizations adopt stronger measures to check security breaches, spotting and mitigating cyber crime and other security related issues will be of utmost importance in a digitally connected world. I work with McGladrey and there's a whitepaper on our website that offers useful information on the common security concerns for businesses and ways to mitigate them. "Two common Web application attacks illustrate security concerns"   @   http://bit.ly/1c0f35M
RetiredUser
RetiredUser,
 User Rank: Ninja
6/17/2014 | 1:16:01 AM
Defending Against a DDoS Attack
Brings to mind your article from a while back DIY: Defending Against a DDoS Attack.  While I agree most enterprises need the help of expert companies to fend off DDoS attacks, I very much support the idea of striking back as well, and preferably bringing the attackers themselves down.  The stronger security teams in the enterprise become, the harder it is for cyber criminals to gain a foothold.  Hacktivists can help in this regard by retaliating on behalf of small businesses that otherwise can't stand a chance against these attacks. 


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.