<?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 Skype Access in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/skype-access/m-p/2084726#M54241</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a signature for Skype activity on the IPS:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;11251-0 Skype Client Activity &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However i believe this will only alert on the activity, it will not prevent Skype from working.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Skype has been designed to tunnel over legitimate protocols on a variety of ports and is therefore quite difficult to restrict.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have heard that the best way to go about it is to rate limit it to an unusable level.&lt;/P&gt;&lt;P&gt;&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;Neil Archibald&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 Jan 2013 16:32:53 GMT</pubDate>
    <dc:creator>nearchib</dc:creator>
    <dc:date>2013-01-07T16:32:53Z</dc:date>
    <item>
      <title>Skype Access</title>
      <link>https://community.cisco.com/t5/network-security/skype-access/m-p/2084725#M54239</link>
      <description>&lt;P&gt;Currently we are using a proxy for internet access with an ASA 5525 on the gateway.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We've started getting a number of requests for Skype access and after much research found that our proxy can't deal with it and neither can the ASA, so its either open the firewall up to all specfic users un-restricted access thus bypassing the proxy or not give access at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is can the IPS module for the ASA drop or allow Skype connections and secondly if a Skype connections is allowed then can it be configured through the IPS to bypass the firewall ruleset?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 12:51:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/skype-access/m-p/2084725#M54239</guid>
      <dc:creator>jonhill</dc:creator>
      <dc:date>2019-03-10T12:51:48Z</dc:date>
    </item>
    <item>
      <title>Skype Access</title>
      <link>https://community.cisco.com/t5/network-security/skype-access/m-p/2084726#M54241</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a signature for Skype activity on the IPS:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;11251-0 Skype Client Activity &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However i believe this will only alert on the activity, it will not prevent Skype from working.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Skype has been designed to tunnel over legitimate protocols on a variety of ports and is therefore quite difficult to restrict.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have heard that the best way to go about it is to rate limit it to an unusable level.&lt;/P&gt;&lt;P&gt;&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;Neil Archibald&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jan 2013 16:32:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/skype-access/m-p/2084726#M54241</guid>
      <dc:creator>nearchib</dc:creator>
      <dc:date>2013-01-07T16:32:53Z</dc:date>
    </item>
    <item>
      <title>Skype Access</title>
      <link>https://community.cisco.com/t5/network-security/skype-access/m-p/2084727#M54243</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"However i believe this will only alert on the activity, it will not prevent Skype from working."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think you can prevent anything from working as long as it's not encrypted, including skype. U just have to use any kind of traffic analyzer to see what application does, find something particular for application you're trying to block, write and tune signatures accordingly to what you see. I suppose u can do it even on any cisco ISR, using Flexible packet matching.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jan 2013 13:29:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/skype-access/m-p/2084727#M54243</guid>
      <dc:creator>Andrew Phirsov</dc:creator>
      <dc:date>2013-01-09T13:29:13Z</dc:date>
    </item>
    <item>
      <title>Skype Access</title>
      <link>https://community.cisco.com/t5/network-security/skype-access/m-p/2084728#M54245</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you want to use Skype, then the best method is to install the Skype-manager and control all access in a central way:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.skype.com/intl/en/business/skype-manager/"&gt;http://www.skype.com/intl/en/business/skype-manager/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the IPS-module or your ASA-5525 it's not possible as all Skype-traffic is encrypted and can use many different transports. Perhaps the ASA-CX is more capable, but that's only a guess.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;nbsp; &lt;BR /&gt;Don't stop after you've improved your network! Improve the world by lending money to the working poor: &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.kiva.org/invitedby/karsteni"&gt;http://www.kiva.org/invitedby/karsteni&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jan 2013 14:06:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/skype-access/m-p/2084728#M54245</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2013-01-09T14:06:06Z</dc:date>
    </item>
    <item>
      <title>Skype Access</title>
      <link>https://community.cisco.com/t5/network-security/skype-access/m-p/2084729#M54246</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don;t see how the Skype Manager would improve the situation, it doesn't solve the issue of allowing access off the network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jan 2013 14:17:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/skype-access/m-p/2084729#M54246</guid>
      <dc:creator>jonhill</dc:creator>
      <dc:date>2013-01-09T14:17:17Z</dc:date>
    </item>
    <item>
      <title>Skype Access</title>
      <link>https://community.cisco.com/t5/network-security/skype-access/m-p/2084730#M54247</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've interpreted your first post that way that you can allow skype, but not control it. Only for this control the Skype-manager can be a solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;nbsp; &lt;BR /&gt;Don't stop after you've improved your network! Improve the world by lending money to the working poor: &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.kiva.org/invitedby/karsteni"&gt;http://www.kiva.org/invitedby/karsteni&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jan 2013 14:29:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/skype-access/m-p/2084730#M54247</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2013-01-09T14:29:34Z</dc:date>
    </item>
  </channel>
</rss>

