<?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: IDS PIX shunning in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ids-pix-shunning/m-p/156134#M609512</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You don't really configure the PIX, you just need to configure the sensor (via CSPM) to do blocking.  When the sensor detects a signature that is set up for blocking, it will telnet/SSH to the PIX and add a "shun" command that will drop all packets from the signature source.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/ismg/policy/ver23i/idsguide/ch03.htm#57747" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/ismg/policy/ver23i/idsguide/ch03.htm#57747&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Noe that for a PIX, there is no interface to apply this to, the shun get's applied to all incoming packets on all interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You then need to modify the particular signature so that one of it's Actions is to block.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/ismg/policy/ver23i/idsguide/ch05.htm#xtocid263714" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/ismg/policy/ver23i/idsguide/ch05.htm#xtocid263714&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BTW, I would seriously consider upgrading your signatures, you are about 25 signatures releases and 4 service packs behind now.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Feb 2003 01:05:50 GMT</pubDate>
    <dc:creator>gfullage</dc:creator>
    <dc:date>2003-02-14T01:05:50Z</dc:date>
    <item>
      <title>IDS PIX shunning</title>
      <link>https://community.cisco.com/t5/network-security/ids-pix-shunning/m-p/156133#M609510</link>
      <description>&lt;P&gt;How do i configure the PIX for IP blocking when my IDS detect an anomalous activity?  &lt;/P&gt;&lt;P&gt;My IDS version is 3.0(1)S4&lt;/P&gt;&lt;P&gt;I have a CSPM version 2.3.3i&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:33:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-pix-shunning/m-p/156133#M609510</guid>
      <dc:creator>rolalo</dc:creator>
      <dc:date>2020-02-21T06:33:25Z</dc:date>
    </item>
    <item>
      <title>Re: IDS PIX shunning</title>
      <link>https://community.cisco.com/t5/network-security/ids-pix-shunning/m-p/156134#M609512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You don't really configure the PIX, you just need to configure the sensor (via CSPM) to do blocking.  When the sensor detects a signature that is set up for blocking, it will telnet/SSH to the PIX and add a "shun" command that will drop all packets from the signature source.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/ismg/policy/ver23i/idsguide/ch03.htm#57747" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/ismg/policy/ver23i/idsguide/ch03.htm#57747&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Noe that for a PIX, there is no interface to apply this to, the shun get's applied to all incoming packets on all interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You then need to modify the particular signature so that one of it's Actions is to block.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/ismg/policy/ver23i/idsguide/ch05.htm#xtocid263714" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/ismg/policy/ver23i/idsguide/ch05.htm#xtocid263714&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BTW, I would seriously consider upgrading your signatures, you are about 25 signatures releases and 4 service packs behind now.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Feb 2003 01:05:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-pix-shunning/m-p/156134#M609512</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2003-02-14T01:05:50Z</dc:date>
    </item>
  </channel>
</rss>

