<?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: Instant Messenging monitoring in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/instant-messenging-monitoring/m-p/435743#M95470</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Alex, this is exactly what I was looking for. I'm just glad the customer wants to track and not alert on these or we'd most likely have to get an always on line to them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 Aug 2005 20:11:44 GMT</pubDate>
    <dc:creator>5creedus</dc:creator>
    <dc:date>2005-08-30T20:11:44Z</dc:date>
    <item>
      <title>Instant Messenging monitoring</title>
      <link>https://community.cisco.com/t5/network-security/instant-messenging-monitoring/m-p/435740#M95455</link>
      <description>&lt;P&gt;Looking to montior IM sessions using IDS. Due to the nature of IM and the many ports it can use, is there another method (string match etc) that can be used to monitor this activity? The use of customer signature(s) is ok.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:36:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/instant-messenging-monitoring/m-p/435740#M95455</guid>
      <dc:creator>5creedus</dc:creator>
      <dc:date>2019-03-10T09:36:46Z</dc:date>
    </item>
    <item>
      <title>Re: Instant Messenging monitoring</title>
      <link>https://community.cisco.com/t5/network-security/instant-messenging-monitoring/m-p/435741#M95460</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;look at the IPS signatures in the 112xx range.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Aug 2005 17:46:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/instant-messenging-monitoring/m-p/435741#M95460</guid>
      <dc:creator>scothrel</dc:creator>
      <dc:date>2005-08-29T17:46:01Z</dc:date>
    </item>
    <item>
      <title>Re: Instant Messenging monitoring</title>
      <link>https://community.cisco.com/t5/network-security/instant-messenging-monitoring/m-p/435742#M95465</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is a long list of signatures that will probably do what you're looking for. They are as follows (as of S187):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;11200 - Yahoo Messenger Activity&lt;/P&gt;&lt;P&gt;11201 - MSN Messenger Activity&lt;/P&gt;&lt;P&gt;11202 - AIM / ICQ Messenger Activity&lt;/P&gt;&lt;P&gt;11203 - IRC Channel Join&lt;/P&gt;&lt;P&gt;11204 - Jabber Activity&lt;/P&gt;&lt;P&gt;11205 - Sametime Activity&lt;/P&gt;&lt;P&gt;11206 - ICQ Client DNS Request&lt;/P&gt;&lt;P&gt;11207 - AIM Client DNS request&lt;/P&gt;&lt;P&gt;11208 - Yahoo Messenger Client DNS Request&lt;/P&gt;&lt;P&gt;11209 - MSN Messenger Client DNS Request&lt;/P&gt;&lt;P&gt;11210 - AIM / ICQ Through HTTP Proxy&lt;/P&gt;&lt;P&gt;11211 - MSN Messenger Through HTTP Proxy&lt;/P&gt;&lt;P&gt;11212 - Yahoo Messenger Through HTTP Proxy&lt;/P&gt;&lt;P&gt;11213 - AOL IM Login&lt;/P&gt;&lt;P&gt;11214 - AIM/ICQ Message Send&lt;/P&gt;&lt;P&gt;11215 - AIM/ICQ Message Receive&lt;/P&gt;&lt;P&gt;11216 - AOL IM Chat - User Join&lt;/P&gt;&lt;P&gt;11217 - Yahoo Messenger Logon&lt;/P&gt;&lt;P&gt;11218 - Yahoo Messenger Send Message&lt;/P&gt;&lt;P&gt;11219 - Yahoo Messenger Receive Message&lt;/P&gt;&lt;P&gt;11221 - Yahoo Messenger Chat Invitation Activity&lt;/P&gt;&lt;P&gt;11222 - MSN Login&lt;/P&gt;&lt;P&gt;11223 - MSN Message Sent&lt;/P&gt;&lt;P&gt;11224 - MSN Message Received&lt;/P&gt;&lt;P&gt;11225 - MSN Chat Invitation Sent&lt;/P&gt;&lt;P&gt;11226 - MSN Chat Invitation Received&lt;/P&gt;&lt;P&gt;11227 - MSN Chat Invitation Accepted&lt;/P&gt;&lt;P&gt;11228 - MSN Chat Joined&lt;/P&gt;&lt;P&gt;11229 - AOL IM Chat - User Leave&lt;/P&gt;&lt;P&gt;11230 - AOL IM Chat - Incoming Message&lt;/P&gt;&lt;P&gt;11231 - AOL IM Chat - Outgoing Message&lt;/P&gt;&lt;P&gt;11232 - AOL IM Chat - Create room&lt;/P&gt;&lt;P&gt;11233 - SSH Over Non-standard Ports&lt;/P&gt;&lt;P&gt;11234 - Jabber Logon&lt;/P&gt;&lt;P&gt;11235 - MSN File Transfer Proposal Sent&lt;/P&gt;&lt;P&gt;11236 - MSN File Transfer Proposal Received&lt;/P&gt;&lt;P&gt;11237 - Jabber Chatroom Activity&lt;/P&gt;&lt;P&gt;11238 - MSNFTP File Transfer&lt;/P&gt;&lt;P&gt;11239 - ICQ Chat Invitation Sent&lt;/P&gt;&lt;P&gt;11240 - ICQ Chat Invitation Received&lt;/P&gt;&lt;P&gt;11241 - ICQ Specific Request&lt;/P&gt;&lt;P&gt;11242 - ICQ File Transfer&lt;/P&gt;&lt;P&gt;11244 - MSN P2P File Transfer&lt;/P&gt;&lt;P&gt;11245 - IRC Server Connection&lt;/P&gt;&lt;P&gt;11246 - AIM File Transfer Request&lt;/P&gt;&lt;P&gt;11247 - AIM File Transfer&lt;/P&gt;&lt;P&gt;11248 - Gadu-Gadu Login&lt;/P&gt;&lt;P&gt;11249 - Gadu-Gadu IM Message Sent&lt;/P&gt;&lt;P&gt;11250 - Gadu-Gadu IM Message Received&lt;/P&gt;&lt;P&gt;11251 - Skype Client Activity&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;According to the config on one of my production sensors, none of these signatures, with the exception of 11245 (subsig 0 and 1), are enabled by default. Therefore, in order to take advantage of them, you will have to use your favourite method (IDM, VMS, etc.) to enable them. Also, since they are "informational" only, you may have to reconfigure your monitoring console to actually see them (IEV, for example, only displays "high" and "medium" events by default).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That being said, like anything else, there is a cost in using them (read: potential alarm rate). This will particularly evident if IM is not specifically banned in your environment and you just want to use these signatures to develop some statistics detailing the usage of the various IM applications identified by this group of signatures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps,&lt;/P&gt;&lt;P&gt;Alex Arndt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Aug 2005 18:24:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/instant-messenging-monitoring/m-p/435742#M95465</guid>
      <dc:creator>a.arndt</dc:creator>
      <dc:date>2005-08-29T18:24:25Z</dc:date>
    </item>
    <item>
      <title>Re: Instant Messenging monitoring</title>
      <link>https://community.cisco.com/t5/network-security/instant-messenging-monitoring/m-p/435743#M95470</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Alex, this is exactly what I was looking for. I'm just glad the customer wants to track and not alert on these or we'd most likely have to get an always on line to them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Aug 2005 20:11:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/instant-messenging-monitoring/m-p/435743#M95470</guid>
      <dc:creator>5creedus</dc:creator>
      <dc:date>2005-08-30T20:11:44Z</dc:date>
    </item>
    <item>
      <title>Re: Instant Messenging monitoring</title>
      <link>https://community.cisco.com/t5/network-security/instant-messenging-monitoring/m-p/435744#M95474</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My pleasure. Glad I could help out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alex Arndt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Aug 2005 10:45:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/instant-messenging-monitoring/m-p/435744#M95474</guid>
      <dc:creator>a.arndt</dc:creator>
      <dc:date>2005-08-31T10:45:15Z</dc:date>
    </item>
  </channel>
</rss>

