<?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 blocking connections in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/blocking-connections/m-p/1531974#M695171</link>
    <description>&lt;P&gt;If there is a need to block unwanted or malicious connections on firewall, shun is advised.&lt;/P&gt;&lt;P&gt;Appreciate if any of the gurus here can help me understand what is different in shun than using the ACL for the same purpose.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In which typical scenario is shun preferred over acl.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 18:55:24 GMT</pubDate>
    <dc:creator>suthomas1</dc:creator>
    <dc:date>2019-03-11T18:55:24Z</dc:date>
    <item>
      <title>blocking connections</title>
      <link>https://community.cisco.com/t5/network-security/blocking-connections/m-p/1531974#M695171</link>
      <description>&lt;P&gt;If there is a need to block unwanted or malicious connections on firewall, shun is advised.&lt;/P&gt;&lt;P&gt;Appreciate if any of the gurus here can help me understand what is different in shun than using the ACL for the same purpose.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In which typical scenario is shun preferred over acl.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:55:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-connections/m-p/1531974#M695171</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2019-03-11T18:55:24Z</dc:date>
    </item>
    <item>
      <title>Re: blocking connections</title>
      <link>https://community.cisco.com/t5/network-security/blocking-connections/m-p/1531975#M695182</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;acl will drop everything between a source and destination&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;whereas using shun you can specify a threshold after which it will start shunning, for example say if you see x number of packets in a duration of y mins from z shun the traffic&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope it helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- JA&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Oct 2010 16:49:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-connections/m-p/1531975#M695182</guid>
      <dc:creator>Jitendriya Athavale</dc:creator>
      <dc:date>2010-10-17T16:49:29Z</dc:date>
    </item>
    <item>
      <title>Re: blocking connections</title>
      <link>https://community.cisco.com/t5/network-security/blocking-connections/m-p/1531976#M695195</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Shun will block everything from the specified host, ACL`s will allow you to permit some ports/protocols and deny the rest of the traffic from the specified host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Oct 2010 17:12:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-connections/m-p/1531976#M695195</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2010-10-17T17:12:44Z</dc:date>
    </item>
    <item>
      <title>Re: blocking connections</title>
      <link>https://community.cisco.com/t5/network-security/blocking-connections/m-p/1531977#M695219</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another difference between "shun" and ACLs is in the packet processing. "Shun"ning is performed at the very first in the packet processing steps while ACL checks are performed after a "Flow lookup" or "Connection entry" lookup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So basically it means, if there is an exisiting connection for some kind of traffic and you decide to block it using ACLs it will not happen unless that connection is torn down and a new one created. But if you decide to "shun" that host, then in spite of the exisiting connection entry "anything and everything" from the host will be blocked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the reason why when we configure IPS to block hosts on ASAs (using signature action as "request block"), it uses the "shun" command rather than ACLs (which it uses for router's and switches).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that is clear!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;BR /&gt;Prapanch&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Oct 2010 00:16:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-connections/m-p/1531977#M695219</guid>
      <dc:creator>praprama</dc:creator>
      <dc:date>2010-10-18T00:16:09Z</dc:date>
    </item>
  </channel>
</rss>

