<?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 IDSM-2 host blocks in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/idsm-2-host-blocks/m-p/2160629#M54047</link>
    <description>&lt;P&gt;Hey guys..... I'm having an issue and need some help....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My inline IDSM-2 is blocking internal hosts from accessing the internet. When I run a report to try and identify "why",&amp;nbsp; they don't show up. Using IME, I can see they are in the "denied attackers" section.&amp;nbsp; How can I find out what's causing it? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks...&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 12:54:21 GMT</pubDate>
    <dc:creator>Garrison Botts</dc:creator>
    <dc:date>2019-03-10T12:54:21Z</dc:date>
    <item>
      <title>IDSM-2 host blocks</title>
      <link>https://community.cisco.com/t5/network-security/idsm-2-host-blocks/m-p/2160629#M54047</link>
      <description>&lt;P&gt;Hey guys..... I'm having an issue and need some help....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My inline IDSM-2 is blocking internal hosts from accessing the internet. When I run a report to try and identify "why",&amp;nbsp; they don't show up. Using IME, I can see they are in the "denied attackers" section.&amp;nbsp; How can I find out what's causing it? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks...&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 12:54:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm-2-host-blocks/m-p/2160629#M54047</guid>
      <dc:creator>Garrison Botts</dc:creator>
      <dc:date>2019-03-10T12:54:21Z</dc:date>
    </item>
    <item>
      <title>IDSM-2 host blocks</title>
      <link>https://community.cisco.com/t5/network-security/idsm-2-host-blocks/m-p/2160630#M54048</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Remove only one of the denied hosts and monitor the logs that have its IP [ IME is great doing this ].&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you identify the host as a malicious unit, move it back to the list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you find out that the IPS is reacting to false positives, you can check the signatures that triggger and see how reliable they are.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; A packet capture is also a great idea to see what is the unit is seeing and understanding why it is blocking it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, if you just don't want this host to be affected by the IPS rules, simply create an event action filter for it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2013 05:36:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm-2-host-blocks/m-p/2160630#M54048</guid>
      <dc:creator>jocamare</dc:creator>
      <dc:date>2013-02-27T05:36:47Z</dc:date>
    </item>
  </channel>
</rss>

