Somehow I'm managed to navigate the whitepapers and all the good/bad advice out there with relatively little hassle have a working WPA/802.1x/PEAP implementation against an IAS server in our AD. I've ...

The enterprise mode of WPA has always allowed you to give each user a unique username/password to login to the Wi-Fi or to utilize unique digital certificates for each user to install on devices for ...

The 802.1X category products (Avenda eTIPS, Enterasys NAC, HP ProCurve Identity Driven Manager, Juniper UAC, and to a lesser extent, Microsoft NAP and Symantec NAC) all actively participate in the ...

A recent story on "="" wi-fi="" networks"=""> that spoof legitimate hotspots or corporate networks makes it clear that all public hotspots should immediately implement 802.1x and PEAP authentication.

Is there such a beast? I've got a heterogenious environment (Linux, Windows, Solaris, VMware) with laptops, workstations and servers, and it's time to implement 802.1x. I'll probably start with the ...

In the NAC products we tested, authentication varies from very strong to very weak, and every point in-between. When starting down your path of evaluating NAC products, decide very early what kind of ...