<?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 Just &amp;quot;trust&amp;quot; this specific in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firesight-drops-sql-well-known-traffic/m-p/2874008#M1030211</link>
    <description>&lt;P&gt;Just "trust" this specific traffic from IP and Port with a Access Control Rule. Then do further investigation of why the details this is happening.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;To be or Not to be&lt;/P&gt;</description>
    <pubDate>Fri, 15 Jul 2016 19:38:14 GMT</pubDate>
    <dc:creator>Ed Padilla Jr</dc:creator>
    <dc:date>2016-07-15T19:38:14Z</dc:date>
    <item>
      <title>Firesight drops SQL well known traffic</title>
      <link>https://community.cisco.com/t5/network-security/firesight-drops-sql-well-known-traffic/m-p/2874006#M1030206</link>
      <description>&lt;P&gt;Good day&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I just implement the Firesight solution, and I'm having issues because the Firesight drops SQL traffic. This traffic is well known and it´s part of our day to day traffic.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I would like to know how can I classify these traffic as well know o something to make the Firsight stop blocking the SQL traffic between our servers.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Stay pending for an answer, thanks a lot.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 13:03:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-drops-sql-well-known-traffic/m-p/2874006#M1030206</guid>
      <dc:creator>jfigueroa8</dc:creator>
      <dc:date>2019-03-12T13:03:30Z</dc:date>
    </item>
    <item>
      <title>Hi</title>
      <link>https://community.cisco.com/t5/network-security/firesight-drops-sql-well-known-traffic/m-p/2874007#M1030209</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;It might to due to any IPS rules. I would suggest enable logging on all the rules in access control policy where IPS policy is applied and in default rule as well.&lt;/P&gt;
&lt;P&gt;Then check the IPS events in analysis&amp;gt;Intrusion&amp;gt;events to see if any signature related to SQL is getting fired up.&lt;/P&gt;
&lt;P&gt;Based on which signature is causing it, further analysis can be done to see if its false positive or expected.&lt;/P&gt;
&lt;P&gt;Rate if helps.&lt;/P&gt;
&lt;P&gt;Yogesh&lt;/P&gt;</description>
      <pubDate>Sun, 03 Jul 2016 06:05:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-drops-sql-well-known-traffic/m-p/2874007#M1030209</guid>
      <dc:creator>yogdhanu</dc:creator>
      <dc:date>2016-07-03T06:05:32Z</dc:date>
    </item>
    <item>
      <title>Just "trust" this specific</title>
      <link>https://community.cisco.com/t5/network-security/firesight-drops-sql-well-known-traffic/m-p/2874008#M1030211</link>
      <description>&lt;P&gt;Just "trust" this specific traffic from IP and Port with a Access Control Rule. Then do further investigation of why the details this is happening.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;To be or Not to be&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jul 2016 19:38:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-drops-sql-well-known-traffic/m-p/2874008#M1030211</guid>
      <dc:creator>Ed Padilla Jr</dc:creator>
      <dc:date>2016-07-15T19:38:14Z</dc:date>
    </item>
  </channel>
</rss>

