Use Intel(R) PROSet/Wireless Software
Personal Security
Personal Security Settings
Set up Data Encryption and Authentication
Enterprise Security
Enterprise Security Settings
Network Authentication
802.1X Authentication Types
The following sections describe how to use Intel(R) PROSet/Wireless to set up the required security settings for your wireless adapter. See Personal Security.
It also provides information about how to configure advanced security settings for your wireless adapter. This requires information from a systems administrator (corporate environment) or advanced security settings on your access point (for home users). See Enterprise Security.
For general information about security settings, See Security Overview.
Use Personal Security if you are a home or small business user who can use a variety of simple security procedures to protect your wireless connection. Select from the list of security settings that do not require extensive infrastructure setup for your wireless network. A RADIUS or AAA server is not required.
NOTE: Personal Security options are unavailable in the Administrator Tool when creating Administrator Profiles for Windows Vista*
| Name | Setting |
|---|---|
|
Personal Security |
Select to open the Personal Security settings. The security settings that are available are dependent on the Operating Mode selected in the Create Wireless Profile Security Settings. Device to Device (ad hoc): In device to device mode, also called ad hoc mode, wireless computers send information directly to other wireless computers. You can use ad hoc mode to network multiple computers in a home or small office, or to set up a temporary wireless network for a meeting. NOTE: Device to Device (ad hoc) networks are identified with a notebook image ( Network (Infrastructure): An infrastructure network consists of one or more access points and one or more computers with wireless adapters installed. At least one access point should also have a wired connection. For home users, this is usually a broadband or cable network NOTE: Infrastructure networks are identified with an access point image ( |
|
Security Settings |
If you are configuring a Device to Device (ad hoc) profile, select one of the following data encryption settings:
If you are configuring a Network (Infrastructure) profile, select:
|
|
Advanced button |
Click to access the Advanced Settings and configure the following options:
|
|
Back |
View the prior page in the Profile Wizard. |
|
OK |
Closes the Profile Wizard and saves the profile. |
|
Cancel |
Closes the Profile Wizard and cancels any changes made. |
|
Help? |
Provides the help information for the current page. |
In a home wireless network you can use a variety of simple security procedures to protect your wireless connection. These include:
Wi-Fi Protected Access (WPA) encryption provides protection for your data on the network. WPA uses an encryption key called a Pre-Shared Key (PSK) to encrypt data before transmission. Enter the same password in all of the computers and access point in your home or small business network. Only devices that use the same encryption key can access the network or decrypt the encrypted data transmitted by other computers. The password automatically initiates the Temporal Key Integrity Protocol (TKIP) or AES-CCMP protocol for the data encryption process.
WEP encryption provides two levels of security:
For improved security, use a 128-bit key. If you use encryption, all wireless devices on your wireless network must use the same encryption keys.
You can create the key yourself and specify the key length (64-bit or 128-bit) and key index (the location that a specific key is stored). The greater the key length, the more secure the key.
Pass phrase (64-bit): Enter five (5) alphanumeric characters, 0-9, a-z or A-Z.
Hex key (64-bit): Enter 10 hexadecimal characters, 0-9, A-F.
Pass phrase (128-bit): Enter 13 alphanumeric characters, 0-9, a-z or A-Z.
Hex key (128-bit): Enter 26 hexadecimal characters, 0-9, A-F.
With WEP data encryption, wireless station can be configured with up to four keys (the key index values are 1, 2, 3, and 4). When an access point or a wireless station transmits an encrypted message that uses a key stored in a specific key index, the transmitted message indicates the key index that was used to encrypt the message body. The receiving access point or wireless station can then retrieve the key that is stored at the key index and use it to decode the encrypted message body.
In device to device mode, also called ad hoc mode, wireless computers send information directly to other wireless computers. You can use ad hoc mode to network multiple computers in a home or small office, or to set up a temporary wireless network for a meeting.
On the Intel(R) PROSet/Wireless main window, use one of the following methods to connect to a device to device network:
To create a profile for a wireless network connection with no encryption:
When WEP data encryption is enabled, a network key or password is used for encryption.
A network key is provided for you automatically (for example, it might be provided by your wireless network adapter manufacturer), or you can enter it yourself and specify the key length (64-bit or 128-bit), key format (ASCII characters or hexadecimal digits), and key index (the location where a specific key is stored). The greater the key length, the more secure the key.
To add a network key for a Device to Device (ad hoc) network connection:
To add a password or network key:
When WEP encryption is enabled on an access point, the WEP key is used to verify access to the network. If the wireless device does not have the correct WEP key, even though authentication is successful, the device is unable to transmit data through the access point or decrypt data received from the access point.
Name Description Password
Enter the Wireless Security Password (Pass phrase) or Encryption Key (WEP key).
Pass phrase (64-bit )
Enter five (5) alphanumeric characters, 0-9, a-z or A-Z.
WEP key (64-bit)
Enter 10 hexadecimal characters, 0-9, A-F.
Pass phrase (128-bit)
Enter 13 alphanumeric characters, 0-9, a-z or A-Z.
WEP key (128-bit)
Enter 26 hexadecimal characters, 0-9, A-F.
To add more than one password:
WPA Personal Mode requires manual configuration of a pre-shared key (PSK) on the access point and clients. This PSK authenticates a user's password or identifying code, on both the client station and the access point. An authentication server is not needed. WPA Personal Mode is targeted to home and small business environments.
WPA2 is the second generation of WPA security that provides enterprise and consumer wireless users with a high level of assurance that only authorized users can access their wireless networks. WPA2 provides a stronger encryption mechanism through Advanced Encryption Standard (AES), which is a requirement for some corporate and government users.
To configure a profile with WPA-Personal network authentication and TKIP data encryption:
If your wireless access point or router supports WPA2-Personal, then you should enable it on the access point and provide a long, strong password. The longer the password, the stronger the security of the wireless network. The same password entered in the access point needs to be used on this computer and all other wireless devices that access the wireless network.
NOTE: WPA-Personal and WPA2-Personal are interoperable.
Wi-Fi Protected Access (WPA) is a security enhancement that strongly increases the level of data protection and access control to a wireless network. WPA enforces 802.1X authentication and key-exchange and only works with dynamic encryption keys. For a home user or small business, WPA-Personal usess either Advanced Encryption Standard - Counter CBC-MAC Protocol (AES-CCMP) or Temporal Key Integrity Protocol (TKIP).
NOTE: For the Intel(R) Wireless WiFi Link 4965AGN adapter, to achieve transfer rates greater than 54 Mbps on 802.11n connections, WPA2-AES security must be selected. No security (None) can be selected to enable network setup and troubleshooting.
To create a profile with WPA2-Personal network authentication and AES-CCMP data encryption:
AES-CCMP (Advanced Encryption Standard - Counter CBC-MAC Protocol) is the new method for privacy protection of wireless transmissions specified in the IEEE 802.11i standard. AES-CCMP provides a stronger encryption method than TKIP. Choose AES-CCMP as the data encryption method whenever strong data protection is important.
If your Wireless access point or router supports WPA2-Personal, then you should enable it on the access point and provide a long, strong password. The same password entered into the access point needs to be used on this computer and all other wireless devices that access the wireless network.
NOTE: WPA-Personal and WPA2-Personal are interoperable.
Some security solutions may not be supported by your computer's operating system. You may require additional software or hardware as well as wireless LAN infrastructure support. Contact your computer manufacturer for details.
From the Security Settings page you can enter the required security settings for the selected wireless network.
Use Enterprise Security if your network environment requires 802.1X authentication.
| Name | Setting |
|---|---|
| Enterprise Security |
Select to open the Enterprise Security settings. |
| Network Authentication |
Select one of the following authentication methods:
|
| Data Encryption |
Click to open the following data encryption types: |
| Enable 802.1X (Authentication Type) | Click to open the following 802.1X authentication types: |
| Cisco Options | Click to view the Cisco Compatible Extensions.
NOTE: Cisco Compatible Extensions are automatically enabled for CKIP and LEAP profiles. |
| Advanced button | Select to access the Advanced Settings to configure the following options:
|
| User Credentials |
A profile configured for TTLS, PEAP, or EAP-FAST authentication requires one of the following log on authentication methods: Use Windows logon: The 802.1X credentials match your Windows user name and password. Before connection, you are prompted for your Windows logon credentials. NOTE: This option is unavailable if Pre-Logon Connect is not selected during installation of the Intel(R) PROSet/Wireless software. See Install or Uninstall the Single Sign On Feature. NOTE: For LEAP profiles, this option is listed as Use Windows logon user name and password. Prompt each time I connect: Prompt for your user name and password every time you log onto the wireless network. NOTE: For LEAP profiles, this option is listed as Prompt for the user name and password. Use the following: Use your saved credentials to log onto the network.
NOTE: Contact your administrator to obtain the domain name. NOTE: For LEAP profiles, this option is listed as Use the following user name and password. |
| Server Options |
Select one of the following credential retrieval methods: Validate Server Certificate: Select to verify the server certificate. Certificate Issuer: The server certificate received during TLS message exchange must be issued by this certificate authority (CA). Trusted intermediate certificate authorities and root authorities whose certificates exist in the system store are available for selection. If Any Trusted CA is selected, any CA in the list is acceptable. Click Any Trusted CA as the default or select a certificate issuer from the list. Specify Server or Certificate Name: Enter the server name. The server name or domain to which the server belongs. This depends on which option below has been selected.
NOTE: These parameters should be obtained from the administrator. |
| Certificate Options | To obtain a certificate for TLS authentication, select one of the following:
Use my smart card: Select if the certificate resides on a smart card. Use the certificate issued to this computer: Selects a certificate that resides in the machine store. Use a user certificate on this computer: Click Select to choose a certificate that resides on this computer. NOTE: Intel(R) PROSet/Wireless supports machine certificates. However, they are not displayed in the certificate listings. Notes about Certificates: The specified identity should match the Issued to identity in the certificate and should be registered on the authentication server (for example, RADIUS server) that is used by the authenticator. Your certificate must be valid with respect to the authentication server. This requirement depends on the authentication server and generally means that the authentication server must know the issuer of your certificate as a Certificate Authority. Use the same user name you used to log in when the certificate was installed. |
| Back | View the prior page in the Create Wireless Profile Wizard. |
| Next | View the next page in the Create Wireless Profile Wizard. If more security information is required then the next Step of the Security page is displayed. |
| OK | Closes the Create Wireless Profile Wizard and saves the profile. |
| Cancel | Closes the Create Wireless Profile Wizard and cancels any changes made. |
| Help? | Provides the help information for the current page. |
An infrastructure network consists of one or more access points and one or more computers with wireless adapters installed. Each access point must have a wired connection to a wireless network.
When Shared Key authentication is used, each wireless station is assumed to have received a secret shared key over a secure channel that is independent from the 802.11 wireless network communications channel. Shared key authentication requires that the client configure a static WEP or CKIP key. Client access is granted only if the client passes a challenge-based authentication. CKIP provides stronger data encryption than WEP, but not all operating systems and access points support it.
NOTE: While shared key would appear to be the better option for a higher level of security, a known weakness is created by the clear text transmission of the challenge string to the client. Once an invader finds the challenge string, the shared authentication key can be easily reverse engineered. Therefore, open authentication is actually, and counter intuitively, more secure. To create a profile with shared authentication:
Name Description Password Enter the Wireless Security Password (Pass phrase) or Encryption Key (WEP key).
Pass phrase (64-bit ) Enter five (5) alphanumeric characters, 0-9, a-z or A-Z.
WEP key (64-bit) Enter 10 hexadecimal characters, 0-9, A-F.
Pass phrase (128-bit) Enter 13 alphanumeric characters, 0-9, a-z or A-Z.
WEP key (128-bit) Enter 26 hexadecimal characters, 0-9, A-F.
WPA2-Enterprise requires an authentication server.
NOTE: WPA-Enterprise and WPA2-Enterprise are interoperable.
To add a profile that uses WPA-Enterprise or WPA2-Enterprise authentication:
EAP-SIM uses a dynamic, session-based WEP key, which is derived from the client adapter and RADIUS server, to encrypt data. EAP-SIM requires you to enter a user verification code, or Personal Identification Number (PIN), for communication with the Subscriber Identity Module (SIM) card. A SIM card is a special smart card used by Global System for Mobile Communications (GSM) based digital cellular networks. To add a profile with EAP-SIM authentication:
EAP-SIM authentication can be used with:
These settings define the protocol and the credentials used to authenticate a user. Transport Layer Security (TLS) authentication is a two-way authentication method that exclusively uses digital certificates to verify the identity of a client and a server.
To add a profile with TLS authentication:


TTLS authentication: These settings define the protocol and credentials used to authenticate a user. The client uses EAP-TLS to validate the server and create a TLS-encrypted channel between the client and server. The client can use another authentication protocol, typically password-based protocols. The challenge and response packets are sent over a non-exposed TLS encrypted channel. The following example describes how to use WPA with AES-CCMP encryption with TTLS authentication.
To set up a client with TTLS Network Authentication:
When 802.1X Microsoft IAS RADIUS is used as an authentication server, the server authenticates the device using the Roaming Identity from Intel(R) PROSet/Wireless software, and ignores the Authentication Protocol MS-CHAP-V2 user name. Microsoft IAS RADIUS accepts only a valid user name (dotNet user) for the Roaming Identity. For all other authentication servers, the Roaming Identity is optional. Therefore, it is recommended to use the desired realm (for example, anonymous@myrealm) for the Roaming Identity rather than a true identity.
PEAP authentication: PEAP settings are required for the authentication of the client to the authentication server. The client uses EAP-TLS to validate the server and create a TLS-encrypted channel between client and server. The client can use another EAP mechanism (for example, Microsoft Challenge Authentication Protocol (MS-CHAP) Version 2), over this encrypted channel to enable server validation. The challenge and response packets are sent over a non-exposed TLS encrypted channel. The following example describes how to use WPA with AES-CCMP or TKIP encryption with PEAP authentication.
To set up a client with PEAP Authentication:
Obtain and install a client certificate. See Set up the Client for TLS authentication or consult your administrator.
PEAP relies on Transport Layer Security (TLS) to allow unencrypted authentication types (for example, EAP-Generic Token Card (GTC) and One-Time Password (OTP) support).
When 802.1X Microsoft IAS RADIUS is used as an authentication server, the server authenticates the device using the Roaming Identity from Intel(R) PROSet/Wireless software, and ignores the Authentication Protocol MS-CHAP-V2 user name. Microsoft IAS RADIUS accepts only a valid user name (dotNet user) for the Roaming Identity. For all other authentication servers, the Roaming Identity is optional. Therefore, it is recommended to use the desired realm (for example, anonymous@myrealm) for the Roaming Identity rather than a true identity.
Configure Roaming Identity to Support Multiple Users
If you use a Pre-logon/Common profile that requires the roaming identity to be based on the Windows logon credentials, the creator of the profile can add a roaming identity that uses %username% and %domain%. The roaming identity is parsed and the appropriate log on information is substituted for the keywords. This allows maximum flexibility in configuring the roaming identity while allowing multiple users to share the profile.
Please See your authentication server user guide for directions about how to format a suitable roaming identity. Possible formats are:
- %domain%\%username%
- %username%@%domain%
- %username%@%domain%.com
- %username%@mynetwork.com
If Roaming Identity is cleared, %domain%\%username% is the default.
Notes about the credentials: This user name and domain must match the user name that is set in the authentication server by the administrator prior to client authentication. The user name is case-sensitive. This name specifies the identity supplied to the authenticator by the authentication protocol operating over the TLS tunnel. This user identity is securely transmitted to the server only after an encrypted channel has been verified and established.
Authentication Protocols: This parameter specifies the authentication protocols that can operate over the TTLS tunnel. Below are instructions on how to configure a profile that uses PEAP authentication with
GTC, MS-CHAP-V2 (Default), or TLS authentication protocols.

To configure a one-time password:
Name Description Static Password On connection, enter the user credentials. One-time password (OTP) Obtain the password from a hardware token device. PIN (Soft Token) Obtain the password from a soft token program.
NOTE: The Prompt each time I connect option is unavailable if an Administrator has cleared the Cache Credentials setting in the Administrator Tool. See Administrator Settings for more information.

This parameter specifies the authentication protocol operating over the PEAP tunnel.
Transport Layer Security authentication is a two-way authentication method that exclusively uses digital certificates to verify the identity of a client and a server.
If you did not select Use Windows logon on the Security Settings page and also did not configure user credentials, no credentials are saved for this profile. Please enter your credentials to authenticate to the network.
In the Application Settings, select Enable TLS rejected certificates notification, if you want a warning issued when a PEAP-TLS certificate is rejected. When a certificate has an invalid field expiration date, you are notified that you must take one of the following actions: A potential authentication problem for profile <profile name has been detected. The expiration date in the associated certificate may be invalid. Choose one of the following options:
| Control | Description | |
|---|---|---|
| Continue with current parameters. | Continue with the current certificate. | |
| Update certificate manually. | The Select Certificate page opens for you to choose another certificate. | |
| Update certificate automatically based on the certificates in the local store. | This option is enabled only when the local store holds one or more certificates for which the "issued to" and "issued by" fields match the current certificate and for which the "expiration date" has not expired. If you choose this option, the application selects the first valid certificate. | |
| Log off to obtain certificate during logon process (this does not update the profile and only applies to certificates configured for auto enrollment). | Logs off the user, who must obtain a proper certificate during the next logon process. The profile must be updated to select the new certificate. | |
| Auto enrollment | You are notified to: Please wait while the system is trying to obtain the certificate automatically. Click Cancel to end the certificate retrieval. | |
| Do not show this message again. | A user is able to avoid this step in subsequent sessions. The choice selected is remembered for future sessions. |
Cisco LEAP (Light Extensible Authentication Protocol) is an 802.1X authentication type that supports strong mutual authentication between the client and a RADIUS server. The LEAP profiles settings include LEAP, CKIP with Rogue AP detection integration. To set up a client with LEAP Authentication:


Cisco Options: Use to enable or disable Radio Management and Mixed Cells Mode or Allow Fast Roaming (CCKM).
NOTE: Cisco Compatible Extensions are automatically enabled for CKIP, LEAP or EAP-FAST profiles. To override this behavior, select or clear options on this page.
Enable Cisco Compatible Options: Select to enable Cisco Compatible Extensions for this wireless connection profile.
In Cisco Compatible Extensions, Version 3 (CCXv3), Cisco added support for EAP-FAST (Extensible Authentication Protocol-Flexible Authentication via Secure Tunneling), which uses protected access credentials (PACs) to establish an authenticated tunnel between a client and a server.
Cisco Compatible Extensions, Version 4 (CCXv4) improves the provisioning methods for enhanced security and provides innovations for enhanced security, mobility, quality of service, and network management.
To set up a client with EAP-FAST authentication with Cisco Compatible Extensions, version 3 (CCXv3):

NOTE: If CCXv4 Application Setting was not installed through an Administrator Package, only EAP-FAST User Settings are available for configuration. See EAP-FAST User Settings.
NOTE: If the provisioned PAC is valid, Intel(R) PROSet/Wireless does not prompt the user for acceptance of the PAC. If the PAC is invalid, Intel(R) PROSet/Wireless fails the provisioning automatically. A status message is displayed in the Wireless Event Viewer that an administrator can review on the user's computer.
To import a PAC:
- Click Select server to open the Protected Access Credentials (PAC) list.
- Click Import to import a PAC that resides on this computer or a server.
- Select the PAC and click Open.
- Enter the PAC password (optional).
- Click OK to close this page. The selected PAC is added to PAC list.
To perform client authentication in the established tunnel, a client sends a user name and password to authenticate and establish client authorization policy.
To set up a client with EAP-FAST authentication with Cisco Compatible Extensions, version 4 (CCXv4):
With CCXv4, EAP-FAST supports two modes for provisioning:
NOTE: Server-Authenticated Mode provides significant security advantages over Server-Unauthenticated Mode even when EAP-MS-CHAP-V2 is being used as an inner method. This mode protects the EAP-MS-CHAP-V2 exchanges from potential Man-in-the-Middle attacks by verifying the server’s authenticity before exchanging MS-CHAP-V2. Therefore, Server-Authenticated Mode is preferred whenever it is possible. EAP-FAST peer must use Server-Authenticated Mode whenever a certificate or public key is available to authenticate the server and ensure the best security practices.
EAP-FAST uses a PAC key to protect the user credentials that are exchanged. All EAP-FAST authenticators are identified by an authority identity (A-ID). The local authenticator sends its A-ID to an authenticating client, and the client checks its database for a matching A-ID. If the client does not recognize the A-ID, it requests a new PAC.
NOTE: If the provisioned Protected Access Credential (PAC) is valid, Intel(R) PROSet/Wireless does not prompt the user for acceptance of the PAC. If the PAC is invalid, Intel(R) PROSet/Wireless fails the provisioning automatically. A status message is displayed in the Wireless Event Viewer that an administrator can review on the user's computer.
NOTE: Server groups are only listed if you have installed an Administrator Package that contains EAP-FAST Authority ID (A-ID) Group settings.
PAC distribution can also be completed manually (out-of-band). Manual provisioning enables you to create a PAC for a user on an ACS server and then import it into a user's computer. A PAC file can be protected with a password, which the user needs to enter during a PAC import.
To import a PAC:
EAP-FAST CCXv4 enables support for the provisioning of other credentials beyond the PAC currently provisioned for tunnel establishment. The credential types supported include trusted CA certificate, machine credentials for machine authentication, and temporary user credentials used to bypass user authentication.
If you selected Use a certificate (TLS Authentication) and Use a user certificate on this computer, click Next (no roaming identity is required) and proceed to Step 3 to configure EAP-FAST Server certificate settings. If you do not need to configure EAP-FAST server settings, click OK to save your settings and return to the Profiles page.
If you selected to use a smart card, add the roaming identity, if required. Click OK to save your settings and return to the Profiles page.
If you did not select Use a certificate (TLS Authentication), click Next to select an Authentication Protocol. CCXv4 permits additional credentials or TLS cipher suites to establish the tunnel.
Authentication Protocol: Select either GTC, or MS-CHAP-V2 (Default).
GTC may be used with Server-Authenticated Mode . This enable peers using other user databases as Lightweight Directory Access Protocol (LDAP) and one-time password (OTP) technology to be provisioned in-band. However, the replacement may only be achieved when used with the TLS cipher suites that ensure server authentication.
To configure a one-time password:
Name Description Static Password On connection, enter the user credentials. One-time password (OTP) Obtain the password from a hardware token device. PIN (Soft Token) Obtain the password from a soft token program.
This parameter specifies the authentication protocol operating over the PEAP tunnel.
When 802.1X Microsoft IAS RADIUS is used as an authentication server, the server authenticates the device using the Roaming Identity from Intel(R) PROSet/Wireless software, and ignores the Authentication Protocol MS-CHAP-V2 user name. Microsoft IAS RADIUS accepts only a valid user name (dotNet user) for the Roaming Identity. For all other authentication servers, the Roaming Identity is optional. Therefore, it is recommended to use the desired realm (for example, anonymous@myrealm) for the Roaming Identity rather than a true identity.
Authenticated-TLS-Server Provisioning Mode is supported using a trusted CA certificate, a self-signed server certificate, or server public keys and GTC as the inner EAP method.
NOTE: If an Administrator Package was installed on a user's computer that did not apply the Cisco Compatible Extensions, Version 4 Application Setting, only EAP-FAST User settings are available for configuration.
To set up a client with EAP-FAST authentication:
Select the credential retrieval method:
EAP-FAST uses a PAC key to protect the user credentials that are exchanged. All EAP-FAST authenticators are identified by an authority identity (A-ID). The local authenticator sends its A-ID to an authenticating client, and the client checks its database for a matching A-ID. If the client does not recognize the A-ID, it requests a new PAC.
Click PACs to view any PACs that have already been provisioned and reside on this computer. A PAC must have already been obtained to clear Allow automatic provisioning on the Security Settings.
NOTE: If the provisioned Protected Access Credential (PAC) is valid, Intel(R) PROSet/Wireless does not prompt the user for acceptance of the PAC. If the PAC is invalid, Intel(R) PROSet/Wireless fails the provisioning automatically. A status message is displayed in the Wireless Event Viewer that an administrator can review on the user's computer.
PAC distribution can also be completed manually (out-of-band). Manual provisioning enables you to create a PAC for a user on an ACS server and then import it into a user's computer. A PAC file can be protected with a password, which the user needs to enter during a PAC import.
To import a PAC: