Despite the goal of keeping web communications private, flaws in the design and implementation of Transport Layer Security have led to breaches. But the latest version \u2013 TLS 1.3 \u2013 is an overhaul that strengthens and streamlines the crypto protocol.\nWhat is TLS?\nTLS is a cryptographic protocol that provides end-to-end communications security over networks and is widely used for internet communications and online transactions. It is an IETF standard intended to prevent eavesdropping, tampering and message forgery. Common applications that employ TLS include Web browsers, instant messaging, e-mail and voice over IP.\n\nMany businesses use TLS to secure all communications between their Web servers and browsers regardless of whether sensitive data is being transmitted.\nTLS\u2019s predecessor, secure socket layer (SSL) was developed by Netscape in 1995. SSL version 1.0 and 2.0 contained many security flaws that prompted a complete redesign of the protocol. In 1996, Netscape released SSL version 3.0 which was the basis for TLS1.0.\u00a0 In 1999, the PCI Council suggested the eventual deprecation of SSL as TLS 1.0 was a significant upgrade to SSL 3.0.\u00a0\nTLS vs. SSL\u00a0\u00a0\nTLS is more efficient and secure than SSL as it has stronger message authentication, key-material generation and other encryption algorithms. For example, TLS supports pre-shared keys, secure remote passwords, elliptical-curve keys and Kerberos whereas SSL does not. \u00a0TLS and SSL are not interoperable, but TLS does offer backward compatibility for older devices still using SSL.\nThe TLS protocol specification defines two layers. The TLS record protocol provides connection security, and the TLS handshake protocol enables the client and server to authenticate each other and to negotiate security keys before any data is transmitted.\nThe TLS handshake is a multi-step process.\u00a0 A basic TLS handshake involves the client and server sending \u201chello\u201d messages, and the exchange of keys, cipher message and a finish message. The multi-step process is what makes TLS flexible enough to use in different applications because the format and order of exchange can be modified.\n\n\n\n\n\nTLS flaws and breaches\nFlaws in protocols and implementations constantly cause problems with security tools and technology, and TLS has certainly had its share of breaches.\u00a0 Some of the more significant attacks on TLS\/SSL:\n\nBEAST (2011): The Browser Exploit Against SSL\/TLS is a browser exploit that took advantage of a weakness in the cipher blocking chain (CBC) to extract the unencrypted plaintext in an encrypted session.\nCRIME and BREACH (2012 and 2013): The creators of BEAST authored the security exploit Compression Ratio Info-link Made Easy, which enables a hacker to retrieve the content of Web cookies, even when compression and TLS are used. One nefarious use case for this is recovering the authentication cookies so attackers can hijack authenticated web sessions. Browser Reconnaissance and Exfiltration via Adaptive Compression of Hypertext, or BREACH, is built on CRIME and extracts login tokens, e-mail addresses and other information.\nHeartbleed (2014): Heartbleed allows hackers to steal private keys from what should be secure servers. Infected servers were left wide open to let anyone on the Internet read the memory in systems being protected by a vulnerable version of OpenSSL. The breach let threat actors steal data from servers or listen in on conversations or even spoof services and other users.\n\nTLS 1.3 boosts security, performance, privacy\nTLS 1.3 was the first major rewrite as the Internet Engineering Task Force (IETF) set out to modernize the protocol. Think of previous versions being band aids put on flawed code. These might hold for a while but eventually the bad guys figured out how to work around that. The work on TLS1.3 started in April 2014, and it took four years and 28 drafts before it was approved in March of 2018.\nIn addition to making a major revision, the IETF set out to make what it called \u201cmajor improvements in the areas of security, performance and privacy\u201d. The biggest change is that TLS 1.3 makes it significantly more difficult for attackers to decrypt HTTPS-encrypted traffic and therefore better protect privacy.\nVersion 1.3 also makes the handshake process faster by speeding up the encryption process. This has a security benefit, but it should also improve performance of secure web applications. With TLS 1.2, the handshake process involved several round trips. With 1.3 only one round is required, and all the information is passed at that time.\nImplementing TLS 1.3 should be simple as it\u2019s designed to seamlessly replace TLS 1.2 and uses the same certificates and keys. Also, clients and servers can automatically negotiate a connection if it\u2019s supported on both sides. \u00a0\nEarly in its development cycle there were a few issues, the most notable of which came to light at a school system in Maryland where about 20,000 Chromebooks bricked when upgraded to TLS 1.3. Also, financial-services organizations were vehemently opposed because the encryption made them blind to what was happening on their own networks. The IETF made a few enhancements to allow the protocol to work with monitoring tools if implemented correctly.\nIn addition to security improvements, TLS 1.3 eliminated a number of older algorithms that did nothing other than create vulnerabilities. These include:\n\nRC4 Steam cipher\nDES\n3DES\nRSA Key transport\nSHA-1 hashing\nCBC Mode ciphers\nMD5\nDiffie-Hellman groups\nEXPORT ciphers\n\nAlso, the updated protocol added a function called \u201c0-RTT resumption\u201d that enables the client and server to remember if they have communicated before. If prior communications exist, the previous keys can be used, security checks skipped and the client and server can begin communicating immediately. It is believed that some of the bigger tech companies pushed for 0-RTT because they benefit from the faster connections, but there is some concern from security professionals.\nThe security benefits alone should justify TLS 1.3, but there are network reasons as well. In addition to the security improvements, TLS 1.3 is lighter weight than its predecessor and uses fewer resources. This means its more efficient, consumes fewer CPU cycles and reduces latency, which leads to better performance.