<?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: Pre IDS Implementation Check List for Sig Tuning in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pre-ids-implementation-check-list-for-sig-tuning/m-p/424423#M95091</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Knowing the behavior of your network and the applications that you are running is very important before signatures can be tuned. To avoid false positive alarms, you may have to observe your network for a while and tune the signatures until you get the desired result. From my experience, signature tuning is a contnious process and has to be monitored on a regular basis.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 Nov 2005 15:37:51 GMT</pubDate>
    <dc:creator>vkapoor5</dc:creator>
    <dc:date>2005-11-18T15:37:51Z</dc:date>
    <item>
      <title>Pre IDS Implementation Check List for Sig Tuning</title>
      <link>https://community.cisco.com/t5/network-security/pre-ids-implementation-check-list-for-sig-tuning/m-p/424422#M95089</link>
      <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDS signature tuning can get quite involved. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To make sure nothing important is overlooked, is there a Check List that can be used?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If not, what are some of the critical items that should be known beforehand?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A couple items are obvious e.g. type of OS's used and what servers must never be blocked.  But, I'm sure there's a whole list of things that should be considered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any feedback would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:45:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pre-ids-implementation-check-list-for-sig-tuning/m-p/424422#M95089</guid>
      <dc:creator>jimmi1015</dc:creator>
      <dc:date>2019-03-10T09:45:10Z</dc:date>
    </item>
    <item>
      <title>Re: Pre IDS Implementation Check List for Sig Tuning</title>
      <link>https://community.cisco.com/t5/network-security/pre-ids-implementation-check-list-for-sig-tuning/m-p/424423#M95091</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Knowing the behavior of your network and the applications that you are running is very important before signatures can be tuned. To avoid false positive alarms, you may have to observe your network for a while and tune the signatures until you get the desired result. From my experience, signature tuning is a contnious process and has to be monitored on a regular basis.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Nov 2005 15:37:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pre-ids-implementation-check-list-for-sig-tuning/m-p/424423#M95091</guid>
      <dc:creator>vkapoor5</dc:creator>
      <dc:date>2005-11-18T15:37:51Z</dc:date>
    </item>
  </channel>
</rss>

