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
News
FluBot Malware's Rapid Spread May Soon Hit US Phones
Kelly Sheridan, Staff Editor, Dark Reading,  4/28/2021
Slideshows
7 Modern-Day Cybersecurity Realities
Steve Zurier, Contributing Writer,  4/30/2021
Commentary
How to Secure Employees' Home Wi-Fi Networks
Bert Kashyap, CEO and Co-Founder at SecureW2,  4/28/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31828
PUBLISHED: 2021-05-06
An SSRF issue in Open Distro for Elasticsearch (ODFE) before 1.13.1.0 allows an existing privileged user to enumerate listening services or interact with configured resources via HTTP requests exceeding the Alerting plugin's intended scope.
CVE-2020-18888
PUBLISHED: 2021-05-06
Arbitrary File Deletion vulnerability in puppyCMS v5.1 allows remote malicious attackers to delete the file/folder via /admin/functions.php.
CVE-2020-18890
PUBLISHED: 2021-05-06
Rmote Code Execution (RCE) vulnerability in puppyCMS v5.1 due to insecure permissions, which could let a remote malicious user getshell via /admin/functions.php.
CVE-2021-31793
PUBLISHED: 2021-05-06
An issue exists on NightOwl WDB-20-V2 WDB-20-V2_20190314 devices that allows an unauthenticated user to gain access to snapshots and video streams from the doorbell. The binary app offers a web server on port 80 that allows an unauthenticated user to take a snapshot from the doorbell camera via the ...
CVE-2021-31916
PUBLISHED: 2021-05-06
An out-of-bounds (OOB) memory write flaw was found in list_devices in drivers/md/dm-ioctl.c in the Multi-device driver module in the Linux kernel before 5.12. A bound check failure allows an attacker with special user (CAP_SYS_ADMIN) privilege to gain access to out-of-bounds memory leading to a syst...