<?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 Weak Encryption - SSL Module in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/weak-encryption-ssl-module/m-p/1281337#M26698</link>
    <description>&lt;P&gt;During a recent PCI compliance scan, 4 our our current SSL-Service(s) on the SSL module were scanned and came up with the "SSL Server Supports Weak Encryption Vulnerability". I have checked the configuration and all of our extranet web sites that are hosted on the CSM and have SSL termination at the SSL module appear the same. Also, the private key generated is a 1024 byte key pair. No defined ciphers are in the configuration at this time. Should there be? Is there a white paper on best practices for highest security using the SSL module. We will soon be migrating off to ACE modules, but with PCI compliance currently at hand, we have to mitigate this issue as soon as possible. Thanks.&lt;/P&gt;</description>
    <pubDate>Tue, 16 Jun 2009 13:23:28 GMT</pubDate>
    <dc:creator>aanelso1</dc:creator>
    <dc:date>2009-06-16T13:23:28Z</dc:date>
    <item>
      <title>Weak Encryption - SSL Module</title>
      <link>https://community.cisco.com/t5/application-networking/weak-encryption-ssl-module/m-p/1281337#M26698</link>
      <description>&lt;P&gt;During a recent PCI compliance scan, 4 our our current SSL-Service(s) on the SSL module were scanned and came up with the "SSL Server Supports Weak Encryption Vulnerability". I have checked the configuration and all of our extranet web sites that are hosted on the CSM and have SSL termination at the SSL module appear the same. Also, the private key generated is a 1024 byte key pair. No defined ciphers are in the configuration at this time. Should there be? Is there a white paper on best practices for highest security using the SSL module. We will soon be migrating off to ACE modules, but with PCI compliance currently at hand, we have to mitigate this issue as soon as possible. Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jun 2009 13:23:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/weak-encryption-ssl-module/m-p/1281337#M26698</guid>
      <dc:creator>aanelso1</dc:creator>
      <dc:date>2009-06-16T13:23:28Z</dc:date>
    </item>
    <item>
      <title>Re: Weak Encryption - SSL Module</title>
      <link>https://community.cisco.com/t5/application-networking/weak-encryption-ssl-module/m-p/1281338#M26699</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Configure an ssl policy to limit the cipher list.&lt;/P&gt;&lt;P&gt;Remove the weak ones and run your test again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ssl-proxy(config-context)#policy ssl Ciphers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ssl-proxy(config-ctx-ssl-policy)#cipher ?&lt;/P&gt;&lt;P&gt;  all                           All supported ciphers&lt;/P&gt;&lt;P&gt;  all-export                    All export ciphers&lt;/P&gt;&lt;P&gt;  all-strong                    All strong ciphers&lt;/P&gt;&lt;P&gt;  rsa-exp-with-des40-cbc-sha    rsa export with des40-sha&lt;/P&gt;&lt;P&gt;  rsa-exp-with-rc4-40-md5       rsa export with rc4-md5&lt;/P&gt;&lt;P&gt;  rsa-exp1024-with-des-cbc-sha  rsa export1024 with des-sha&lt;/P&gt;&lt;P&gt;  rsa-exp1024-with-rc4-56-md5   rsa export1024 with rc4-md5&lt;/P&gt;&lt;P&gt;  rsa-exp1024-with-rc4-56-sha   rsa export1024 with rc4-sha&lt;/P&gt;&lt;P&gt;  rsa-with-3des-ede-cbc-sha     rsa with 3des-sha&lt;/P&gt;&lt;P&gt;  rsa-with-des-cbc-sha          rsa with des-sha&lt;/P&gt;&lt;P&gt;  rsa-with-null-md5             rsa with null-md5&lt;/P&gt;&lt;P&gt;  rsa-with-rc4-128-md5          rsa with rc4-md5&lt;/P&gt;&lt;P&gt;  rsa-with-rc4-128-sha          rsa with rc4-sha&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jun 2009 14:44:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/weak-encryption-ssl-module/m-p/1281338#M26699</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2009-06-16T14:44:40Z</dc:date>
    </item>
    <item>
      <title>Re: Weak Encryption - SSL Module</title>
      <link>https://community.cisco.com/t5/application-networking/weak-encryption-ssl-module/m-p/1281339#M26700</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the quick response!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am a bit confused here....it appears that configuration that you are suggesting is for an ACE module. We are currently needing similar for SSL-Module (used in conjunction with CSM).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is what I think I will be using:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;bvlcoelablbrtr1-ssl(config)#ssl-proxy policy ssl Ciphers&lt;/P&gt;&lt;P&gt;bvlcoelabl(config-ssl-policy)#cipher rsa-with-rc4-128-md5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am assuming that the default is to use all which on the SSL-Module includes the following (I believe that rsa with des-sha is the only weak encryption). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  all                        All supported ciphers&lt;/P&gt;&lt;P&gt;  rsa-with-3des-ede-cbc-sha  rsa with 3des-sha&lt;/P&gt;&lt;P&gt;  rsa-with-des-cbc-sha       rsa with des-sha&lt;/P&gt;&lt;P&gt;  rsa-with-rc4-128-md5       rsa with rc4-md5&lt;/P&gt;&lt;P&gt;  rsa-with-rc4-128-sha       rsa with rc4-sha&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jun 2009 18:59:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/weak-encryption-ssl-module/m-p/1281339#M26700</guid>
      <dc:creator>aanelso1</dc:creator>
      <dc:date>2009-06-16T18:59:41Z</dc:date>
    </item>
  </channel>
</rss>

