{"id":38980,"date":"2021-02-23T13:58:39","date_gmt":"2021-02-23T05:58:39","guid":{"rendered":"https:\/\/version-2.com\/?p=38980"},"modified":"2021-09-25T11:37:53","modified_gmt":"2021-09-25T03:37:53","slug":"enterprise-wifi-authentication-explained","status":"publish","type":"post","link":"https:\/\/version-2.com\/en\/2021\/02\/enterprise-wifi-authentication-explained\/","title":{"rendered":"Enterprise WiFi Authentication, Explained"},"content":{"rendered":"
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

\n\"Gartner<\/p>\n\n

Types of WiFi Authentication<\/h2>\n

There are several different methods for authenticating wireless clients. Some have fallen out of favor due to security weaknesses, ultimately being replaced with newer, more secure authentication methods. These include :<\/p>\n

    \n
  • Open authentication to the access point<\/li>\n
  • Shared key authentication to the access point<\/li>\n
  • EAP authentication to the network<\/li>\n
  • MAC address authentication to the network<\/li>\n
  • Combining MAC-based, EAP, and open authentication<\/li>\n
  • Using CCKM for authenticated clients<\/li>\n
  • Using WPA key management<\/li>\n<\/ul>\n

    WiFi Authentication Challenges<\/h2>\n

    From its outset, WiFi posed a unique challenge when it came to authenticating identities since users were no longer physically connecting to ethernet ports. Originally, there were several methods used to authenticate users across wireless networks:<\/p>\n

      \n
    1. Separation:<\/strong> One was to separate the WiFi network and enable it to access the Internet. If you needed to access on-prem applications or resources, you would VPN into the network just as if you were remote. In this case the solution for WiFi authentication was the implementation of the SSID and password which was shared across any users of that particular network. In this case, there wasn\u2019t really a connection to the main network even though the WiFi network was located alongside the internal network. It operated more as a separate network for a variety of reasons.<\/li>\n
    2. SSID:<\/strong> Another path is to simply leverage an SSID and passphrase and let anybody on the network that has that. Subsequently the user could authenticate to the directory service, but even if they failed the authentication, they would still have access to the WiFi network.<\/li>\n
    3. RADIUS Authentication:<\/strong> Yet, another path was to leverage the RADIUS authentication protocol to auth access to the WiFi network which would subsequently authenticate access with Active Directory. The RADIUS server was the intermediary between the WiFi access point and the core identity provider. RADIUS was able to speak to the WiFi access points and then translate for the directory to authenticate user access. Of course, the downside of this approach was more servers, more integration, and more configuration on end user devices.<\/li>\n<\/ol>\n

      WiFi Authentication with Portnox CLEAR<\/h2>\n

      WiFi extends beyond your walls. Employees harmlessly share company WiFi passwords with guests, contractors, business neighbors without ever stopping to think about the network and information security risks this poses to their organization. It\u2019s not just outsiders, however. Today, nearly 20% of SMBs experience a data breach by a former employee who still has WiFi access.<\/p>\n

      It\u2019s never been easier to secure your WiFi. With Portnox\u2019s WiFi Security-as-a-Service, complex integrations and RADIUS server setups that traditionally required skilled IT staff and extensive training have been eliminated. Now, you can set-up user and device authentication that comply with security regulations in minutes.<\/p>\n

      Watch How it Works<\/h3>\n