<?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 IDS monitoring in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ids-monitoring/m-p/753757#M86782</link>
    <description>&lt;P&gt;We are seeing too many events in IDS/IPS. Is there a way to filter events and any one suggest best practice or top 20-30 events we should monitor ?&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 10:35:50 GMT</pubDate>
    <dc:creator>sagittarius</dc:creator>
    <dc:date>2019-03-10T10:35:50Z</dc:date>
    <item>
      <title>IDS monitoring</title>
      <link>https://community.cisco.com/t5/network-security/ids-monitoring/m-p/753757#M86782</link>
      <description>&lt;P&gt;We are seeing too many events in IDS/IPS. Is there a way to filter events and any one suggest best practice or top 20-30 events we should monitor ?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:35:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-monitoring/m-p/753757#M86782</guid>
      <dc:creator>sagittarius</dc:creator>
      <dc:date>2019-03-10T10:35:50Z</dc:date>
    </item>
    <item>
      <title>Re: IDS monitoring</title>
      <link>https://community.cisco.com/t5/network-security/ids-monitoring/m-p/753758#M86789</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First you need to fine tune your IDS/IPS. then ig you still have too many events showing off you need to use something like Cisco Monitoring and Response System, which would reduce the incidents you see.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 May 2007 07:10:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-monitoring/m-p/753758#M86789</guid>
      <dc:creator>rnaydenov</dc:creator>
      <dc:date>2007-05-05T07:10:56Z</dc:date>
    </item>
    <item>
      <title>Re: IDS monitoring</title>
      <link>https://community.cisco.com/t5/network-security/ids-monitoring/m-p/753759#M86793</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have spent years refining best practices for various customers that we manage. I can say from hard won experience that there is no magic bullet here and that data diving, sifting results, knowing your network all play vital roles in tuning your sensor(s).  It is something that occurs daily due to copious amounts of time performing in depth investigations. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 05 May 2007 20:25:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-monitoring/m-p/753759#M86793</guid>
      <dc:creator>attmidsteam</dc:creator>
      <dc:date>2007-05-05T20:25:04Z</dc:date>
    </item>
  </channel>
</rss>

