Qualys SSL Labs - SSL Pulse

Time 2020-09-24 05:07:31

Web Name: Qualys SSL Labs - SSL Pulse

WebSite: http://www.trustworthyinternet.org

ID:57745

Keywords:

SSL,Qualys,Pulse,

Description:

SSL Pulse is a continuous and global dashboard for monitoring the quality of SSL / TLS support over time across 150,000 SSL- and TLS-enabled websites, based on Alexa s list of the most popular sites in the world. This is the summary of the effective SSL security implemented by the most popular web sites. To be secure, a site has to be well configured, which means that it must have the A grade. In addition, it must not be vulnerable to any of the two currently known attacks against SSL (Insecure Renegotiation and the BEAST attack). The SSL Labs assessment grade reflects the quality of the configuration of an SSL web site. The assessment methodology is documented in the SSL Rating Guide. All SSL sites use certificates as their digital IDs. However, in many cases a chain certificates is needed to create a trust link between the user and a trust anchor. A common mistake is that the certificate chain is incomplete, which often results with certificate warnings on sites that are otherwise well configured. Key strength is the foundation of SSL security. Sites with weak keys cannot provide robust security, even when everything else is well configured. At minimum, web sites should 2048-bit RSA keys or 256-bit ECDSA keys. This chart shows both RSA and ECDSA keys, but the strength of the latter is converted to their RSA equivalent to make the comparison possible. For example, 256-bit ECDSA keys have strength equivalent to that of 3072-bit RSA keys. HTTP Strict Transport Security (HSTS) is an SSL safety net: technology designed to ensure that security remains intact even in the case of configuration problems and implementation errors. To activate HSTS protection, you set a single response header in your websites. After that, browsers that support HSTS (at this time, Chrome and Firefox) will enforce the protection. The goal of HSTS is simple: after activation, do not allow insecure communication with your website. It achieves this goal by automatically converting all plain-text links to secure ones. As a bonus, it will also disable click-through SSL certificate warnings. The Certification Authority Authorization (CAA) DNS Resource Record allows a DNS domain name holder to specify one or more Certification Authorities (CAs) authorized to issue certificates for that domain. CAA Resource Records allow a public Certification Authority to implement additional controls to reduce the risk of unintended certificate mis-issue. communication channel. Ciphers weaker than 128 bits are insecure and must not be used. There are six protocols in the SSL/TLS family, but not all of them are secure. The best practice is to use minimum TLS v1.2 as your main protocol and TLS v1.3 if they are supported by your server platform. That way, the clients that support newer protocols will select them, and those that don't will fall back to TLS v1.2. You must not use SSL v2.0 and SSL v3.0, because it is insecure. Avoid the usage of TLS v1.0 and TLS v1.1. This chart shows the weakest key exchange supported by the servers we monitor. Values of 512 bits are typically observed on servers that support insecure export suites; 768 on some servers that use weak DH parameters; 1024 bits is very common and also usually comes from weak DH parameters. At this time, 2048 bits is the minimum expected strength. In 2009, the renegotiation feature of SSL was found to be insecure. A successful exploitation of this issue may allow the attacker to impersonate his victims and extract confidential data. Most vendors have issued patches by now or, at the very least, provided workarounds for the problem. Extended Validation (EV) certificates are high-assurance certificates that rely on manual identity validation to establish links between web sites and the organizations behind them. HTTP/2 is the second generation of the HTTP protocol, which powers the World Wide Web. This protocol has its origins in the earlier experimental SPDY protocol, originally developed by Google. Forward Secrecy is a protocol feature that protects each connection individually. It designed so that is is impossible to compromise connection security by compromising server private key. There are six protocols in the SSL/TLS family, but not all of them are secure. The best practice is to use minimum TLS v1.2 as your main protocol and TLS v1.3 if they are supported by your server platform. That way, the clients that support newer protocols will select them, and those that don't will fall back to TLS v1.2. You must not use SSL v2.0 and SSL v3.0, because it is insecure. Avoid the usage of TLS v1.0 and TLS v1.1. Key strength is the foundation of SSL security. Sites with weak keys cannot provide robust security, even when everything else is well configured. At minimum, web sites should 2048-bit RSA keys or 256-bit ECDSA keys. This chart shows both RSA and ECDSA keys, but the strength of the latter is converted to their RSA equivalent to make the comparison possible. For example, 256-bit ECDSA keys have strength equivalent to that of 3072-bit RSA keys. The BEAST attack is a practical attack based on a protocol vulnerability that was discovered in 2004. A successful exploitation of this issue will result in a disclosure of victim's session cookies, allowing the attacker to completely hijack the application session. It is no longer considered a threat because modern browsers ship with mitigations that prevent the attack. RC4 is a very widely used cipher suite. Before 2013, we knew of some RC4 weaknesses, but it was thought that they did not affect SSL. With new research published in early 2013, we now know that RC4 is weak and should not be used. The strength of a certificate signature depends on the strength of the hashing function used to produce it. Most certificates use SHA1 for hashing, but this function is known to weak. It is advisable to use signatures that use SHA256 for hashing. A vulnerability in OpenSSL 1.0.1 versions (before 1.0.1t) and 1.0.2 versions (before 1.0.2h). This vulnerability can be exploited by MITM attacker using a padding Oracle attack to decrypt traffic when the connection uses an AES CBC cipher and the server supports AES-NI. Return Of Bleichenbacher Oracle Threat, is an attack model based on Daniel Bleichenbacher chosen-ciphertext attack. Researchers have been able to exploit the same vulnerability with small variations to the Bleichenbacher attack. A vulnerability in OpenSSL 1.0.1 (all releases) allows a MITM attacker to attack connections with clients who also use OpenSSL (all versions). Successful attack downgrades the connection and gives the attacker full access to the traffic. The DROWN attack is a cross-protocol security bug that attacks servers with modern protocol suites by using their support for the insecure SSL v2 protocol and also in cases where the servers don't support SSL v2 but shares the same RSA-key/hostname with server that does. To mitigate this attack disable SSLv2 on all servers you have. Heartbleed is a vulnerability in the widely deployed OpenSSL library. It is very easy to exploit and allows the attacker to retrieve sensitive server data in just a few HTTP requests. The sensitive data could be anything that's in process memory, including passwords, session data, and server private key. RC4 is a very widely used cipher suite. Before 2013, we knew of some RC4 weaknesses, but it was thought that they did not affect SSL. With new research published in early 2013, we now know that RC4 is weak and should not be used. The Zombie POODLE attack affects some TLS CBC implementations that don't have proper padding checks. The end result is that an active network attacker can relatively easily uncover small fragments of encrypted data (e.g., cookies). Zombie POODLE. A vulnerability in OpenSSL 1.0.2 versions (From 1.0.2 to 1.0.2q). When a 0-byte record is received with invalid padding, then OpenSSL behaves differently which is detectable to the remote peer, then this amounts to a padding oracle that could be used to decrypt data. CVE-2019-1559. The POODLE attack affects even some TLS implementations that don't have proper padding checks after decryption. The end result is that an active network attacker can relatively easily uncover small fragments of encrypted data (e.g., cookies). embed certificate freshness proof in the TLS handshake itself. Clients that connect to servers that support this feature don't need to contact the issuing CA to double-check certificate validity. GOLDENDOODLE is the name given for exploiting modern TLS stacks using the classic CBC padding oracle technique described by Serge Vaudenay in 2002. Difference between GOLDENDOODLE and Zombie POODLE or POODLE TLS is performance i.e GOLDENDOODLE is faster in exploiting. GOLDENDOODLE. This vulnerability is similar to POODLE TLS only change is that in POODLE TLS padding was checked on Application Record whereas for Sleeping POODLE padding is checked on Finished message. No article/advisory on this vulnerability is published yet. Servers that support a special signalling suite called TLS_FALLBACK_SCSV can detect protocol downgrade attacks when accessed by clients that also support this feature. Sites that support TLS compression. These sites are vulnerable to the CRIME attack.

TAGS:SSL Qualys Pulse 

<<< Thank you for your visit >>>

Hot Websites