<?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: PIX 7.0 inspect in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-7-0-inspect/m-p/744748#M1005346</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just a follow on question..  what would be the difference if once just modified the SQL behaviour in the global policy instead  .. with access lists..  etc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 11 May 2007 20:40:11 GMT</pubDate>
    <dc:creator>amcneish</dc:creator>
    <dc:date>2007-05-11T20:40:11Z</dc:date>
    <item>
      <title>PIX 7.0 inspect</title>
      <link>https://community.cisco.com/t5/network-security/pix-7-0-inspect/m-p/744746#M1005344</link>
      <description>&lt;P&gt;As you are all aware, by default the 'inspect sqlnet' feature is switched on under the global policy map on PIX v7 firewalls. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to keep the 'inspect sqlnet' feature on at the global policy level, but turn it off for traffic travelling between a specific source/destination network using access lists. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this possible? If so, could someone please provide some guidance on how to do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:08:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-7-0-inspect/m-p/744746#M1005344</guid>
      <dc:creator>itrequest</dc:creator>
      <dc:date>2019-03-11T10:08:47Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 7.0 inspect</title>
      <link>https://community.cisco.com/t5/network-security/pix-7-0-inspect/m-p/744747#M1005345</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can achieve that by configuring a layer3/4 policy and bind it to an interface.&lt;/P&gt;&lt;P&gt;Policy binded to the interface will take precedence than the gloabal default inspection policy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a look at this URL for more details.&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/ps6120/products_configuration_guide_chapter09186a008063706a.html" target="_blank"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_guide_chapter09186a008063706a.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example: You can configure as follows&lt;/P&gt;&lt;P&gt;Define a acl, to exclude the traffic between source and destination network and then permit everything else.&lt;/P&gt;&lt;P&gt;Create class map and match this ACL in it.&lt;/P&gt;&lt;P&gt;Create a policy-map, call this class-map and perform inpsect sqlnet for the matching traffic in the class-map.&lt;/P&gt;&lt;P&gt;Bind this policy-map to the appropriate interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sample configuration&lt;/P&gt;&lt;P&gt;*********************&lt;/P&gt;&lt;P&gt;access-list sqlnettraffic deny ip &lt;SOURCE network=""&gt; &lt;MASK&gt; &lt;DESTINATION network=""&gt; &lt;MASK&gt;&lt;/MASK&gt;&lt;/DESTINATION&gt;&lt;/MASK&gt;&lt;/SOURCE&gt;&lt;/P&gt;&lt;P&gt;access-list sqlnettraffic permit ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map my-sqlnet-traffic&lt;/P&gt;&lt;P&gt;match access-list sqlnettraffic&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map my-sqlnet-policy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class my-sqlnet-traffic&lt;/P&gt;&lt;P&gt;inspect sqlnet&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service-policy my-sqlnet-policy interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This should help to acheive what you are looking.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-VJ&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 May 2007 05:00:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-7-0-inspect/m-p/744747#M1005345</guid>
      <dc:creator>vijayasankar</dc:creator>
      <dc:date>2007-05-04T05:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 7.0 inspect</title>
      <link>https://community.cisco.com/t5/network-security/pix-7-0-inspect/m-p/744748#M1005346</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just a follow on question..  what would be the difference if once just modified the SQL behaviour in the global policy instead  .. with access lists..  etc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 May 2007 20:40:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-7-0-inspect/m-p/744748#M1005346</guid>
      <dc:creator>amcneish</dc:creator>
      <dc:date>2007-05-11T20:40:11Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 7.0 inspect</title>
      <link>https://community.cisco.com/t5/network-security/pix-7-0-inspect/m-p/744749#M1005347</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That will affect for all the SQL traffic passing through the firewall.&lt;/P&gt;&lt;P&gt;What is your exact requirement? Why do you want to disable the SQL inspect feature.?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-VJ&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 May 2007 03:56:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-7-0-inspect/m-p/744749#M1005347</guid>
      <dc:creator>vijayasankar</dc:creator>
      <dc:date>2007-05-12T03:56:39Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 7.0 inspect</title>
      <link>https://community.cisco.com/t5/network-security/pix-7-0-inspect/m-p/744750#M1005348</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was interested in the original request to permit the remote site to perform the permit of the SQL traffic..  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If one only has an outside and an inside.. then using the global should be about the same as putting it on the outside interface..  (is that correct??)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If one has many DMZ's..  then one could put it on the outside.. or possibly one of the DMZ's (is that also correct??)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We recently upgraded for Pix 525's to ASA 5540's and we are new to the policy statements and answers to the above questions would go a long way to giving us insight.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andy &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 May 2007 11:30:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-7-0-inspect/m-p/744750#M1005348</guid>
      <dc:creator>amcneish</dc:creator>
      <dc:date>2007-05-12T11:30:21Z</dc:date>
    </item>
  </channel>
</rss>

