Is 802.1x the Answer?

The 802.1x standard requires that data encryption under the RC4 algorithm use 128-bit keys—rather than 40-bit keys. These longer keys prevent passive eavesdropping attacks and other intrusions. Also, the system will be able to manage and rotate WEP encryption keys on a per-session basis. Such rotation prevents key theft or impersonation: Attackers will be unable to gather enough data to obtain a keystream.

The 802.1x standard encompasses existing, proven protocols such as Extensible Authentication Protocol (EAP), Remote Authentication Dial-In User Service (RADIUS), and Transport Layer Security (TLS). EAP lets wireless clients use a single sign-on (SSO) to authenticate to RADIUS servers. (Networks running RADIUS are in for an easy integration.) TLS provides for mutual authentication; integrity-protected, cipher-suite negotiation; and key exchange between two endpoints.

The 802.1x standard blocks any networking activity until after a successful user authentication occurs. One criticism of the 802.11 standard is that a security vulnerability exists for a short time while the system authenticates the user.

The 802.1x standard will preclude the necessity to use one vendor for wireless client hardware. Moreover, wireless users won't need to have a WEP key flashed onto their wireless LAN (WLAN) cards, so corporations can use Windows wireless services to support more than one wireless NIC standard.

The 802.1x standard makes no fundamental changes to the 802.11 WLAN standard. Therefore, companies that already have a WLAN in place will be able to make a smooth transition.