<?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 4.1 event filters in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ids-4-1-event-filters/m-p/331583#M96787</link>
    <description>&lt;P&gt;How would I configure an event filter for SIGID 4003 so that the source IP of A.B.C.D when the source port is 53 to any destination IP any destination port is filtered so it is excluded.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 09:20:22 GMT</pubDate>
    <dc:creator>5creedus</dc:creator>
    <dc:date>2019-03-10T09:20:22Z</dc:date>
    <item>
      <title>IDS 4.1 event filters</title>
      <link>https://community.cisco.com/t5/network-security/ids-4-1-event-filters/m-p/331583#M96787</link>
      <description>&lt;P&gt;How would I configure an event filter for SIGID 4003 so that the source IP of A.B.C.D when the source port is 53 to any destination IP any destination port is filtered so it is excluded.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:20:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-4-1-event-filters/m-p/331583#M96787</guid>
      <dc:creator>5creedus</dc:creator>
      <dc:date>2019-03-10T09:20:22Z</dc:date>
    </item>
    <item>
      <title>Re: IDS 4.1 event filters</title>
      <link>https://community.cisco.com/t5/network-security/ids-4-1-event-filters/m-p/331584#M96788</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I know how to do this using IDM. Here goes...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Access IDM via a browser (for example, &lt;A class="jive-link-custom" href="https://" target="_blank"&gt;https://&lt;/A&gt;&lt;IP of="" sensor=""&gt;)&lt;/IP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Use a username/password pair with administrative privileges&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) Left-click "Configuration" at the top of the page&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4) Left-click "Sensing Engine" when it appears&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5) Left-click "Event Filters" in the TOC menu when it appears&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6) Left-click "Add" at the bottom of the page&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;7) In the "SIGID" field, put 4003 (or whatever signature you wish to build the exclusion for)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":smiling_face_with_sunglasses:"&gt;😎&lt;/span&gt; In the "SubSig" field, place a Sub-signature number if required. Otherwise, leave it as a "*"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;9) Leave the "Exception" check box empty&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;10) In the "SrcAddrs" field, input the IP you wish to ignore (for example, A.B.C.D)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;11) In the "DstAddrs" field, leave the default "*", since you don't care which destination is involved for this particular source IP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;12) Left-click "Apply to Sensor"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;13) Confirm the details are correct in the resulting page and then left-click "Save Changes" icon near the top right-hand corner of the page&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;14) Enjoy the silence...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BTW, you cannot filter a specific source host based on a &lt;B&gt;specific source port&lt;/B&gt;. You'll have to choose to ignore all Nmap-like activity that may originate from your chosen source IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assuming that this is in fact a DNS server however, this is an acceptable risk to assume, since you would likely see other signs of compromise besides outbound Nmap scans in the event that someone owns your DNS server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps,&lt;/P&gt;&lt;P&gt;Alex Arndt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Mar 2005 19:32:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-4-1-event-filters/m-p/331584#M96788</guid>
      <dc:creator>a.arndt</dc:creator>
      <dc:date>2005-03-16T19:32:38Z</dc:date>
    </item>
    <item>
      <title>Re: IDS 4.1 event filters</title>
      <link>https://community.cisco.com/t5/network-security/ids-4-1-event-filters/m-p/331585#M96791</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it does. I got the CLI commands working to do just as you outlined using IDM. I just was not sure if flitering on a specific source port is available. I'll configure the filter based on source IP as you stated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Mar 2005 21:56:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-4-1-event-filters/m-p/331585#M96791</guid>
      <dc:creator>5creedus</dc:creator>
      <dc:date>2005-03-16T21:56:40Z</dc:date>
    </item>
    <item>
      <title>Re: IDS 4.1 event filters</title>
      <link>https://community.cisco.com/t5/network-security/ids-4-1-event-filters/m-p/331586#M96793</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Filtering on ports is added in version 5.0.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2005 17:00:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-4-1-event-filters/m-p/331586#M96793</guid>
      <dc:creator>marcabal</dc:creator>
      <dc:date>2005-03-17T17:00:19Z</dc:date>
    </item>
    <item>
      <title>Re: IDS 4.1 event filters</title>
      <link>https://community.cisco.com/t5/network-security/ids-4-1-event-filters/m-p/331587#M96796</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sweet! I guess I need to remember to state what version my instructions work with...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I happily stand corrected, at least where version 5.x is involved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alex Arndt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Mar 2005 15:25:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-4-1-event-filters/m-p/331587#M96796</guid>
      <dc:creator>a.arndt</dc:creator>
      <dc:date>2005-03-20T15:25:29Z</dc:date>
    </item>
  </channel>
</rss>

