<?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: DNS big text threat seems to bypass security rule in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/dns-big-text-threat-seems-to-bypass-security-rule/m-p/67110#M39428</link>
    <description>&lt;P&gt;Because it's DNS answer. Session initiator (DNS query) is probably one of your DNS servers so session is allowed and response can come back.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 22 Oct 2015 13:43:51 GMT</pubDate>
    <dc:creator>santonic</dc:creator>
    <dc:date>2015-10-22T13:43:51Z</dc:date>
    <item>
      <title>DNS big text threat seems to bypass security rule</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-big-text-threat-seems-to-bypass-security-rule/m-p/67096#M39426</link>
      <description>&lt;P&gt;I have a strange circumstance here, I think. I've received several threats in my threat log for "DNS Answer Big TXT Record Response Anomaly" Threat ID &lt;LABEL id="ext-gen2191" class="x-form-item-label" style="width: 80px;" for="ext-comp-2073"&gt;&lt;/LABEL&gt;31580 (not sure if that's relevant or not, it just seems an odd similarity)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So yesterday I had a few instances of this threat from a particular IP. My usual response (like it or not) when I see threats that come through with an action of "allow" or "alert" and I see multiple atempts from the same source IP (and I can't refute the assumption that this is a threat and not mis-classified normal traffic) is to add the IP as a recognized address and put it in a group for "blocked IP's." I have a security rule that says to deny from the source in the "blocked IP's" group and coming in on the L3-untrust zone (which is where this threat comes in) and to any destination on L3-trust zone (which is the destination on these threats). So that's my setup, and I went to add this IP that got through yesterday to the block list, but it's already in the block list. Busy day yesterday, so I forgot about it - if the same IP tries again, I'll see it the next day.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So today I have the exact same circumstance with a different IP. So it seems that I have these threats that are for some reason ignoring the first security rule I have in place and making it through to the threat processor, where they're getting "allowed" or "alerted"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thoughts on how this could be happening? my only other thought at this point is to try rebooting the firewall, but that seems far-fetched - why are all my other security rules working, and it's just these two IP's with this common threat that's getting through?&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2015 13:29:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-big-text-threat-seems-to-bypass-security-rule/m-p/67096#M39426</guid>
      <dc:creator>mkeller</dc:creator>
      <dc:date>2015-10-22T13:29:30Z</dc:date>
    </item>
    <item>
      <title>Re: DNS big text threat seems to bypass security rule</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-big-text-threat-seems-to-bypass-security-rule/m-p/67110#M39428</link>
      <description>&lt;P&gt;Because it's DNS answer. Session initiator (DNS query) is probably one of your DNS servers so session is allowed and response can come back.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2015 13:43:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-big-text-threat-seems-to-bypass-security-rule/m-p/67110#M39428</guid>
      <dc:creator>santonic</dc:creator>
      <dc:date>2015-10-22T13:43:51Z</dc:date>
    </item>
  </channel>
</rss>

