<?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: Default Action for SQL Injection Attacks in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/238446#M452</link>
    <description>&lt;P&gt;Leaving medium to default allows so much bad stuff through.&lt;/P&gt;&lt;P&gt;I have even low severety set to reset-both with only 3 manual exeptions in there for traffic sourcinf from wan and handful more for internal traffic.&lt;/P&gt;</description>
    <pubDate>Fri, 02 Nov 2018 21:47:03 GMT</pubDate>
    <dc:creator>Raido_Rattameister</dc:creator>
    <dc:date>2018-11-02T21:47:03Z</dc:date>
    <item>
      <title>Default Action for SQL Injection Attacks</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/235975#M436</link>
      <description>&lt;P&gt;Following a sudden spike in SQLMap threats, I was looking at the default action for SQL injection threats and I noticed that it is is only an "alert" which seems odd for that kind of attack.&amp;nbsp; Has anyone looked deeper into this and/or changed the action and is there a reason for this not being a reset/drop action?&lt;/P&gt;</description>
      <pubDate>Thu, 18 Oct 2018 12:09:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/235975#M436</guid>
      <dc:creator>djr</dc:creator>
      <dc:date>2018-10-18T12:09:58Z</dc:date>
    </item>
    <item>
      <title>Re: Default Action for SQL Injection Attacks</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/236285#M439</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;While it is by deafult sert to alert, I found its best to block threats by Severity. As you can see by the picture, this Vulnerability Protection Profile, when added to a Policy, will reset the traffic so it cannot cause any damage:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image.png" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/17250i0125B124E1502F54/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;I hope this makes sense.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 19 Oct 2018 20:45:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/236285#M439</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2018-10-19T20:45:54Z</dc:date>
    </item>
    <item>
      <title>Re: Default Action for SQL Injection Attacks</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/236456#M440</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We already reset Critical and high, but use the PAN default below that so the difference between your profile and ours is really just that you extend that down to medium.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I see you also use the default action for low and info which is probably for the same reason we&amp;nbsp;do - some of the low and info threats are by default blocked which we found odd.&amp;nbsp; The PAN severity classification seems a bit weird which is why I was asking if anyone knew a reason why SQL injection was only an alert by default - if the detection is robust I would expect this to be a block by default.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 11:16:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/236456#M440</guid>
      <dc:creator>djr</dc:creator>
      <dc:date>2018-10-22T11:16:53Z</dc:date>
    </item>
    <item>
      <title>Re: Default Action for SQL Injection Attacks</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/236527#M441</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I would recommend setting the medium to also reset or block. There are going to be some exceptions, at least there are in my environemtn so I had to create special exception cases for them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 17:04:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/236527#M441</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2018-10-22T17:04:07Z</dc:date>
    </item>
    <item>
      <title>Re: Default Action for SQL Injection Attacks</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/236641#M442</link>
      <description>&lt;P&gt;OK thanks, I will look a bit closer at what other medium level threats we are seeing, with a view to doing that.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Many thanks&lt;/P&gt;</description>
      <pubDate>Tue, 23 Oct 2018 09:47:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/236641#M442</guid>
      <dc:creator>djr</dc:creator>
      <dc:date>2018-10-23T09:47:50Z</dc:date>
    </item>
    <item>
      <title>Re: Default Action for SQL Injection Attacks</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/238446#M452</link>
      <description>&lt;P&gt;Leaving medium to default allows so much bad stuff through.&lt;/P&gt;&lt;P&gt;I have even low severety set to reset-both with only 3 manual exeptions in there for traffic sourcinf from wan and handful more for internal traffic.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Nov 2018 21:47:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/238446#M452</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2018-11-02T21:47:03Z</dc:date>
    </item>
    <item>
      <title>Re: Default Action for SQL Injection Attacks</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/238564#M454</link>
      <description>&lt;P&gt;Thanks, I don't think I will go that far just yet, but have put medium to reset-both&amp;nbsp;for spyware and vulnerabilities.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Nov 2018 09:28:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/default-action-for-sql-injection-attacks/m-p/238564#M454</guid>
      <dc:creator>djr</dc:creator>
      <dc:date>2018-11-05T09:28:50Z</dc:date>
    </item>
  </channel>
</rss>

