Nail Down Client Configurations
Managing client configurations is critical. Left on their own, employees will adjust their laptops to access public hot spots or home wireless routers. Enterprises can manage their clients through configuration control, usage policy and dedicated client software.
Since Windows XP laptops ship with an internal wireless network adapter that automatically tries to attach to available WLANs, it's important to change the adapter's network properties from allowing ad hoc connections. Furthermore, administrators need to disable Wireless Auto Configuration, install XP Service Pack 2, which supports WPA and fixes several wireless security flaws, and change dangerous default settings, such as the administrative password.
Mad Science not only restricts use of the wireless client, but also locks down its mobile machines through user privileges, preventing the installation of applications.
"Our users aren't allowed to do anything to reconfigure their wireless client," says Alszko. "That doesn't mean they aren't going to try."
Meanwhile Peregrine uses client software specific to its ...
To continue reading for free, register below or login
To read more you must become a member of SearchSecurity.com

Fortress Access Control Server to guarantee that only clients installed by Willis and his team can connect to the WLAN.
Define and Enforce Policy
A detailed acceptable-use policy is the foundation of a sound wireless security program. For example, Mortgage Financial is selective about who gets VPN access.
"If you want to connect to the network remotely, a request is submitted for a VPN client. The VPN client is deployed only after reviewing the environment and if the user meets the criteria," says Beaupre. This ensures everyone connects through a gateway that verifies the correct encryption level is being used and the antivirus definitions are current.
Because of the rapid changes in wireless technologies, WLAN policies need to be dynamic. Organizations should revisit the policy and educate wireless users regularly.
Issues routinely covered by written policies should include the type of encryption to be used for authentication, acceptable use policy (corporate access points only vs. public networks), procedures in the event a device is lost or stolen, and the consequences for violating policies.
|
 |
|