Outsourcing DDOS

Sat Oct 22 23:24:20 UTC 2011

Good points Steven.  I'd suggest a deep dive on the technologies implemented by the vendor today as times and attack methods have evolved. Many attacks today are not Volumetric or easily detected or mitigated by traditional methods.

Stefan Fouant <sfouant at shortestpathfirst.net> wrote:

>Although a bit dated, I did a pretty exhaustive comparison of offerings 
>from AT&T, Verizon, Prolexic, and a few others a while back.
>
>Don't forget there is also the go-it-yourself approach which is always a 
>fun option, guaranteed to keep you up at night and give you a few 
>additional gray hairs...
>
>Let me know if you're interested in the slides...
>
>Stefan Fouant
>JNCIE-SEC, JNCIE-SP, JNCIE-ER, JNCI
>Technical Trainer, Juniper Networks
>
>Follow us on Twitter @JuniperEducate
>
>On 10/20/2011 4:43 PM, Hank Nussbacher wrote:
>> At 09:13 19/10/2011 -0400, samuel.cunningham at wellsfargo.com wrote:
>>> We are considering using Prolexic to 'defend' our Internet-facing
>>> network from DDOS attacks. Anyone have any known issues or word of
>>> warnings before we proceed?
>>
>> Things to check:
>>
>> - DDOS service caps
>> - outage remedy credits
>> - service trial period
>> - monitoring - you will want some external mutually agreeable monitoring
>> service like gomez/compuware. Who pays for it?
>>
>> Regards,
>> Hank
>>
>>
>>
>>> Chris Cunningham
>>> Network Engineering
>>> Secure Connectivity
>>> 704-427-3557 (Desk)
>>> 704-701-6924 (Cell)
>>> Samuel.Cunningham at Wellsfargo.com<mailto:Samuel.cunningham at wellsfargo.com>
>>> [X]
>>>
>>> This e-mail, including any attached files, may contain confidential
>>> and privileged information for the sole use of the intended recipient.
>>> Any review, use, distribution, or disclosure by others is strictly
>>> prohibited. If you are not the intended recipient (or authorized to
>>> receive information for the intended recipient), please contact the
>>> sender by reply e-mail and delete all copies of this message.
>>
>>
>
>