{"id":11300,"date":"2014-03-19T12:41:10","date_gmt":"2014-03-19T12:41:10","guid":{"rendered":"http:\/\/tricks-collections.com\/?p=11300"},"modified":"2014-04-08T14:03:31","modified_gmt":"2014-04-08T14:03:31","slug":"application-layer-ddos-new-weapon-of-choice","status":"publish","type":"post","link":"http:\/\/tricks-collections.com\/application-layer-ddos-new-weapon-of-choice\/","title":{"rendered":"Application-Layer DDoS: New Weapon of Choice"},"content":{"rendered":"
The sheer variety of online threats today in the cyber landscape can be mind-boggling. This article will address one of the more pressing issues for online businesses–Application Layer DDoS\u2014what it is, and how to protect against it.<\/p>
As opposed to large-scale, flashy volumetric attacks, Application Layer Distributed Denial of Service (DDoS) works in more subtle ways to disrupt websites. Instead of overwhelming a target network with floods of information, Application Layer DDoS attacks are smaller and spread over many connections.<\/p>
<\/p>
Hackers start by setting up several TCP connections with a target server. This way, the target sees the bot-generated requests as \u2018legitimate,\u2019 making them even more difficult to detect. In fact, many Application Layer DDoS are executed without the victims even realizing they are getting hit. They may write off the disruption as a connectivity issue. Businesses may believe they are protected by their traditional security measures like firewall or load balancers, but these are ineffective against \u2018legitimate\u2019 requests.<\/p>
As the name suggests, these attacks aim at applications, like HTTP, by taxing a server\u2019s memory resources. Then the attack may move on to other applications, slowly bringing down the site piece by piece. Clearly, security in these cases requires more than just a big network.<\/p>
Back in October, Incapsula, a leading security firm, had a drawn out battle against one of the most sophisticated DDoS attacks<\/a> of all time. It began shortly after one of the target company\u2019s partners left on bad terms, leading the firm to believe he was at the bottom of the attack.<\/p> The first tremor came from a short-lived SYN flood, a relatively simple threat to handle. Next came a head-on HTTP flood at a heavy 10M requests\/second. This alone would be enough to take down most servers, but it could not trick Incapsula\u2019s Client Classification system.<\/p> But then the hackers got serious. They began hitting other applications like AJAX, and even Incapsula itself. They came with bots able to capture session cookies, bots with human-like user-agent, and bots with human behavior. Incapsula countered with CAPTCHA challenges. On and on the attack rained down, for over 7 weeks. Fortunately the target was prepared with 3rd<\/sup> party security, but most companies do not have the wherewithal to arm themselves with proper defenses.<\/p>