<?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: nm-cids and packet flow in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nm-cids-and-packet-flow/m-p/831611#M85175</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That depends on how you configured the IDS/IPS to work on. If it is promicious mode means, internet --&amp;gt; firewall (a copy of packet is sent to IDS for scanning of vulnerability in it) or if it is inline mode, internet --&amp;gt; IPS --&amp;gt; firewall, packet scanned by IPS will be send it to firewall for further processing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Dec 2007 14:59:13 GMT</pubDate>
    <dc:creator>jbayuka</dc:creator>
    <dc:date>2007-12-12T14:59:13Z</dc:date>
    <item>
      <title>nm-cids and packet flow</title>
      <link>https://community.cisco.com/t5/network-security/nm-cids-and-packet-flow/m-p/831610#M85174</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have some questions regarding the ids module. A router is connected to the internet and is using the software firewall. There is also a NM-CIDS in the router.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) What is the sequence when a packet arrives from the internet?&lt;/P&gt;&lt;P&gt;Is it internet -&amp;gt; firewall -&amp;gt; ids?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Does the command "ids-service module monitoring" imply that traffic is sent to the IDS inbound and outbound?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) The event viewer in the IDM shows a lot of events. Does it mean that the firewall is not dropping the packets? Is the IDM the only place to monitor the events or can they be sent to a syslog server?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4) In case there is an event, what can the module do to block the attack since it is not in line?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Pascal &lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:53:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nm-cids-and-packet-flow/m-p/831610#M85174</guid>
      <dc:creator>pascal_parrot</dc:creator>
      <dc:date>2019-03-10T10:53:41Z</dc:date>
    </item>
    <item>
      <title>Re: nm-cids and packet flow</title>
      <link>https://community.cisco.com/t5/network-security/nm-cids-and-packet-flow/m-p/831611#M85175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That depends on how you configured the IDS/IPS to work on. If it is promicious mode means, internet --&amp;gt; firewall (a copy of packet is sent to IDS for scanning of vulnerability in it) or if it is inline mode, internet --&amp;gt; IPS --&amp;gt; firewall, packet scanned by IPS will be send it to firewall for further processing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Dec 2007 14:59:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nm-cids-and-packet-flow/m-p/831611#M85175</guid>
      <dc:creator>jbayuka</dc:creator>
      <dc:date>2007-12-12T14:59:13Z</dc:date>
    </item>
    <item>
      <title>Re: nm-cids and packet flow</title>
      <link>https://community.cisco.com/t5/network-security/nm-cids-and-packet-flow/m-p/831612#M85176</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1) If there is no encryption then the packet is copied to the NM-CIDS after all router features (including firewall as well as NAT/PAT) have been done.  I am about 90% sure on this.  There is the possibility of a few features being done after the copy that I may not know about.&lt;/P&gt;&lt;P&gt;If NAT has been done then the packet itself will have the translated ips, however, the packet has an additional headers that tells the NM-CIDS wha the untranslated IPs are, and the analysis and alerting is done with the untranslated ips from the additional header.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When there is encryption involved, then incoming decryption is done with all other router features before copying to the NM-CIDS.  But the outgoing encryption is the one feature done on the packet After it is copied to the NM-CIDS.  This way the NM-CIDS always gets copies of unencrypted packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) The command on an interface implies that all traffic coming in as well as traffic going out will be copied to the Nm-CIDS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) If IDM shows alerts, then I am pretty sure this means that they are making it through the firewall features (not being dropped) and making it to the other network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I recommend using IEV for monitoring the alerts if you have a small number of sensors.&lt;/P&gt;&lt;P&gt;If you have a large number of sensors then I would recommend CS-MARS for monitoring.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IEV files:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/cgi-bin/tablebuild.pl/ips-ev" target="_blank"&gt;http://www.cisco.com/cgi-bin/tablebuild.pl/ips-ev&lt;/A&gt;&lt;/P&gt;&lt;P&gt;NOTE: There is not a User Guide specifically for the latest version.  To get a basic understanding look at the User Guide for the older version 4.x IEV:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/ips/4.0/configuration/guide/idm/swchap6.html" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/ips/4.0/configuration/guide/idm/swchap6.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOTE: Syslog is not supported for IPS events.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4) The NM-CIDS does support the Blocking feature.  With the Blocking features the NM-CIDS is able to telnet back into the router and create an ACL.  The ACL can then deny the IP Address of the attacker.&lt;/P&gt;&lt;P&gt;It can not deny the actual packet that triggered the signature, but the ACL can deny additional packets coming from that attacker/source address.&lt;/P&gt;&lt;P&gt;To read more on the Blocking feature:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/partner/products/hw/vpndevc/ps4077/products_configuration_guide_chapter09186a00807517a6.html" target="_blank"&gt;http://www.cisco.com/en/US/partner/products/hw/vpndevc/ps4077/products_configuration_guide_chapter09186a00807517a6.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Dec 2007 20:03:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nm-cids-and-packet-flow/m-p/831612#M85176</guid>
      <dc:creator>marcabal</dc:creator>
      <dc:date>2007-12-12T20:03:16Z</dc:date>
    </item>
  </channel>
</rss>

