Will Cloud Signaling Contain DDoS Attacks?

Arbor Networks' "Bat-signal" for distributed denial of service attacks culls your network service provider's resources to help stop it.

Is a distributed denial of service (DDoS) attack crippling your corporate network? Then signal your upstream service provider so it can filter out the attack using carrier-grade equipment.

That's the premise of "cloud signaling," which is a set of technical capabilities and mitigation strategies offered by network security vendor Arbor Networks. Announced in May, Arbor released the first related product in August, named Pravail, which it bills as an availability protection system.


More Security Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

A business that's already purchased DDoS defenses can typically mitigate small attacks, but those that flood the network pipe, or target the application level--including intrusion prevention systems and firewalls--may be much more difficult to stop. That's where cloud signaling comes in. "You can either set it to automatically signal your upstream provider, kind of like a Bat-signal--help me--and it will send help, sending all of the [attack] parameters" to the carrier, said Rob Malan, CTO of Arbor Networks, in an interview. Alternately, Pravail users can trigger the signaling manually.

[Businesses aren't ready to defend against the rising tide of sophisticated cyber attacks. Learn more: Advanced Threats Touch Two-Thirds Of Enterprises.]

Calling in the service provider brings carrier-grade packet-scrubbing power to bear on attacks, which means the attacks can be more easily eradicated by the service provider. "So maybe you've got one to 10 gigs of mitigation protection at the enterprise edge, but you have hundreds of gigs of mitigation protection at the carrier," said Malan.

He said the idea for cloud signaling arose during a late-night Denny's discussion he had with his Arbor co-founder, Farnam Jahanian, who now heads the National Science Foundation's computer & information science & engineering directorate. They hit upon the idea of "being able to hit a 'big red button' at the target of the DDoS attack, and signal all the way back upstream to the sources of the attack, automatically protecting the target."

But that discussion happened in 1999; what took 11 years for the idea to become reality? "While we always wanted to do this, you can't make a living selling a promise that it will be great in 10 years. So we needed to get a large install base," said Malan.

"The first major problem was getting the tool into all the carriers' hands so they could do coordinated troubleshooting. The second was getting it into the hands of the enterprise, so they could do coordinated troubleshooting back to the carrier. Once you have that infrastructure covered, you can hook them all together, all the way back to the carrier," he said.

One related step along this path was the Fingerprint Sharing Alliance, launched in 2002 as a way for network providers to share information with each other about large-scale attacks in progress. From there, it wasn't a big leap to having downstream customers share information about attacks that targeted their specific infrastructure.

Recent changes in DDoS attacks have also created an impetus for such information sharing. "The attacks changed in the last couple of years," said Malan. "Some kinds of attacks, you have to see the packets in line, and the only scalable way to do that is at the enterprise or data center edge--you can't sit up in the cloud and look at every packet, it's too packet-intensive; you've got to distribute that to the enterprise."

But when those defenses located at the edge of a business' infrastructure detect an attack, they can't always stop it. Notably, research from Arbor has found that the average DDoS attack bandwidth increased by 102% during 2010, and rose by 1,000% from 2005 to 2010.

When attackers do attempt to DDoS a business, it typically wouldn't take a data center operator long to pick up the phone and call their carrier, seeking a way to mitigate the attack. But with Pravail, said Malan, the process can be entirely automated, and attack signatures passed upstream at the first hint of trouble. That increases the chance that not only will the attack get quickly blocked, but also that the business won't even see an outage.

User names and passwords are no longer sufficient authentication. Security requirements and regulatory mandates are putting pressure on business to adopt strong, multifactor authentication methods. In this Tech Center report, we explain how to weigh cost vs. risk to select the Web authentication method for your high-risk applications. Download it now. (Free with registration.)

Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links