Endpoint

4/15/2016
10:00 AM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail
50%
50%

How To Prepare For A DDoS Attack: 10 Steps

Like a hurricane or a flood, a DDoS is a crisis. Follow these 10 steps to prepare for an attack before it hits.
Previous
1 of 11
Next

Image Credit: Can Stock Photo

Image Credit: Can Stock Photo

Distributed denial of service (DDoS) attacks are scary. In a matter of minutes, they can shut down a network, service or website, costing companies millions of dollars.

A recent study by Corero Network Security found that while 34 percent of IT managers surveyed cited lost revenues as the most damaging consequence of a DDoS. Nearly half -- or 45 percent -- say loss of customer trust and confidence is their greatest concern.

When they first came on the scene 20 years ago, a DDoS -- which is when a large network of botnets overwhelm another system’s connection causing it to deny service to legitimate traffic – even threatened to take down the Internet itself.

That’s ancient history. Over time, vendors and service providers have developed products that help IT staffs better cope with the threat of a DDoS. But they come in waves and over the past year there has been an uptick in DDoS attacks.

“There have always been various waves of DDoS attacks, and we saw one toward the end of 2015,” says Barry Greene, CTO of Palo Alto-based GetIT, or Green Energy Technology & Infocommunications Technology.

Greene says that although we are currently experiencing a bit of a lull, now’s a good time to prepare for the next wave. He recently authored a white paper on preparing for a DDoS and spent some time talking with Dark Reading about strategies for defending against DDoS attacks. 

“Think of a DDoS as a crisis much like a hurricane or a flood,” Greene says. “You wouldn’t want to start preparing for a hurricane on the day of the event. The same holds true for a DDoS.”

 

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio

Previous
1 of 11
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
MatsS846
100%
0%
MatsS846,
User Rank: Apprentice
4/15/2016 | 4:25:33 PM
11FU
11 pageloads to read one text?

ELEVEN pages?


Yeah...keep it!
LordC623
100%
0%
LordC623,
User Rank: Strategist
4/15/2016 | 10:48:23 AM
No thanks
Oh, interesting story let's check this out.

 

*sees 11 image slide show*

 

*closes browser tab*
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Australian Teen Hacked Apple Network
Dark Reading Staff 8/17/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-2765
PUBLISHED: 2018-08-20
pyro before 3.15 unsafely handles pid files in temporary directory locations and opening the pid file as root. An attacker can use this flaw to overwrite arbitrary files via symlinks.
CVE-2018-15594
PUBLISHED: 2018-08-20
arch/x86/kernel/paravirt.c in the Linux kernel before 4.18.1 mishandles certain indirect calls, which makes it easier for attackers to conduct Spectre-v2 attacks against paravirtual guests.
CVE-2018-15572
PUBLISHED: 2018-08-20
The spectre_v2_select_mitigation function in arch/x86/kernel/cpu/bugs.c in the Linux kernel before 4.18.1 does not always fill RSB upon a context switch, which makes it easier for attackers to conduct userspace-userspace spectreRSB attacks.
CVE-2018-15573
PUBLISHED: 2018-08-20
** DISPUTED ** An issue was discovered in Reprise License Manager (RLM) through 12.2BL2. Attackers can use the web interface to read and write data to any file on disk (as long as rlm.exe has access to it) via /goform/edit_lf_process with file content in the lfdata parameter and a pathname in the lf...
CVE-2018-15574
PUBLISHED: 2018-08-20
** DISPUTED ** An issue was discovered in the license editor in Reprise License Manager (RLM) through 12.2BL2. It is a cross-site scripting vulnerability in the /goform/edit_lf_get_data lf parameter via GET or POST. NOTE: the vendor has stated "We do not consider this a vulnerability."