Operations

WPA3 Brings New Authentication and Encryption to Wi-Fi

The Wi-Fi Alliance officially launches its latest protocol, which offers new capabilities for personal, enterprise, and IoT wireless networks.

Wi-Fi connections soon will become easier to secure with a newly available security protocol from the Wi-Fi Alliance.

WPA3 is the latest version of Wi-Fi Protected Access, a suite of protocols and technologies that provide authentication and encryption for Wi-Fi networks. WPA3, which was first announced earlier this year, is now available for inclusion in products. It brings two deployment models, personal and enterprise, along with a related security set called Easy Connect.

Kevin Robinson, vice president of marketing for the Wi-Fi Alliance, says WPA3 is intended to meet the security needs of wireless users in a security landscape that has become very dynamic. "WPA3 simplifies configuration and adds more authentication and increased cryptographic levels," Robinson says.

The primary enhancement to WPA3 Personal is in the authentication process, where WPA3 makes brute-force dictionary attacks much more difficult and time-consuming for an attacker. "For every guess at a password the attacker has to interact with the network," Robinson explains.

WPA3 Personal authentication is a process called a simultaneous authentication of equals (SAE), which comes from the IETF Dragonfly key exchange. Robinson says that with SAE, the authentication requires interaction, and only after authentication will the keys be generated. This makes attacks that depend on cloud-based server farms and automated key attempts unavailable to attackers.

WPA3 Enterprise provides 192-bit encryption, critical for Wi-Fi networks handling sensitive personal or intellectual property data. In addition, both WPA3 flavors disallow certain previous encryption algorithms while still providing a path for transition to the new standard. "You do have to think about how to transition. [The standard does] define a transition network, but they only allow WPA2 to blend with WPA3," he says.

While WPA3 Personal and Enterprise will see primary deployment for end devices such as laptops, tablets, and smartphones, IoT devices get their own new security with Easy Connect. This standard allows a device with a rich user interface to on-board devices with no UI. For example, a tablet or phone can be used to bring Web cams onto the network.

Robinson says that in a typical device enrollment, the new device will come with QR code, which the administrator will scan with a phone. The phone then "introduces" the IoT device to the network.

Asked about large-scale device enrollment, Robinson says that Easy Connect is scalable so that devices can be batch-introduced to the network. Easy Connect supports WPA2 and WPA3 networks and has provisions for future enhancements such as individual device management through the standard.

Robinson says that, as adoption grows, WPA3 will become mandatory in certified equipment. "Right now, WPA2 is mandatory, with WPA3 optional," he says though he expects that, by late 2019, there will be near-universal adoption of WPA3. 

Roughly 3 billion devices connect to a Wi-Fi network each year, according to the Wi-Fi Alliance.

Related Content:

Why Cybercriminals Attack: A DARK READING VIRTUAL EVENT Wednesday, June 27. Industry experts will offer a range of information and insight on who the bad guys are – and why they might be targeting your enterprise. Go here for more information on this free event.

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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Crowdsourced vs. Traditional Pen Testing
Alex Haynes, Chief Information Security Officer, CDL,  3/19/2019
BEC Scammer Pleads Guilty
Dark Reading Staff 3/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Well, at least it isn't Mobby Dick!
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
The State of Cyber Security Incident Response
The State of Cyber Security Incident Response
Organizations are responding to new threats with new processes for detecting and mitigating them. Here's a look at how the discipline of incident response is evolving.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-3965
PUBLISHED: 2019-03-23
Hospira Symbiq Infusion System 3.13 and earlier allows remote authenticated users to trigger "unanticipated operations" by leveraging "elevated privileges" for an unspecified call to an incorrectly exposed function.
CVE-2016-10743
PUBLISHED: 2019-03-23
hostapd before 2.6 does not prevent use of the low-quality PRNG that is reached by an os_random() function call.
CVE-2019-9947
PUBLISHED: 2019-03-23
An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.2. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the query string or PATH_INFO) follo...
CVE-2019-9948
PUBLISHED: 2019-03-23
urllib in Python 2.x through 2.7.16 supports the local_file: scheme, which makes it easier for remote attackers to bypass protection mechanisms that blacklist file: URIs, as demonstrated by triggering a urllib.urlopen('local_file:///etc/passwd') call.
CVE-2019-9945
PUBLISHED: 2019-03-23
SoftNAS Cloud 4.2.0 and 4.2.1 allows remote command execution. The NGINX default configuration file has a check to verify the status of a user cookie. If not set, a user is redirected to the login page. An arbitrary value can be provided for this cookie to access the web interface without valid user...