Access member only content, take part in discussions with comments on blogs, news and reviews and receive all the latest security industry news directly to your inbox. Join now for free.
Processing registration... Please wait.
This process can take up to a minute to complete.
A confirmation email has been sent to your email address - SUPPLIED EMAIL HERE. Please click on the link in the email to verify your email address. You need to verify your email before you can start posting.
If you do not receive your confirmation email within the next few minutes, it may be because the email has been captured by a junk mail filter. Please ensure you add the domain @scmagazine.com.au to your white-listed senders.
For many merchants, the quarterly ASV scan brings back a range of findings relating to weak SSL ciphers and/or implementation of SSLv2 that results in a failing score.
Often this can be a time consuming task to track down the offending systems, identify the changes necessary for that platform and then implement them.
The process itself is not terribly difficult, but it can be time consuming to identify the correct commands necessary to disable the weak ciphers.
In order to make this process a little less painful, the following is a condensed version of fixes for this issue across a range of common web platforms:
F5 BIG-IP
Configuration changes to SSL cipher support are best made via the BIG-IP console.
bigpipe profile clientssl <your_ssl_profile_name> { ciphers 'DEFAULT:!ADH:!EXPORT40:!EXP:!LOW' }
bigpipe save
Cisco Application Control Engine
In order to define specific SSL cipher support, you will need to establish a dedicated parameter map
parameter-map type ssl <your_map_name>
cipher RSA_WITH_3DES_EDE_CBC_SHA
cipher RSA_WITH_AES_128_CBC_SHA
cipher RSA_WITH_AES_256_CBC_SHA
Brocade (formerly Foundry) ServerIron
disable-ssl-v2no cipher-suite all-cipher-suitescipher-suite rsa-with-3des-ede-cbc-shacipher-suite rsa-with-aes-128-shacipher-suite rsa-with-aes-256-shacipher-suite rsa-with-rc4-128-md5cipher-suite rsa-with-rc4-128-sha
Apache v2
SSLProtocol -all +SSLv3 +TLSv1 SSLCipherSuite HIGH:!ADH
Microsoft IIS (Version 6 and below)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers
DES 56/56NULLRC2 40/128RC2 56/128RC4 40/128RC4 56/128RC4 64/128
Microsoft IIS 7
HKLM\System\CurrentControlSet\Control\SecurityProviders\SChannel\Protocols\SSL 2.0\
WebSEAL
Similar to Apache, WebSEAL uses a single file (webseald.conf) for key configuration items, located at /opt/pdweb/etc/ . Disabling SSLv2 and weak cipher support is quite straightforward.
disable-ssl-v2 = no
disable-ssl-v3 = no
disable-tls-v1 = no
default = DES-168
default = RC2-128
default = RC4-128
default = AES-128
default = AES-256
Lotus Domino
SSL ciphers can be modified either via the Domino Administrator tool, or via the notes.ini file. For the purposes of this article, we will be using the Administrator tool.
RC4 encryption with 128-bit key and MD5 MAC
RC4 encryption with 128-bit key and SHA-1 MAC
Triple DES encryption with 168-bit key and SHA-1 MAC
AES encryption with 128-bit key and SHA-1 MAC (Domino 8+ only)
AES encryption with 256-bit key and SHA-1 MAC (Domino 8+ only)
· You should also ensure that ‘Enable SSL v2’ is set to No
Copyright © SC Magazine, Australia
To begin commenting right away, you can log in below or register an account if you don't yet have one. Please read our guidelines on commenting. Offending posts will be removed and your access may be suspended. Abusive or obscene language will not be tolerated. The comments below do not necessarily reflect the views or opinions of SC Magazine, Haymarket Media or its employees.