Key Takeaways
- WPA2-Enterprise is a Wi-Fi security mode that authenticates individual users or devices to protect enterprise networks from unauthorized access.
- It uses 802.1X to control network access, with a RADIUS server verifying the identity of each user or device before granting access.
- Unlike WPA2-PSK, which relies on a shared password, WPA2-Enterprise authenticates users individually. WPA3-Enterprise offers newer security improvements for compatible networks.
Many of us connect to enterprise Wi-Fi at work or on campus without giving much thought to how it actually works. WPA2-Enterprise is often what keeps those connections secure behind the scenes. But how does it verify who’s connecting, and what role does 802.1X play in the process?
In this guide, we’ll look at how WPA2-Enterprise works and how it compares with other Wi-Fi authentication methods. We’ll also analyze its pros and cons.
What Is WPA2-Enterprise?
WPA2-Enterprise is a Wi-Fi security protocol designed for organizations, enterprises, schools, hospitals, and any environment where protecting sensitive data and controlling access is critical. Unlike the shared-password approach common to homes or small-office setups, WPA2-Enterprise authenticates every user and device individually before granting network access, creating a much stronger barrier against unauthorized entry.
WPA2-Enterprise combines robust over-the-air encryption with per-user authentication enforced through the 802.1X framework. This allows administrators to apply granular policies, such as role-based access, VLAN segmentation, or device posture checks.
Here’s an illustration of what a WPA2-Enterprise network looks like in practice: multiple device types and one secure, centrally managed connection.
Info: Enterprise configurations are the gold standard for large-scale Wi-Fi authentication because they support integration with existing identity systems (like Active Directory, LDAP, or cloud directories) and can scale to thousands of users without compromising security. Businesses choose WPA2-Enterprise to safeguard against common threats like man-in-the-middle attacks or credential compromise.
If your network serves diverse users, handles confidential information, or needs centralized control, WPA2-Enterprise provides the structured, individualized authentication that personal modes simply can’t match.
How Does WPA2–Enterprise Work?
WPA2-Enterprise secures Wi-Fi networks by verifying each user's identity through a central authentication server instead of using one shared password. It uses IEEE 802.1X for access control and typically relies on a RADIUS server to authenticate users or devices before granting network access.
Here's how WPA2-Enterprise authentication works:
- A device connects to the Wi-Fi network. The user selects the enterprise Wi-Fi network on a laptop, phone, or other supported device.
- The access point requests authentication. The wireless access point acts as the authenticator and forwards the device's authentication messages to a RADIUS server.
- The RADIUS server verifies the identity. The server checks the authentication request using a supported enterprise Wi-Fi authentication method, such as EAP-TLS with digital certificates or PEAP with credentials.
- The server returns a decision. The RADIUS server sends an Access-Accept or Access-Reject response, depending on whether authentication succeeds.
- The device receives or is denied access. If authentication succeeds, the network allows the device to connect. If it fails, access is denied.
See your security gap before attackers do.
See continuous trust in action on a platform that includes RADIUS, PKI and AI security.
WPA2-PSK and WPA2-Enterprise: What’s the Difference?
WPA2-PSK and WPA2-Enterprise are different security protocols used to keep home and enterprise Wi-Fi networks secure. The following table illustrates some of the key differences between the two protocols.
|
Feature |
WPA2-PSK (Personal) |
WPA2-Enterprise |
|---|---|---|
|
Authentication |
Uses one shared Wi-Fi password. |
Verifies each user or device individually. |
|
Authentication method |
Pre-shared key (PSK). |
802.1X with EAP authentication. |
|
RADIUS server |
Not required. |
Required for standard 802.1X authentication. |
|
Access management |
Anyone with the password can connect. |
IT teams can manage access for individual users and devices. |
|
Password management |
The shared password must be changed for everyone if it is compromised. |
Individual credentials or certificates can be revoked without changing a shared network password. |
|
Security |
A leaked password can expose the network to unauthorized users. |
Provides stronger access control through individual authentication. |
|
Deployment |
Simple to configure and manage. |
Requires additional setup and authentication infrastructure. |
|
Best for |
Homes, small offices, and trusted devices. |
Businesses, schools, healthcare organizations, and large Wi-Fi networks. |
These, in addition to WPA3-PSK and WPA3-Enterprise, are the most commonly used Wi-Fi Protected Access (WPA) protocols. Here’s an explanation of each protocol and the environment they are typically used in.
WPA2-PSK
WPA2-PSK (Wi-Fi Protected Access 2 Pre-Shared Key) is a security protocol that protects a Wi-Fi network using a single password shared between all users. It’s generally accepted that a single password to access Wi-Fi is only safe if you trust all those using it. Otherwise, it’s trivial for someone who has obtained the password through nefarious means to infiltrate the network. This is why WPA2-PSK is often considered insecure.
There are only a few situations in which WPA2-PSK should be deployed:
- The network has just a few devices, all of which are trusted. This could be a home or small office.
- Admins are unable to deploy a captive portal but need a straightforward way to restrict casual users from joining an open network. This could be a coffee shop or guest network.
- Users want an alternative network for devices not compatible with 802.1X. An example is game consoles in a student dorm.
WPA3-PSK
WPA3-PSK offers greater protection than WPA2-PSK, thanks to an authentication process that uses Simultaneous Authentication of Equals (SAE) to make brute-force dictionary attacks far more difficult for a hacker. This protocol is designed to protect against offline dictionary attacks, causing a significant slowdown for those attempting to brute-force through the authentication process.
WPA2-Enterprise
Deploying WPA2-Enterprise requires a RADIUS server, which handles the task of authenticating network users’ access. The actual authentication process is based on the 802.1X policy and comes in several different systems labeled EAP. Because each device is authenticated before it connects, a personal, encrypted tunnel is effectively created between the device and the network.
The WPA2 (Enterprise) RADIUS combination affords networks strong security, especially when X.509 digital certificates are used for authentication. WPA2-Enterprise requires an 802.1X authentication server anyway, so it’s only logical to implement the best possible authentication security during configuration.
WPA3-Enterprise
A significant improvement that WPA3-Enterprise offers is a requirement for server certificate validation to be configured to confirm the identity of the server to which the device is connecting.
Interested in learning more about WPA3? Get the details about the changes WPA3 is poised to bring in this article.
How to Deploy WPA2-Enterprise and 802.1X
An 802.1X RADIUS server for Wi-Fi authentication is a core component of enterprise network security. Remote Authentication Dial In User Service (RADIUS) secures Wi-Fi by requiring a unique login for each user, as well as recording event logs and applying authorization policies.
There are just a few components that are needed to make 802.1X work. If you already have access points and some spare server space, you possess all the hardware needed to make secure wireless happen. Sometimes you don’t even need the server: some access points come with built-in software that can operate 802.1X (though only for the smallest of small deployments).
Regardless of whether you purchase professional solutions or build one yourself from open-source tools, the quality and ease of 802.1X is entirely a function of design.
The Components of 802.1X for WPA2-Enterprise Authentication
802.1X for WPA2-Enterprise uses three core components — the supplicant, the authenticator, and the authentication server — to exchange authentication messages before a device is granted network access, as the following diagram illustrates.
A fourth component, the identity store, supports the RADIUS server behind the scenes.
Client/Supplicant
In order for a device to participate in 802.1X authentication, it must have a piece of software called a supplicant installed in the network stack. The supplicant is necessary as it will participate in the initial negotiation of the EAP transaction with the switch or controller and package up the user credentials in a manner compliant with 802.1X.
If a client does not have a supplicant, the EAP frames sent from the switch or controller will be ignored and the switch will not be able to authenticate.
Info: Fortunately, almost all devices we might expect to connect to a wireless network have a supplicant built in. SecureW2 provides an 802.1X supplicant for devices that don’t have one natively.
Thankfully, the vast majority of device manufacturers have built-in support for 802.1X. The most common exceptions to this might be consumer gear, such as game consoles, entertainment devices or some printers. Generally speaking, these devices should be less than 10% of the devices on your network and are best treated as the exception rather than the focus.
Key Takeaway
- The client contains the user’s credentials and connects with the switch/controller to initiate the authentication process.
Switch / Access Point / Controller
The switch or wireless controller plays an important role in the 802.1X transaction by acting as a ‘broker’ in the exchange between the user device and the RADIUS server. Until a successful authentication, the client does not have network connectivity, and the only communication is between the client and the switch in the 802.1X exchange.
The switch/controller initiates the exchange by sending an EAP-Request/Identity packet to the client when the client connects to the network; the client can also start the exchange by sending an EAPOL-Start packet. The client’s responses are forwarded to the correct RADIUS server based on the configuration in the Wireless Security Settings.
When the authentication is complete, the switch/controller decides whether to grant network access based on the user’s status and possibly the attributes contained in the Access_Accept packet sent from the RADIUS server.
If the RADIUS server sends an Access Accept packet as the result of an authentication, it may contain certain attributes which provide the switch information on how to connect the device on the network. Common attributes will specify which VLAN to assign a user, or possibly a set of ACLs (Access Control Lists) the user should be given once connected.
This is commonly called ‘User–Based Policy Assignment’, as the RADIUS server is making the decision based on user credentials. Common use cases would be to push guest users to a ‘Guest VLAN’ and employees to an ‘Employee VLAN’.
RADIUS Server
RADIUS is an acronym for Remote Authentication Dial In User Service. It’s sometimes called an AAA server, which stands for Authentication, Authorization, and Accounting. RADIUS is a Wi-Fi security necessity – it replaces a single preshared key with unique credentials per user or device.
The on-premises or Cloud RADIUS server acts as the “security guard” of the network; as users connect to the network, the RADIUS authenticates their identity and authorizes them for network use.
A user becomes authorized for network access after enrolling for a certificate from the PKI (Public Key Infrastructure) or confirming their credentials. Each time the user connects, the RADIUS confirms they have the correct certificate or credentials and prevents any unapproved users from accessing the network.
A key security mechanism to employ when using a RADIUS is server certificate validation. This helps ensure that the user only connects to the network they intend to by configuring their device to confirm the identity of the RADIUS by checking the server certificate. If the certificate is not the one which the device is looking for, it will not send a certificate or credentials for authentication.
RADIUS servers can also be used to authenticate users from a different organization. Solutions like eduroam have RADIUS servers work as proxies (for example, connected over RadSec, which carries RADIUS over TLS) so that if a student visits a neighboring university, the RADIUS server can authenticate their status at their home university and grant them secure network access at the university they are currently visiting.
Identity Store
The Identity Store refers to the entity in which usernames and passwords are stored. In most cases, this is Active Directory, or potentially an LDAP server.
Almost any RADIUS server can connect to your AD or LDAP to validate users. There are a few caveats when LDAP is used, specifically around how the passwords are hashed in the LDAP server. If your passwords are not stored in cleartext or an NTLM hash, you will need to choose your EAP methods carefully as certain methods, such as EAP-PEAP, may not be compatible. This is not an issue caused by RADIUS servers, but rather from the password hash.
SecureW2 can help you set up SAML to authenticate users, on any Identity Provider, for Wi-Fi access. Here are guides to integrating with some popular products:
- To set up SAML authentication within Google Workspace, click here.
- To learn about configuring WPA2-Enterprise with Okta, click here.
- For a guide on SAML Authentication using Shibboleth, click here.
- To configure WPA2-Enterprise with ADFS, click here.
Developing a robust WPA2-Enterprise network requires additional tasks, like setting up a PKI or CA (Certificate Authority), to seamlessly distribute certificates to users.
Contrary to what you might think, you can make any of these upgrades without buying new hardware or making changes to your infrastructure. For example, rolling out guest access or changing the authentication method can be accomplished without additional infrastructure.
Recently, many institutions have been switching EAP methods from PEAP to EAP-TLS after seeing noticeable improvement in connection time and roaming ability or switching from a physical RADIUS server to a Cloud RADIUS solution. Improving the functionality of wireless networks can be gained without changing a single piece of hardware.
WPA2-Enterprise Protocols
Not all WPA2-Enterprise protocols offer the same level of protection; the chart below highlights the key differences.
|
WPA2 & WPA3 Enterprise Common Protocols |
Level of Encryption |
Authentication Speed |
Directory Support |
Credentials |
|---|---|---|---|---|
|
EAP-TLS |
Public-Private Key Cryptography |
Fast – 12 Steps |
Universal |
Passwordless |
|
PEAP-MSCHAPv2 |
Bad Encryption (MS-CHAPv2 reduces to a single DES encryption, cracked in 2012) |
Slow – 22 Steps |
Active Directory |
Passwords |
|
EAP-TTLS/PAP |
No Credential Encryption |
Slowest – 25 Steps |
Non-AD LDAP Servers |
Passwords |
What follows is a brief summary of the primary WPA2-Enterprise Authentication Protocols. If you’d like a more in-depth compare-and-contrast, read the full-length article.
EAP-TLS
EAP-TLS is a certificate-based protocol that is widely considered one of the most secure EAP standards because it eliminates the risk of over-the-air credential theft. It’s also the protocol that provides the best user experience, as it eliminates password-related disconnects due to password-change policies.
In the past, there was a misconception that certificate-based authentication was difficult to set up and/or manage, but now EAP-TLS is regarded by many to actually be easier to set up and manage than the other protocols.
Want to learn more about the advantages of EAP-TLS and how SecureW2 can help you implement it in your own network? Click the link!
EAP-TTLS/PAP
EAP-TTLS/PAP is a credential-based protocol that was created for an easier setup because it only requires the server to be authenticated, while client certificate authentication is optional. TTLS creates a “tunnel” between the client and the server and gives you multiple choices for authentication.
But TTLS includes many vulnerabilities. The configuration process can be difficult for inexperienced network users, and a single misconfigured device can result in significant loss to the organization. The protocol sends the password inside the TLS tunnel without any additional encryption, so a device that does not validate the server certificate can hand it to a man-in-the-middle, where it can be easily repurposed to accomplish the hacker’s goals.
Info: If you’d like to know more about the vulnerabilities of TTLS-PAP, read the full article here.
PEAP-MSCHAPv2
PEAP-MSCHAPv2 is a credential-based protocol that was designed by Microsoft for Active Directory environments. Although it’s one of the most popular methods for WPA2-Enterprise authentication, PEAP-MSCHAPv2 leaves devices vulnerable to over-the-air credential theft because it does not require the configuration of server-certificate validation.
Device misconfiguration, when left to end-users, is relatively common. That’s why most organizations rely on Onboarding Software to configure devices for PEAP-MSCHAPv2. Read how this top university converted from PEAP-MSCHAPv2 to EAP-TLS authentication to provide more stable authentication to network users.
Info: For more information on PEAP MSCHAPv2, read this article.
802.1X Authentication Methods for Enterprise Wi-Fi
Before users can be authenticated for network access day-to-day, they must be onboarded to the secure network. Onboarding is the process of reviewing and approving users so they can connect to the secure network using a form of identification, such as username/password or certificates.
This process often becomes a significant burden because it requires users to get their devices configured for the network. For regular network users, the process can prove to be too difficult because it requires high-level IT knowledge to understand the steps.
For example, universities experience this at the beginning of an academic year when onboarding hundreds or even thousands of student devices. This influx of students often results in long lines of support tickets.
Onboarding clients offer an easy-to-use alternative that enables end users to easily self-configure their devices in a few steps, saving users and IT admins a ton of time and money.
Password-Based Authentication
Most authentication methods rely on a username/password. Password-based authentication is easy to deploy, since most institutions already have credentials in place. However, without an onboarding system, the network is susceptible to all of the vulnerabilities associated with password-based access.
For password-based authentication, there are basically 2 options: PEAP-MSCHAPv2 and EAP-TTLS/PAP. They both function similarly, but TTLS is not supported by any Microsoft OS before Windows 8 without using a third-party 802.1X supplicant, such as our Enterprise Client.
At this point, most institutions have deployed or made the switch to PEAP. However, you can’t deploy PEAP without either using Active Directory (a proprietary Microsoft service) or leaving your passwords unencrypted.
Key Takeaway
- Over 80% of hacking-related breaches leveraged stolen and/or weak passwords. Consider moving towards certificate-based authentication.
Token-Based Authentication
Historically, tokens were physical devices in the form of key fobs or dongles that would be distributed to users. They generated numbers in sync with a server to add additional validation to a connection. Even though you can carry them around and utilize advanced features like fingerprint scanners or as USB plug-ins, dongles do have downsides. They can be expensive and are known to occasionally lose connection to the servers.
Physical tokens are still in use, but their popularity is waning as smartphones have made them redundant. What was once loaded onto a fob you can now put into an app. In addition, there are other methods for two-factor authentication outside of the EAP method itself, such as text or email confirmations to validate a device.
Certificate-Based Authentication
One of the key advantages of certificates is the richness of data they contain — as the comparison below makes clear.

Certificates have long been a mainstay of authentication, but they are not typically deployed in BYOD settings since certificates require users to install them on their own devices. However, once a certificate is installed, they are amazingly convenient as they:
- Are not affected by password change policies
- Are far safer than usernames/passwords
- Authenticate devices faster
The SecureW2 PKI services, combined with the JoinNow onboarding client, create a turnkey solution for certificate-based Wi-Fi. Our PKI provides all the necessary infrastructure to implement a certificate-based network and maintain the security and distribution of all network certificates. Organizations can now seamlessly distribute certificates to devices and manage them with ease using our powerful certificate management features.
Pros and Cons of WPA2–Enterprise
WPA2-Enterprise provides stronger Wi-Fi access control than WPA2-PSK by authenticating individual users or devices. However, it requires more infrastructure and configuration to deploy and manage.
Pros of WPA2–Enterprise
- Individual authentication: Each user or device authenticates separately, making it easier to identify who connects to the network.
- Centralized access management: IT teams can manage authentication and network access policies through a RADIUS server.
- Better access control: Administrators can revoke an individual user's credentials or certificate without changing a shared Wi-Fi password for everyone.
- Certificate-based authentication: WPA2-Enterprise supports EAP-TLS, which uses digital certificates to authenticate users and devices without relying on passwords.
- Improved network visibility: Authentication logs help IT teams investigate failed connections and monitor network access.
- Broad device compatibility: WPA2 is widely supported across enterprise access points and client devices, making WPA2-Enterprise a practical choice for organizations with mixed device environments.
Cons of WPA2–Enterprise
- More complex setup: Deployment requires compatible access points, a RADIUS server, and correctly configured authentication methods.
- Ongoing management: IT teams must manage user identities, certificates or credentials, device configurations, and authentication policies.
- Compatibility limitations: Some older or specialized devices may not support 802.1X authentication.
- Higher implementation costs: Organizations may need additional infrastructure, configuration work, or managed authentication services.
- Older security standard: WPA2 lacks some of the security improvements introduced by WPA3. Organizations should consider WPA3 when their access points and client devices support it, while assessing compatibility and migration requirements.
Simplifying WPA2-Enterprise With JoinNow
A properly configured WPA2-Enterprise network utilizing 802.1X authentication is a powerful tool for protecting the safety of network users and securing valuable data — but it’s just one piece of the puzzle. A truly secure and usable network depends on how all its components work together as a complete system.
If just the authentication method is secure while the configuration of managed devices is left to the average network user, there is a serious risk to the integrity of the network. SecureW2 recognizes that every facet of the wireless network must work in unison for ironclad security, so we’ve provided some turnkey concepts that every network administrator needs to consider in their network planning.
Efficiency Through Onboarding
Choosing the right onboarding client can make or break your WPA2-Enterprise deployment. This diagram shows how JoinNow Connector stacks up against the competition.

One of the greatest challenges for network administrators is efficiently and accurately onboarding users to the secure network. If left to their own devices, many users will misconfigure. Configuring for a WPA2-Enterprise network with 802.1X authentication is not a simple process and involves several steps that a person unfamiliar with IT concepts would not understand.
Warning: If users are not connecting to the secure SSID and are not properly set up for WPA2-Enterprise, the security benefits admins expect will be lost. For those that want the advantages that come with certificate-based networks, many opt to deploy an onboarding client that will automatically configure users’ devices.
Onboarding clients, such as the JoinNow Connector offered by SecureW2, eliminate the confusion for users by prompting them with only a few, simple steps designed to be completed by K-12 age students and up. The result is a properly configured WPA2-Enterprise network with 802.1X authentication that has successfully onboarded all network users to the secure network.
The best PKI solution provides self-service software for BYOD and unmanaged devices that automatically administers 802.1X settings.
Want more info on the advantages of a streamlined and secure Bring Your Own Device (BYOD) onboarding software? Check out this informative piece on onboarding!
Key Takeaway
- The best PKI solution provides self-service software for BYOD and unmanaged devices that automatically administers 802.1X settings.
Certificate-Hardened WPA2-Enterprise
A PKI enables organizations to use X.509 certificates and distribute them to network users. It consists of an HSM (Hardware Security Module), CAs, client, public and private keys, and a CRL (Certificate Revocation List). An effective PKI significantly bolsters network security, allowing organizations to eliminate password-related issues with certificate-based authentication.
Once the PKI is configured, users can begin enrolling for certificates. Certificate distribution can be a challenging task to complete, but organizations that use an onboarding client tend to have the most success.
SecureW2 provides all the tools needed for a successful managed PKI deployment and efficient distribution of certificates. After equipping their devices with a certificate, users are ready to be authenticated for the wireless network. Beyond secure wireless authentication, certificates can be used for VPN, Web application authentication, SSL Inspection security, and much more.
Our JoinNow Dynamic PKI supplies a robust framework for passwordless security to strongly authenticate devices, networks, and apps.
Key Takeaway
- Our JoinNow Dynamic PKI supplies a robust framework for passwordless security to strongly authenticate devices, networks, and apps.
WPA2-Enterprise Managed Device Configuration
Managing certificate deployment across dozens or hundreds of devices doesn’t have to be a manual process. The diagram below shows how it can be fully automated.
Enterprises with managed devices often lack a unified method of getting devices configured for certificate-driven security. Allowing users to self-configure often results in many misconfigured devices, and leaving the task to IT can be mountainous.
Configuring dozens, or sometimes even hundreds, of devices manually for a secure WPA2-Enterprise network is often considered too labor-intensive to be worthwhile. The SecureW2 advanced SCEP and WSTEP gateways provide a means to auto-enroll managed devices with no end user interaction. In one fell swoop, these gateways allow an IT department to configure managed devices from any major vendor for certificate-driven network security.
With the SecureW2 JoinNow API, you can use your device management platforms (including IoT) and MDM/EMM platforms to distribute and manage certificates.
Key Takeaway
- Use your device management platforms (including IoT) and MDM / EMM platforms via JoinNow’s APIs to distribute and manage certificates.
RADIUS Servers and Policy-Driven Access Control
The RADIUS server plays a critical role in the network, authenticating every device when it connects to the network. The SecureW2 JoinNow solution comes equipped with a world-class Cloud RADIUS server, providing powerful, policy-driven 802.1X authentication.
Backed by AWS, it delivers high availability, consistent and quality connections, and requires no physical installation. The server can be easily configured and customized to fit any organizations’ requirements, with no forklift upgrades of existing infrastructure required. Once fully integrated, the certificate-based network is ready to begin authenticating network users.
SecureW2 also offers an industry-first technology we call Dynamic Cloud RADIUS that allows the RADIUS to directly reference the directory – even cloud directories like Google, Microsoft Entra ID, and Okta. Instead of making policy decisions based on static certificates, the RADIUS makes runtime-level policy decisions based on user attributes stored in the directory.
Dynamic RADIUS is an enhanced RADIUS with better security and easier user management. Want to know more? Talk to one of our experts to see if your WPA2-Enterprise network can benefit from Dynamic RADIUS.
The keys to a successful RADIUS deployment are availability, consistency, and speed. SecureW2’s Cloud RADIUS equips organizations with the tools they need to make the secure network easy to connect to and always available so users are consistently protected from outside threats.
The security plan that scales with you.
Our solutions can scale from mid-market to global enterprises. Compare options and see how our solutions protect you from costly breaches and ensure peace of mind.
Secure Your Wireless Network With WPA2-Enterprise Authentication
WPA2-Enterprise with certificate-based authentication closes the gaps left permanently open by pre-shared keys. There are no shared secrets to rotate, no credentials exposed to phishing, and no opportunity for rogue devices to bypass a misconfigured RADIUS policy.
Our JoinNow platform enforces EAP-TLS across your wired and wireless infrastructure, connects RADIUS policy to live IdP and MDM data, and revokes access in seconds when a user offboards. If your wireless security still depends on passwords or shared keys, that’s the gap worth closing first.
See how SecureW2 secures wireless networks without passwords.
Frequently Asked Questions
What is a WPA2-Enterprise network?
The core difference between a WPA2-Enterprise Wi-Fi network and the type of Wi-Fi network you use at home is the method you use to authenticate. In a standard home Wi-Fi network, which uses WPA2-PSK, you enter a single password to gain access. This password is the same for all connected devices.
A WPA2-Enterprise network requires all devices to log into the Wi-Fi with unique credentials. This means that everyone either has their own username and password or they have their own digital certificate. It’s beneficial for a few reasons: it allows administrators more visibility over who’s connected to the network and can prevent the spread of compromise.
If one set of credentials is stolen, it’s easier to disconnect the associated device and deactivate those credentials than to disconnect all devices when the single password used in a PSK network is compromised. Without WPA2-Enterprise, organizations that offer network connectivity to large groups of users, like universities, are helpless to cease-and-desist letters when users illegally download copyrighted material, since they cannot associate network connections to users/devices.
What is required for a WPA2-Enterprise network?
A WPA2-Enterprise network typically needs a directory that contains all the individual user credentials for access and some way of authenticating those credentials or certificates as users and devices connect. One of the main differences between a WPA2-PSK network and a WPA2-Enterprise network is the use of an authentication server, also known as a RADIUS server.
Authentication servers are compatible with a number of authentication protocols. We recommend the Extensible Authentication Protocol with TLS (certificate-based authentication for wireless networks), because wired and wireless networks can be secured more rigorously with digital certificates, especially when their private keys are protected by hardware such as a trusted platform module (TPM).
Can a router be a RADIUS server?
Some routers can act as a RADIUS server; MikroTik RouterOS, for example, offers a RADIUS server package called User Manager. Running authentication on a dedicated RADIUS server or a cloud RADIUS service instead keeps it separate from routing.
How do I set up a RADIUS server as a Wi-Fi hotspot?
RADIUS servers cannot be used as Wi-Fi hotspots. By definition, a RADIUS server is a service whose function is to authenticate users and devices when they access your network. The RADIUS server is not itself an access point — it simply tells the access point to grant network access to authorized users.
How do I set up a wireless RADIUS server?
Setting up a wireless RADIUS server can vary depending on the APs you’re using and, of course, your RADIUS provider. With Cloud RADIUS, however, it’s relatively simple and can be completed in several steps:
- Create a RADIUS profile in your wireless controller.
- Navigate to AAA management, then AAA configuration in the SecureW2 Management Portal.
- Note the Primary IP Address, Port, and Shared Secret.
- Input this information into the RADIUS profile you created.
- Save the new RADIUS profile.
You can learn more about configuring RADIUS with an AP in one of our integration guides.
How does Wi-Fi RADIUS authentication work?
RADIUS can be described as a virtual bouncer at a virtual gate. When a user attempts to access your network, the RADIUS server checks that their credentials or certificates are valid by comparing them to a directory or Certificate Revocation List.
What is the benefit of RADIUS?
The main benefit to RADIUS is that it makes it possible for users to each use their own set of credentials to access the Wi-Fi or VPN, as opposed to sharing credentials. Individual credentials increase security, and if they’re stolen, the breach can be stopped by changing or revoking the single set of stolen credentials rather than all of them.
How do I set up WPA2-Enterprise at home?
In most home environments, WPA2-PSK (Wi-Fi access based on a single password) is sufficient. However, it is possible to set up WPA2-Enterprise at home if you have the expertise and are willing to invest more time, hardware, and maintenance into it.
You’ll need to establish a directory to keep user credentials in. For enterprise settings, this is almost always an Identity Provider such as Microsoft Entra ID or Google. Some devices may even allow you to enter in a few sets of credentials if you don’t want a separate database.
Additionally, you’ll need to establish a RADIUS server to authenticate all access requests and an access point that supports this type of authentication. You can find access points with RADIUS built into them, or use something sufficient for home use like pfSense or Microsoft NPS.
Keep in mind that this isn’t strictly necessary in the majority of home settings where Wi-Fi is used primarily for recreational purposes.
How do I connect to WPA2-Enterprise Wi-Fi?
From an end user’s perspective, connecting to a WPA2-Enterprise Wi-Fi network is mostly the same as connecting to Wi-Fi at home. They choose the network they want to connect to and enter a password or, if certificates are used, authenticate automatically with certificates. The authentication server responds with an ACCESS_ACCEPT or ACCESS_REJECT based on those credentials or certificates.
In an enterprise environment, connecting to WPA2-Enterprise Wi-Fi is often done automatically through an MDM (like Intune, Jamf, or Google). MDMs can send Network Profiles, which are essentially scripts that automatically configure a device for the necessary settings for WPA2-Enterprise, so end users don’t have to manually configure anything; they just open their laptop at work and they are connected.
How can certificates be used for Wi-Fi authentication?
With the right setup, certificates can completely replace passwords in Wi-Fi authentication. They allow administrators to leverage the information from their Identity Provider and apply that to their Wi-Fi access. Certificates can contain detailed information about each user and device which is retrieved from the Identity Provider at the time the user enrolls for a certificate.
Once they have a certificate, they may present the certificate to the RADIUS server when they connect to Wi-Fi instead of entering a password. The RADIUS then checks if the certificate is expired. With Cloud RADIUS, the authentication is taken a step further and the Identity Provider is checked in real-time during the authentication process to ensure the user exists in the IdP.