So, this isn't an uncommon security alert when you have your system scanned.  One thing to keep in mind is the placement of your server and who/what it is accessed for.  In any case, you're not likely to find a Cisco doc that references this specifically.  Instead, if you really want to move forward with making the appropriate registry changes then you'll want to open a TAC case and find out if this is supported or not.  In terms of further info on your issue:

There is a McAfee article about making websites more secure.  It is here:  http://www.codeproject.com/KB/aspnet/MakeWebsiteMcAfeeSecured.aspx

Your alert is referenced as follows:

Vulnerability Name:  Weak Supported SSL Ciphers Suites

Description

The remote host supports the use of SSL ciphers that offer either weak encryption or no encryption at all. This vulnerability is valid for all SSL/TLS sessions that are passing sensitive information.
PCI defines strong cryptography, for secret key based systems, as anything above 80 bit encryption.

Solution

The solution to this is very simple but requires registry tweak again. Following are the steps:

• Click Start, click Run, type regedt32 or type regedit, and then click OK.
• In Registry Editor, locate the following registry key:

  HKey_Local_Machine\System\CurrentControlSet\Control\SecurityProviders 
                                \SCHANNEL\Ciphers 

  
• Under the Cipher key, there are several Ciphers.
• Locate the ciphers which have encryption less than 128 bit.
• Create DWORD values named Enabled and Value 0 for each of them, just as the previous case.
• For convenience, I have marked them with red arrows in the picture above.
• System Restart is NOT required for this.

Now the server is secured.
The above mentioned security issues are the major ones that most of the systems have. However other than this, there may be some easy and minor vulnerabilities like:

• Using robots.txt in the pages. (Generally inserted by Web Marketing team to track user hit).
• Directory Scanner: Common directories are revealed. This can be resolved by URL rewriting and setting “Directory Browsing” off.

Note: For the above vulnerabilities, minor registry tweaks will be necessary. So it is strongly recommended to back up the registry before doing anything. By any chance if something gets messed up, just delete the SCHANNEL key and restart the machine, the key will be auto-generated.

Hailey

Please rate helpful posts!