<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DTLS Amplification DDoS Attack on Citrix ADC and Citrix Gateway in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DTLS-Amplification-DDoS-Attack-on-Citrix-ADC-and-Citrix-Gateway/m-p/107574#M56216</link>
    <description>&lt;P&gt;Geo policy/blocking might also help depending on the specific origins of what you're seeing.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Jan 2021 09:04:27 GMT</pubDate>
    <dc:creator>Chris_Atkinson</dc:creator>
    <dc:date>2021-01-12T09:04:27Z</dc:date>
    <item>
      <title>DTLS Amplification DDoS Attack on Citrix ADC and Citrix Gateway</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DTLS-Amplification-DDoS-Attack-on-Citrix-ADC-and-Citrix-Gateway/m-p/107295#M56214</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I'm sure you're all aware of this attack by now, more details can be found on Citrix webpage: &lt;A href="https://support.citrix.com/article/CTX289674" target="_blank"&gt;https://support.citrix.com/article/CTX289674&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have upgraded our environments and enabled "Hello Verify Request", but even so, there amount of actors attempting to abuse this is filling our connection tables and causing issues for our legitime traffic.&lt;/P&gt;
&lt;P&gt;Disabling DTLS altogther seems like the best solution so far, as they give up faster, but we still see connection spikes from time to time and would like to know how we can handle it better.&lt;/P&gt;
&lt;P&gt;Are there any IPS signatures, or other ways to throttle the udp/443 traffic from the threat actors abusing this?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Jan 2021 13:17:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DTLS-Amplification-DDoS-Attack-on-Citrix-ADC-and-Citrix-Gateway/m-p/107295#M56214</guid>
      <dc:creator>Sigbjorn</dc:creator>
      <dc:date>2021-01-08T13:17:17Z</dc:date>
    </item>
    <item>
      <title>Re: DTLS Amplification DDoS Attack on Citrix ADC and Citrix Gateway</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DTLS-Amplification-DDoS-Attack-on-Citrix-ADC-and-Citrix-Gateway/m-p/107556#M56215</link>
      <description>&lt;P&gt;You can definitely rate limit these inbound connections using fw samp/sam erdos or similar.&lt;BR /&gt;Other than that, I'm not aware of a specific action you can take here.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jan 2021 02:17:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DTLS-Amplification-DDoS-Attack-on-Citrix-ADC-and-Citrix-Gateway/m-p/107556#M56215</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2021-01-12T02:17:58Z</dc:date>
    </item>
    <item>
      <title>Re: DTLS Amplification DDoS Attack on Citrix ADC and Citrix Gateway</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DTLS-Amplification-DDoS-Attack-on-Citrix-ADC-and-Citrix-Gateway/m-p/107574#M56216</link>
      <description>&lt;P&gt;Geo policy/blocking might also help depending on the specific origins of what you're seeing.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jan 2021 09:04:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DTLS-Amplification-DDoS-Attack-on-Citrix-ADC-and-Citrix-Gateway/m-p/107574#M56216</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2021-01-12T09:04:27Z</dc:date>
    </item>
  </channel>
</rss>

