Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Application Security

9/7/2018
05:05 PM
100%
0%

TLS 1.3 Won't Break Everything

The newest version of TLS won't break everything in your security infrastructure, but you do need to be prepared for the changes it brings.

Transport Layer Security (TLS) is a foundation piece of modern Internet security. As the replacement of the earlier (and now deprecated) SSL, TLS encrypts the majority of sessions taking place via a web interface. And now, there's a new version with new considerations for organizations giving their users and customers a more secure web experience.

In August, TLS 1.3 was defined in IETF RFC 8446. With that formal definition, the new version became available for implementation and a possible part of the requirements for a number of different regulations.

TLS 1.3 was not suddenly sprung on an unsuspecting world. The new standard went through 28 drafts to reach a production state and some products and services began incorporating TLS 1.3 compatibility over a year before the final version. Even so, articles have been written, and speeches given, about all the ways that TLS 1.3 will break current security protocols. So what is it about TLS 1.3 that leads to so much anxiety?

How TLS 1.3 is different

One of the important benefits touted for TLS 1.3 is improved performance, much of which comes because of a simplified "handshake" process between client and server when establishing a session. There are several technical reasons this is possible, but one of them is that a single negotiation — that of which encryption algorithm to use — is eliminated.

The server provides a key for an approved algorithm, the client accepts the key, and the session is begun. One strength of this scheme is that a number of older, weaker, encryption algorithms are no longer allowed, so several attack mechanisms become impossible.

When the server supplies an encryption key, it is valid for the particular session, and only that session. This leads to something called Perfect Forward Secrecy (PFS), which means that it's impossible for a threat actor to capture a bunch of traffic, later discover the server's encryption key, and then decrypt the captured traffic after the fact. This is, by itself, a major step forward in data security.

Why TLS 1.3 is important

While many organizations, especially those in finance and banking, have been proponents of TLS 1.3, there has not been universal joy at its adoption. The reason is that, despite the concerns of some security professionals, there's no "back door" into the unencrypted traffic.

Why would security professionals, of all people, want a back door into encryption? The answer is visibility. Many enterprise security tools, especially those that do anything described as "deep packet inspection," are essentially engaging in an authorized man-in-the-middle attack, intercepting encrypted traffic, decrypting and analyzing the contents, then re-encrypting the stream before sending it to its destination.

This sort of man-in-the-middle approach is relatively simple with an encryption key based on a server identity (rather than a session), but becomes vastly more complex with the scheme used by TLS 1.3. To put it bluntly, TLS 1.3 breaks many of the products used by organizations deploying TLS 1.2 for their encryption. Those organizations have concerns for both malware trapping and regulatory compliance since they may not have a way of inspecting the contents of communications going in and out of the network.

Network and application infrastructure companies have begun rolling out products that address the inspection issues in TLS 1.3. This is critical because both server software and browsers are beginning to be released that support or require the use of TLS 1.3. The real question will be how quickly organizations adopt the new protocol, a question that is more relevant given that, by some measures, more than half of all commercial web sites still have pages using TLS 1.0 for security.

Related content:

 

 

Black Hat Europe returns to London Dec 3-6 2018  with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/14/2020
Omdia Research Launches Page on Dark Reading
Tim Wilson, Editor in Chief, Dark Reading 7/9/2020
Why Cybersecurity's Silence Matters to Black Lives
Tiffany Ricks, CEO, HacWare,  7/8/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13934
PUBLISHED: 2020-07-14
An h2c direct connection to Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M5 to 9.0.36 and 8.5.1 to 8.5.56 did not release the HTTP/1.1 processor after the upgrade to HTTP/2. If a sufficient number of such requests were made, an OutOfMemoryException could occur leading to a denial of service.
CVE-2020-13935
PUBLISHED: 2020-07-14
The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56 and 7.0.27 to 7.0.104. Invalid payload lengths could trigger an infinite loop. Multiple requests with invalid payload lengths could lead to a denial of ser...
CVE-2020-15721
PUBLISHED: 2020-07-14
RosarioSIS through 6.8-beta allows modules/Custom/NotifyParents.php XSS because of the href attributes for AddStudents.php and User.php.
CVE-2020-7592
PUBLISHED: 2020-07-14
A vulnerability has been identified in SIMATIC HMI Basic Panels 1st Generation (incl. SIPLUS variants) (All versions), SIMATIC HMI Basic Panels 2nd Generation (incl. SIPLUS variants) (All versions), SIMATIC HMI Comfort Panels (incl. SIPLUS variants) (All versions), SIMATIC HMI KTP700F Mobile Arctic ...
CVE-2020-7593
PUBLISHED: 2020-07-14
A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (V1.81.01 - V1.81.03), LOGO! 8 BM (incl. SIPLUS variants) (V1.82.01), LOGO! 8 BM (incl. SIPLUS variants) (V1.82.02). A buffer overflow vulnerability exists in the Web Server functionality of the device. A remote unauthenticate...