<?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: IDS Location in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ids-location/m-p/1054998#M79039</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was looking for an article about where to place an IDS on a network.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Aug 2008 13:33:38 GMT</pubDate>
    <dc:creator>rayroyalmontana</dc:creator>
    <dc:date>2008-08-27T13:33:38Z</dc:date>
    <item>
      <title>IDS Location</title>
      <link>https://community.cisco.com/t5/network-security/ids-location/m-p/1054993#M79024</link>
      <description>&lt;P&gt;What factors should be considered when deciding where to place an IDS on a network?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:16:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-location/m-p/1054993#M79024</guid>
      <dc:creator>rayroyalmontana</dc:creator>
      <dc:date>2019-03-10T11:16:02Z</dc:date>
    </item>
    <item>
      <title>Re: IDS Location</title>
      <link>https://community.cisco.com/t5/network-security/ids-location/m-p/1054994#M79028</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One of the most important considerations to sensor placement is to place it inside the firewall. This will keep you from looking at events that would have been blocked by your firewall poilcy and allow you to spend your time looking at reall traffic entering your network.&lt;/P&gt;&lt;P&gt;If you use a VPN, placing the sensor on the unencrypted side is good too.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Aug 2008 18:13:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-location/m-p/1054994#M79028</guid>
      <dc:creator>rhermes</dc:creator>
      <dc:date>2008-08-26T18:13:48Z</dc:date>
    </item>
    <item>
      <title>Re: IDS Location</title>
      <link>https://community.cisco.com/t5/network-security/ids-location/m-p/1054995#M79031</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Another important point is to compare the throughput offered by the throughput with the one to be monitored. Otherwise it could be a real bottleneck for our network. This would also  influence your deployment mode (Inline,Promiscuous etc.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Aug 2008 19:10:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-location/m-p/1054995#M79031</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-08-26T19:10:09Z</dc:date>
    </item>
    <item>
      <title>Re: IDS Location</title>
      <link>https://community.cisco.com/t5/network-security/ids-location/m-p/1054996#M79033</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you provide a link to an article about this issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Aug 2008 10:21:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-location/m-p/1054996#M79033</guid>
      <dc:creator>rayroyalmontana</dc:creator>
      <dc:date>2008-08-27T10:21:58Z</dc:date>
    </item>
    <item>
      <title>Re: IDS Location</title>
      <link>https://community.cisco.com/t5/network-security/ids-location/m-p/1054997#M79036</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you be let us know about which 'issue' do you need the link?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Aug 2008 13:24:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-location/m-p/1054997#M79036</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-08-27T13:24:13Z</dc:date>
    </item>
    <item>
      <title>Re: IDS Location</title>
      <link>https://community.cisco.com/t5/network-security/ids-location/m-p/1054998#M79039</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was looking for an article about where to place an IDS on a network.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Aug 2008 13:33:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-location/m-p/1054998#M79039</guid>
      <dc:creator>rayroyalmontana</dc:creator>
      <dc:date>2008-08-27T13:33:38Z</dc:date>
    </item>
    <item>
      <title>Re: IDS Location</title>
      <link>https://community.cisco.com/t5/network-security/ids-location/m-p/1054999#M79041</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm not aware of any such document on the Cisco website at least. Ill try to write a short description here. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some places to use Promiscuous mode:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; When you fear that the sensor will be a bottleneck because of its limited throughput (if placed Inline) in each traffic flow.&lt;/P&gt;&lt;P&gt;&amp;gt; You want to protect a server farm subnet, but not all subnets in it. This is sort of related to the first point.&lt;/P&gt;&lt;P&gt;&amp;gt; You are concerned that the sensor deployment is not mature and it might block valid connections (False Negative).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some places to use Inline mode:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; When you want the IPS to play a more 'active' role in the network and Deny packets as they pass through it. With promiscuous mode it is possible that the attack goes through before the sensor actually goes ahead and 'logs' into the blocking device and block its.&lt;/P&gt;&lt;P&gt;&amp;gt; When you have devices that are not supported for blocking, like non cisco routers etc. you would go for inline&lt;/P&gt;&lt;P&gt;&amp;gt; You want the sensor to have a 'better view' of the network&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some places to use Inline VLAN pair mode:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Same as inine, but you don't have enough physical interfaces to cover all physical segments. Also IDSM-2 is usually deployed in this fashion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Aug 2008 15:25:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-location/m-p/1054999#M79041</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-08-27T15:25:33Z</dc:date>
    </item>
    <item>
      <title>Re: IDS Location</title>
      <link>https://community.cisco.com/t5/network-security/ids-location/m-p/1055000#M79043</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://analysisandreview.com/security/ips-ids-install-tune-incident-response-guide/" target="_blank"&gt;http://analysisandreview.com/security/ips-ids-install-tune-incident-response-guide/&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Sep 2008 16:48:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-location/m-p/1055000#M79043</guid>
      <dc:creator>kutukutu9</dc:creator>
      <dc:date>2008-09-03T16:48:58Z</dc:date>
    </item>
  </channel>
</rss>

