For over 20 years Secure Sockets Layer (SSL) has been in the market as one of the most widely-used encryption protocols ever released, and remains in widespread use today despite various security vulnerabilities exposed in the protocol. SSL/early TLS was removed as an example of strong cryptography in PCI DSS v3.1 (April 2015).
SSL v3.0 was superseded in 1999 by TLS v1.0, which has since been superseded by TLS v1.1 and v1.2. Now SSL & early TLS no longer meet minimum security standards due to security vulnerabilities in the protocol for which there are no fixes. It is critically important that entities upgrade to a secure alternative as soon as possible, and disable any fallback to both SSL and early TLS.
The best response is to disable SSL entirely and migrate to a more modern encryption protocol, which at the time of publication is a minimum of TLS v1.1, although entities are strongly encouraged to consider TLS v1.2 as not all implementations of TLS v1.1 are considered secure.
Yes but PCI DSS compliance scans from Approved Scanning Vendors check more than just SSLv3. After June 30, 2018, all entities MUST have stopped use of SSL & early TLS as a security control, and use only secure versions of the protocol. Failure to comply with this instruction will impact ASV scan results and will ultimately negatively impact on PCI compliance. A document on the PCI DSS requirements regarding SSL & early TLS can be read here.
For the convenience of LANCOM resellers looking to future proof their customer’s SSL/TLS settings, as well as pass PCI DSS testing now and into the future, we have formulated a script that will disable every instance of SSL v3.0, TLS v1.0 and TLS v1.1 leaving only the latest TLS v1.2 enabled. This script also locks down other security algorithm settings to ensure LANCOM routers will pass PCI DSS compliance scans.
*Note HTTPS WAN remote access can be enabled if a valid SSL certificate from a trusted Certificate Authority is loaded into the router. Even with HTTPS disabled you can still fully manage a LANCOM router over SSH Port 22 using the latest version of LANconfig and the CLI.
About the author