<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 26/09/2021 21:54, Mike Hammett
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:2060116959.4015.1632689676870.JavaMail.mhammett@Thunderfuck2">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<style type="text/css">p { margin: 0; }</style>
<div style="font-family: arial,helvetica,sans-serif; font-size:
10pt; color: #000000">
<div><br>
<div style="font-size: 13.3333px; background-color: rgb(255,
255, 255);">Are your garden variety DDoS mitigation
platforms or services equipped to handle DDoSes of VoIP
services? What nuances does one have to be cognizant of? A
WAF doesn't mean much to SIP, IAX2, RTP, etc.</div>
</div>
</div>
<br>
</blockquote>
<p><br>
</p>
<p>Without saying too much:<br>
</p>
<p><br>
</p>
<p>Seems to be a spate of DDOS against UK based voip providers at
the moment. For ransom. Don't pay.<br>
</p>
<p><br>
</p>
<p>One provider said that traditional approaches did not work.
They tried Voxility but just got false positives. There are
providers that do work. <br>
</p>
<p><br>
</p>
<p>But in the UK a lot of traffic goes over peers through internet
exchanges. So just swapping transit only half the problem.<br>
</p>
<p><br>
Prep wise:<br>
</p>
<p>So practice altering your IP advertisements, dropping and
bringing up peers. If you connect to route servers, practice
doing selective announcements. Try to get private interconnects
to your upstream telco providers. Get your network teams warmed
up for when it does happen. If you host with a cloud provider,
have a backup because if DDOS is coming from the same cloud .....<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Tim<br>
</p>
</body>
</html>