<?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 IM on Cisco ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/blocking-im-on-cisco-asa/m-p/547881#M427390</link>
    <description>&lt;P&gt;Anyone know the best way to block Instant Messaging on an ASA (7.1) box? I'm taking that using a service policy is the correct method? I'm currently using the default service policy so I'm not sure what I need to remove from the default policy to accomplish this. Any ideas? Thanks&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 08:47:26 GMT</pubDate>
    <dc:creator>PaulWelc</dc:creator>
    <dc:date>2020-02-21T08:47:26Z</dc:date>
    <item>
      <title>Blocking IM on Cisco ASA</title>
      <link>https://community.cisco.com/t5/network-security/blocking-im-on-cisco-asa/m-p/547881#M427390</link>
      <description>&lt;P&gt;Anyone know the best way to block Instant Messaging on an ASA (7.1) box? I'm taking that using a service policy is the correct method? I'm currently using the default service policy so I'm not sure what I need to remove from the default policy to accomplish this. Any ideas? Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:47:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-im-on-cisco-asa/m-p/547881#M427390</guid>
      <dc:creator>PaulWelc</dc:creator>
      <dc:date>2020-02-21T08:47:26Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking IM on Cisco ASA</title>
      <link>https://community.cisco.com/t5/network-security/blocking-im-on-cisco-asa/m-p/547882#M427391</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;http-map http_deny_IM&lt;/P&gt;&lt;P&gt;port-misuse p2p action drop&lt;/P&gt;&lt;P&gt;port-misuse tunnelling action drop&lt;/P&gt;&lt;P&gt;port-misuse im action drop&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Mar 2006 02:40:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-im-on-cisco-asa/m-p/547882#M427391</guid>
      <dc:creator>froggy3132000</dc:creator>
      <dc:date>2006-03-22T02:40:42Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking IM on Cisco ASA</title>
      <link>https://community.cisco.com/t5/network-security/blocking-im-on-cisco-asa/m-p/547883#M427392</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks froggy3132000. Is this applied to the inside interface?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Mar 2006 15:06:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-im-on-cisco-asa/m-p/547883#M427392</guid>
      <dc:creator>PaulWelc</dc:creator>
      <dc:date>2006-03-22T15:06:56Z</dc:date>
    </item>
  </channel>
</rss>

