<?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: IPS Tuning and deployment in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ips-tuning-and-deployment/m-p/513248#M98786</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good question... We run with the default sigs activated by cisco, with exception to the "spyware" sigs which are turned off by default. We enable those and set the action to deny-packet. The issue that you will most likly run into is assigning actions to the sigs. By default all sigs are set to "produce alert". So the sensor will do nothing but tell you about the events. I encourage you to look into how the "Risk Ratings" and "Event action overides" work. If you can get that to work well then you do not have to assign actions to each sig. Instead you can tell the sensor that if the RR is between 92-100 add a "deny-packet" action.&lt;/P&gt;&lt;P&gt;It takes a while to get it all figured out.&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;M&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 31 Jan 2006 21:57:52 GMT</pubDate>
    <dc:creator>mkirbyii</dc:creator>
    <dc:date>2006-01-31T21:57:52Z</dc:date>
    <item>
      <title>IPS Tuning and deployment</title>
      <link>https://community.cisco.com/t5/network-security/ips-tuning-and-deployment/m-p/513247#M98785</link>
      <description>&lt;P&gt;I have a question for you who are already using the IPS signatures to block traffic.  When you started setting up these signatures what guidlines did you use?  I'm trying to develop a strategy for my company's activating of signatures. &lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:52:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-tuning-and-deployment/m-p/513247#M98785</guid>
      <dc:creator>dhopper82</dc:creator>
      <dc:date>2019-03-10T09:52:25Z</dc:date>
    </item>
    <item>
      <title>Re: IPS Tuning and deployment</title>
      <link>https://community.cisco.com/t5/network-security/ips-tuning-and-deployment/m-p/513248#M98786</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good question... We run with the default sigs activated by cisco, with exception to the "spyware" sigs which are turned off by default. We enable those and set the action to deny-packet. The issue that you will most likly run into is assigning actions to the sigs. By default all sigs are set to "produce alert". So the sensor will do nothing but tell you about the events. I encourage you to look into how the "Risk Ratings" and "Event action overides" work. If you can get that to work well then you do not have to assign actions to each sig. Instead you can tell the sensor that if the RR is between 92-100 add a "deny-packet" action.&lt;/P&gt;&lt;P&gt;It takes a while to get it all figured out.&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;M&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jan 2006 21:57:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-tuning-and-deployment/m-p/513248#M98786</guid>
      <dc:creator>mkirbyii</dc:creator>
      <dc:date>2006-01-31T21:57:52Z</dc:date>
    </item>
  </channel>
</rss>

