Linked by David Adams on Tue 28th Jun 2011 15:35 UTC, submitted by HAL2001
Privacy, Security, Encryption In an unexpected move for a security company, SecurEnvoy today said that cyber break-ins and advanced malware incidents, such as the recent DDoS attack by LulzSec, should actually be welcomed and their initiators applauded. The company's CTO Andy Kemshall said: "I firmly believe that the media attention LulzSec’s DDoS attack has recently received is deserving. It’s thanks to these guys, who’re exposing the blase attitudes of government and businesses without any personal financial gain, that will make a difference in the long term to the security being put in place to protect our own personal data!"
Permalink for comment 479272
To read all comments associated with this story, please click here.
Member since:


"I'd suggest that DDoS vulnerability is indeed a security issue. Security is not just concerned with protecting the information in that one box. It is also concerned with protecting the system resources for legitimate use. A denial of service removes resources from legitimate users."

This is all true, however you've overlooked a crucial element: in a well designed large scale DDoS attack, the victim doesn't know the attackers from legitimate customers.

"If your network gets flooded out by packets, you have a security mechanism failing to filter packets properly."

Two problems:
1. A filter is useless when the attacker's botnet has more bandwidth than you. Even an OC3 (which was considered large enough for my whole university) is easily saturated by a few hundred broadband users.

2. What kind of filter do you use? If you detect excessive bandwidth on an IP you can block it, but it may or may not be legitimate. Consider a bunch of mobile users being a proxy/nat router, you're filter could inadvertently block all of them.

"If your software gets crashed into a denial of service condition, you have an exploitable vulnerability in the code that needs to be addressed."

Well granted, the software should never crash. In the worse case, a busy server should start returning something like error 500 in http-speak.

"If your website takes down your webserver due to resource exhaustion through a designed website function, you have site code that needs to be addressed."

You're totally oversimplifying the issue to imply that code is at fault. Assuming you actually have enough bandwidth in the first place (which isn't likely for most small/medium businesses), then there are other local bottlenecks which will require infrastructure upgrades to eliminate. Databases quickly become saturated. Even ordinary web servers can start thrashing if the attackers deliberately request pieces of material which are unlikely to be cached. This causes random disks seeks well in excess of normal load. A typical disk seek is 5ms, if the attacker successfully requests an uncached file each time, then both normal users and attackers will reach a limit of 200 requests/sec.

"The information systems are a business resource that need to be protected in addition to the information those systems house. Denial of service demonstrates an exploitable flaw in the security of those systems."

Hopefully I've gotten my point across that being vulnerable to DDoS doesn't imply a security vulnerability. As Soulbender stated already "Availability != security."

I'd gladly discuss any usable ideas you have, but DDoS isn't as easy to solve as you make it out.

Reply Parent Score: 2