<?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: Exclude network traffic from inspection in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/exclude-network-traffic-from-inspection/m-p/531463#M92583</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What kind if traffic you would like to exclude? By not using IPS filter (prevent oversubscribtion or cpu processing), you basically need filter it out at switch/router/firewall port level. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can create ACL to filter the unwanted traffic from hitting your IPS interface. But the setback is, you might filter passing through traffic/protocol that is needed by clients/hosts on the other side of the network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess this is where you really need the IPS filter. Basically, your IPS model selection should be suitable for the link &amp;amp; bandwidth that it need to monitor/filter to prevent oversubscription.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 22 Aug 2006 07:56:31 GMT</pubDate>
    <dc:creator>a.kiprawih</dc:creator>
    <dc:date>2006-08-22T07:56:31Z</dc:date>
    <item>
      <title>Exclude network traffic from inspection</title>
      <link>https://community.cisco.com/t5/network-security/exclude-network-traffic-from-inspection/m-p/531462#M92581</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;May I configure my IPS (this is an appliance), not to monitor, analyse some network traffic? I know I can create filters for events, but I want to prevent my box from oversubscribtion, so I don't want to monitor some type of traffic with it.&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:10:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/exclude-network-traffic-from-inspection/m-p/531462#M92581</guid>
      <dc:creator>teperjesi</dc:creator>
      <dc:date>2019-03-10T10:10:46Z</dc:date>
    </item>
    <item>
      <title>Re: Exclude network traffic from inspection</title>
      <link>https://community.cisco.com/t5/network-security/exclude-network-traffic-from-inspection/m-p/531463#M92583</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What kind if traffic you would like to exclude? By not using IPS filter (prevent oversubscribtion or cpu processing), you basically need filter it out at switch/router/firewall port level. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can create ACL to filter the unwanted traffic from hitting your IPS interface. But the setback is, you might filter passing through traffic/protocol that is needed by clients/hosts on the other side of the network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess this is where you really need the IPS filter. Basically, your IPS model selection should be suitable for the link &amp;amp; bandwidth that it need to monitor/filter to prevent oversubscription.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Aug 2006 07:56:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/exclude-network-traffic-from-inspection/m-p/531463#M92583</guid>
      <dc:creator>a.kiprawih</dc:creator>
      <dc:date>2006-08-22T07:56:31Z</dc:date>
    </item>
  </channel>
</rss>

