Chapter 7. Implementing and Configuring Advanced 802.1X

This chapter covers the following subjects:

• Plan the deployment of Cisco Advanced 802.1x authentication features: Learn what is involved in planning the deployment of advanced 802.1x features.

• Configure and verify EAP-TLS authentication on Cisco IOS components and Cisco Secure ACS: Learn how to configure EAP-TLS authentication in this section.

• Deploying user and machine authentication: Covers the deployment of user and machine authentication. You also learn when to use each of them.

• Deploying VLAN and ACL assignment: For granular control of user access, you can use dynamically assigned VLANs and ACL assignment.

• Configure and verify Cisco Secure ACS MAC address exception policies: Covers configuring MAC Authentication Bypass for your non-802.1X clients.

• Configure and verify web authentication on Cisco IOS Software LAN switches and Cisco Secure ACS: Web authentication is another method for authentication of non-802.1x clients. This section covers configuring and verifying web authentication.

• Choose a method to support multiple hosts on a single port: Covers the information needed for you to provide authentication support for multiple hosts on the same port.

• Configuring fail-open policies: Learn how to configure fail-open policies for times when the default fail-close policy does not apply to your environment.

• Resolve 802.1x compatibility issues: Covers what you can do to overcome incompatibility issues when deploying 802.1x authentication in your network.

Chapter 6, “Implementing and Configuring Basic 802.1X,” covered the basic configuration and troubleshooting of 802.1X authentication. Securing information assets is more important now than it has ever been in the past. Criminals have become more sophisticated in their types of attacks on organizations, and this requires the deployment of more advanced security features. This chapter discusses some advanced features of 802.1X authentication that will provide the capability to combat the newer, more prevalent attacks. The advanced 802.1X features will enhance basic authentication by adding things such as the use of certificates, machine authentication, automatic assignment of VLANs and ACLs, web authentication, and so on.

“Do I Know This Already?” Quiz

The “Do I Know This Already?” quiz helps you decide whether you really need to read the entire chapter. If you already intend to read the entire chapter, you do not necessarily need to answer these questions now.

The nine-question quiz, derived from the major sections in the “Foundation Topics” portion of this chapter, helps you determine how to spend your limited study time.

Table 7-1 outlines the major topics discussed in this chapter and the “Do I Know This Already?” quiz questions that correspond to those topics.

Table 7-1. “Do I Know This Already?” Foundation Topics Section-to-Question Mapping

image

Caution

The goal of self-assessment is to gauge your mastery of the topics in this chapter. If you do not know the answer to a question or are only partially sure of the answer, you should mark this question wrong for purposes of the self-assessment. Giving yourself credit for an answer that you correctly guess skews your self-assessment results and might provide you with a false sense of security.

1. To provide per-user services, such as downloadable ACLs, which of the following must be deployed? (Select all that apply.)

a. User authentication

b. Machine authentication

c. Combination of user and machine authentication

d. One-time passwords

e. All of these answers are correct.

2. In EAP-TLS implementations, which kind of certificate is used to verify identity certificates?

a. The identity certificate belonging to each entity

b. Supplicant certificate

c. Certificate Authority (CA) certificate

d. SSL certificate

3. What identifies the hardware (computer) as opposed to the user identity that is used to identify users that are logged in to the machine?

a. SNMP

b. Host name

c. CA certificate

d. User identity

e. Machine identity

4. Cisco IBNS components can dynamically assign what two features to increase security in the environment?

a. Physical tokens

b. Access controls lists (ACL)

c. Identity certificates

d. VLAN assignment

e. Kerberos ticket

5. If MAB is enabled, when will the switch try to authenticate the non-802.1X-capable client by using its MAC address?

a. As soon as the switch receives the first EAPOL frame.

b. After 802.1X authentication times out.

c. It will not authenticate non-802.1X-capable clients.

d. After the client sends an authentication request.

e. None of these answers are correct.

6. How can web authentication be verified?

a. Use show ip admission cache in the CLI.

b. Call the user and ask him.

c. In the Passed Authentication report in Cisco Secure ACS.

d. Consult the logs on the web server.

e. None of these answers are correct.

7. Which multihost authentication mode allows multiple hosts to forward traffic through a single port but does not require authentication after the first host authenticates?

a. Multidomain mode

b. Single-host mode

c. Multihost mode

d. Multi-auth mode

e. None of these answers are correct.

8. The default, fail-closed mode of the Cisco Catalyst IOS Software 802.1X authenticator can be changed by enabling which optional fail-open features?

a. Inaccessible Authentication Bypass feature

b. MAC Authentication Bypass

c. Open Authentication feature

d. Multi-auth mode

9. Which of the following will not work with 802.1X authentication by default? (Select all that apply.)

a. Wake-on-LAN (WOL)

b. Non-802.1X IP phones

c. Preboot Execution Environment (PXE)

d. None of these answers are correct.

The answers to the “Do I Know This Already?” quiz are found in Appendix A. The suggested choices for your next step are as follows:

• 6 or less overall score: Read the entire chapter. This includes the “Foundation Topics” and the “Exam Preparation” section.

• 7 through 9 overall score: If you want more review on these topics, skip to the “Exam Preparation” section. Otherwise, move on to Chapter 8, “Implementing and Configuring Cisco IOS Routed Data Plane Security.”

Foundation Topics

802.1X is an IEEE standard that provides a framework for authenticating and authorizing network devices connected to LAN ports and for preventing access in the event that the authentication and authorization fail. The authentication and authorization process requires a supplicant (client), an authenticator (router, switch, wireless AP, and so on), and an authentication server. In this chapter, advanced 802.1X features will be discussed. This chapter will discuss topics that enable additional security features on top of the basic 802.1X configurations that were covered in Chapter 6. The enhancements that will be covered include

• Configuring authentication of users and the network with certificate-based EAP-TLS

• Machine authentication

• Using VLANs or access control lists (ACL) to restrict authorization levels

• Providing support for multiple hosts on a single interface

• Providing support for non-802.1X devices

The Cisco Identity-Based Networking Services (IBNS) components on which these features will be configured will be the Cisco Catalyst IOS Software 802.1X authenticator, the Cisco Secure ACS 4.2 Server, and the Cisco Secure Services Client and Microsoft Windows wired 802.1X supplicants.

Plan the Deployment of Cisco Advanced 802.1X Authentication Features

The planning of Cisco 802.1X deployments is as important as the implementation. Information about your existing environment must be gathered, and some decisions must be made.

Gathering Input Parameters

Gathering important information about the environment into which 802.1X authentication will be deployed is needed to successfully deploy 802.1X on Cisco IBNS components. Information that you should gather includes the following:

image

• To use user or machine certificates, you should gather information about existing certificate architectures. Information about the existing Microsoft Active Directory or Public-Key Infrastructure (PKI) is important.

• Determine whether the deployment will employ user and/or machine authentication. This will help plan for certificate needs and Extensible Authentication Protocol (EAP) mode requirements.

• Determine any additional restrictions that will be deployed as part of the 802.1X authentication process, such as assigning VLANs or ACLs to users upon authentication.

• Gather a list of the types of clients that will be connecting to the network to determine if there are any non-802.1X-capable devices in the environment.

Deployment Tasks

Deploying advanced 802.1X authentication revolves around advanced EAP modes but includes several optional configuration items, including the following:

Step 1: Deploy advance EAP mode configurations.

Step 2: (Optional) Configure machine or machine and user authentication.

Step 3: (Optional) Configure authorization policies.

Step 4: (Optional) Configure features, if needed, to support non-802.1X host and special LAN features.

Deployment Choices

Choices must be made that depend upon an organization’s environment and architecture, including the following:

• Choice of EAP method: As with the basic 802.1X configuration discussed earlier, the EAP method that satisfies authentication requirements must be chosen. Consider the following scenarios:

• If the environment is one in which users and/or computers already have adequate certificates and a trusted certificate management process is in place, use Extensible Authentication Protocol–Transport Layer Security (EAP-TLS) (or, if you prefer inner and outer authentication layers, EAP-TLS tunneled inside Protected EAP [PEAP] or EAP–Flexible Authentication via Secure Tunneling [EAP-FAST]) as your authentication method.

• Similarly, if you want to build a new certificate infrastructure to provide a stronger authentication mechanism, use EAP-TLS (or, if you prefer inner and outer authentication layers, EAP-TLS tunneled inside PEAP or EAP-FAST) as your authentication method.

• Use EAP–Generic Token Card (EAP-GTC) tunneled inside PEAP if you prefer one-time passwords to authenticate users.

• To use static passwords and avoid EAP-FAST because of the complexities of PAC deployment in your environment, use EAP–Microsoft Challenge Handshake Authentication Protocol version 2 (EAP-MSCHAPv2) inside PEAP because it only requires configuration of ACS or root CA certificates on the clients.

• Type of authentication: Choose whether to require user or machine authentication. It is also possible to choose to require both user and machine authentication. Consider the following:

• Use machine authentication if you only need to tell the difference between a managed 802.1X machine and nonmanaged machines.

• Decide whether automatic assignment of VLANs or ACLs to users is required. If so, plan to authenticate users with a combination of machine and user authentication.

Configure and Verify EAP-TLS Authentication on Cisco IOS Components and Cisco Secure ACS

Extensible Authentication Protocol–Transport Layer Security (EAP-TLS) is a good authentication choice when there is a requirement for mutual authentication using identity certificates.

EAP-TLS consists of two parties that each have a certificate with which to identify themselves and a Certificate Authority (CA) certificate with which it verifies the certificates of other parties.

image

In an EAP-TLS 802.1X authentication exchange, there are two authenticating parties:

• Supplicant (client)

• Server (the network), which is the Cisco Secure ACS server

This means that the client is requesting authentication to access network resources, but it also authenticates the network as well, thus the term mutual authentication. Each party sends its identity certificate to the other party. It can then use its CA certificate to verify the identity certificate.

Upon successful authentication, the ACS server notifies the authenticator (the switch), which then authorizes the port on which the supplicant is connected. Figure 7-1 shows the supplicant, authenticator, and authentication server.

Figure 7-1. 802.1X Components

image

EAP-TLS with 802.1X Configuration Tasks

To configure EAP-TLS with 802.1X on Cisco IBNS components, complete the following tasks:

Task 1. Configure the Cisco IOS Software Catalyst switch authenticator and the RADIUS server (ACS).

Task 2. Install identity certificate and CA certificate on all clients.

Task 3. Install identity certificate and CA certificate on the Cisco Secure ACS server.

Task 4. Configure the Cisco Secure ACS server for EAP-TLS support.

Task 5. (Optional) Configure a network access profile to support EAP-TLS on the Microsoft Windows native 802.1X supplicant.

Task 6. (Optional) Configure a network access profile to support EAP-TLS on the Cisco Secure Services Client supplicant.

Configuration Scenario

The configuration scenario shown in Figure 7-2 illustrates the tasks needed to configure EAP-TLS. The client will either be using the Microsoft Windows native 802.1X supplicant or the Cisco Secure Services Client (CSSC) supplicant. The authenticator is running Cisco IOS Software and is configured with 192.168.254.1 as its management IP address. The client will use an identity certificate to authenticate to the ACS server and a CA certificate to verify the ACS server’s identity certificate. The ACS server will obtain its identity certificate from a Public Key Infrastructure (PKI) and use a CA certificate to verify the client’s identity certificate. The ACS server is at IP address 10.1.1.1. It is assumed that the RADIUS configuration exists on both the switch and the ACS server and that basic 802.1X port authentication is already configured on the switch, as discussed in the previous chapter.

Figure 7-2. Components in EAP-TLS with 802.1X Configuration

image

Configuration Choices

image

You have to make the following configuration choices when configuring EAP-TLS:

• The first decision is to determine what kind of identity certificate to use on the Cisco Secure ACS server. One option is to use a self-signed certificate, which is where the ACS server issues one to itself. The use of self-signed certificates should be limited to test scenarios because they must be manually imported to all clients and they are more difficult to revoke as compared to certificates obtained automatically from certificate servers. It is important to be able to revoke certificates in the event that the certificate becomes compromised by potential attackers. Obtaining identity certificates automatically by enrolling the ACS server with a certificate server provides automatic retrieval, renewal, and revocation of identity certificates.

• The second decision is whether to use one-way or two-way authentication inside EAP-TLS. One-way and two-way are also known as unidirectional and bidirectional, respectively. Unidirectional authentication involves the client being authenticated by the authentication server (ACS), but the client does not authenticate the authentication server. This can be acceptable in a highly trusted network, where other security controls are used to mitigate the possibility of interception and spoofing attacks. Because the client does not authenticate the ACS server, there is no need for provisioning certificate authority certificates to clients. This can make deployment and maintenance of EAP-TLS much easier, but it should not be used in environments that are not fully trusted. Bidirectional authentication should be used in production and other environments where there are no mitigating security controls in place.

Task 1: Configure RADIUS Server

The first task is to configure a RADIUS server on the authenticator (switch) and configure the authenticator (switch) as an authentication, authorization, and accounting (AAA) client on the RADIUS server. This task is the same as the procedure in the previous chapter. See Chapter 6 for details.

Task 2: Install Identity and Certificate Authority Certificates on All Clients

The procedure for installing identity certificates and CA certificates on clients is specific to the certificate authority and the client operating system. Consult the vendor documentation for this procedure.

Task 3: Configure an Identity Certificate on the Cisco Secure ACS Server

Task 3 includes the necessary steps to successfully create an identity certificate and a CA certificate on the Cisco Secure ACS server. There are two subsets of configuration steps for this task. The CA certificate will be used by the ACS server to validate client identity certificates. Configure the following items:

Step 1: Log on to the Cisco Secure ACS server with administrative privileges and navigate to System Configuration > ACS Certificate Setup > ACS Certificate Authority Setup.

Step 2: The CA certificate must be imported to the Cisco Secure ACS server. Obtain the certificate from the CA administrator in the form of a file. This should be the file that the CA used to provision client certificates. This is the CA certificate that the ACS server will use to verify client certificates. After you have the file, enter the full pathname to the file in the CA Certificate File field and click Submit to continue.

Step 3: This step, as shown in Figure 7-3, configures a Certificate Signing Request (CSR) by enrolling with the organization’s PKI:

a. Enter a unique X.500 name in the Certificate Subject field.

b. In the Private Key File field, specify the full pathname to the location where the ACS will store its private RSA key.

c. In the Private Key Password field, enter a strong password that will be used to encrypt the ACS server’s private key.

d. Re-enter the password in the Retype Private Key Password field.

e. Enter the length of the RSA private and public keys in the Key Length field. A key length of 2048 bits is recommended.

f. Specify the SHA-1 hashing algorithm in the Digest to Sign With field.

Figure 7-3. Generate Certificate Signing Request

image

Step 4: Click Submit to generate the Certificate Signing Request (CSR).

The CSR is a block of text that must be sent to the PKI to have a server identity certificate generated. The particular PKI in use will have procedures for importing a CSR and should then issue an identity certificate for the ACS server. The identity certificate should be in the form Base 64-encoded. After you have the identity certificate, refer to Figure 7-4 and follow these steps:

Step 1: Navigate to System Configuration > ACS Certificate Setup > Install ACS Certificate and select the Install New Certificate option. The ACS server should already have a self-signed certificate, but this will be overridden with the newly obtained PKI-issued certificate. There can be only one identity certificate.

Step 2: On the Install New Certificate page, choose the Read Certificate from File option and provide the full pathname to the location where the ACS identity certificate is stored. Also, in the bottom section, provide the path to the file containing the ACS server’s private key and the password to decrypt the file. These were configured in previous steps. Click the Submit button to continue.

Step 3: The ACS server will read the certificate and then install it. If the process is successful, the new certificate will be shown in the Installed Certificate Information section. Verify the Issued To and Issued By fields and make sure that Validity is set to OK.

Step 4: Restart the Cisco Secure ACS after installing a new certificate.

Figure 7-4. Install New Certificate in Cisco Secure ACS

image

Note

To restart the system, navigate to System Configuration > Service Control and click Restart. This does not reboot the server. It restarts the Cisco Secure ACS services.

Task 4: Configure Support of EAP-TLS on the Cisco Secure ACS Server

Task 4 configures support of EAP-TLS on the Cisco Secure ACS server. Task 4 is comprised of two subsets of steps. The first set configures EAP-TLS and some of its basic properties. The second set configures user accounts for comparison to identity certificates received from supplicants.

To configure EAP-TLS and some of its basic properties, follow these steps:

Step 1: Navigate to System Configuration > Global Authentication Setup.

Step 2: From the resulting screen shown in Figure 7-5, select the Allow EAP-TLS option in the EAP-TLS section of the Global Authentication Setup page.

Figure 7-5. EAP-TLS on Cisco Secure ACS

image

Step 3: Select the Certificate CN Comparison option in the EAP-TLS section to specify which field in the certificate will be compared against the ACS internal or external database. This step is to verify that the user specified in the client identity certificate does exist in an authentication database.

Step 4: Click Submit + Restart.

Next, you need to create the user account in the ACS internal database, as shown in Figure 7-6. Alternatively, you can use an external database such as Active Directory. Either way, the user account that is read from the client’s identity certificate must match an account that exists. Perform the following steps to create user accounts in the ACS internal database:

Step 1: Click User Setup, and the User Setup screen opens.

Step 2: In the User field, enter a unique name and click the Add/Edit button. The Edit User page opens. The username should match the format of the username in the identity certificate. For example, if the name in the certificate is in the user@domain.com format, the username created in ACS must also be created in that format.

Step 3: Even though the user’s password will never be used for EAP-TLS, because authentication is verified by certificates, enter a password in the user’s password field. The password chosen should be a strong password with adequate length in case the user account is ever used for an authentication purpose that uses the password.

Step 4: Click Submit.

Figure 7-6. User Setup in Cisco Secure ACS

image

Task 5: (Optional) Configure EAP-TLS Support Using the Microsoft Windows Native Supplicant

Task 5 provides the steps necessary to configure support of EAP-TLS on the Microsoft Windows native 802.1X supplicant. You can configure the supplicant to support EAP-TLS in the LAN adapter properties window, as shown in Figure 7-7. Perform the following steps to complete this task:

Step 1: Open the properties dialog box of the LAN adapter that will be authenticating using 802.1X, and then click the Authentication tab.

Step 2: On the Authentication tab, select the Enable IEEE 802.1X Authentication check box, choose the Smart Card or Other Certificate EAP type, and make sure that both the Authenticate as Computer When Computer Information Is Available and the Authenticate as Guest When User or Computer Information Is Available options are not selected.

Step 3: Click the Properties button to open the EAP-TLS properties window.

Step 4: Select the Use a Certificate on This Computer option.

Step 5: To enable bidirectional authentication and ensure that the client authenticates the network (authentication server), choose the Validate Server Certificate option.

Step 6: Select the Connect to These Servers option and enter the name in the canonical name (CN) field on the ACS server’s identity certificate.

Step 7: Find and select the installed CA certificate that issued the ACS certificate in the Trusted Root Certificate Authorities section.

Figure 7-7. Configure Windows Native 802.1X Client

image

The supplicant should now be configured to support authentication with EAP-TLS and 802.1X.

Task 6: (Optional) Configure EAP-TLS Support Using the Cisco Secure Services Client (CSSC) Supplicant

Task 6 provides the steps necessary to configure support of EAP-TLS on the CSSC 802.1X supplicant. The following steps show how to configure support of the 802.1X supplicant. Chapter 6 provided full guidance of CSSC profile configuration:

Step 1: In the Allowed Authentication Modes section, on the Authentication Policy page, select the EAP-TLS protocol as the outer EAP mode and leave all other choices deselected.

Step 2: On the User Authentication page, select EAP-TLS as the outer EAP mode. Click the Configure button to configure EAP-TLS-specific parameters.

Step 3: Select the Validate Server Certificate option in the EAP-TLS Settings window, as shown in Figure 7-8.

Figure 7-8. EAP-TLS on Cisco Secure Services Client

image

Step 4: The Enable Fast Reconnect option can be selected to allow reauthentication between the supplicant and the ACS server. Essentially the TLS session keys are cached, thus allowing faster reauthentication by not having to perform a full TLS handshake. This is an optional setting that must be configured on the ACS server and the supplicant if used.

Step 5: On the User Server Validating page, choose the Common Name value in the Certificate field, choose the Exactly Matches option in the Match field, and enter the name that exactly matches the canonical name (CN) as it was entered on the ACS identity certificate.

The supplicant should now be configured to support authentication with EAP-TLS and 802.1X.

Implementation Guidelines

Consider the following when deploying EAP-TLS:

• Using certificates to verify the authenticity of another party is much more demanding than other cryptographic methods that use passwords (EAP-MSCHAPv2 or EAP-FAST). The computational requirements placed on the ACS server will require that the platform be sized appropriately to handle the load.

• When using certificates, recommended practice dictates that both the ACS server and the clients be configured properly to use Certificate Revocation Lists (CRL). This will permit the device to automatically deny authentication requests that use expired or otherwise revoked certificates.

Feature Support

Minimum versions that support EAP-TLS features are v3.2 for Cisco Secure ACS and v4.0 for Cisco Secure Services Client (CSSC).

Verifying EAP-TLS Configuration

You can verify EAP-TLS authentication through the Passed Authentications report on Cisco Secure ACS. The report shows successful authentications of each 802.1X client and provides the username, MAC address, and 802.1X-enabled switch that is the authenticator. This report should be used to ensure that the client had the correct identity as well as the correct EAP mode.

Deploying User and Machine Authentication

Most of today’s current operating systems have a machine identity and user identities. Note that the user identities are plural while the machine identity is not. The machine identity identifies the hardware (computer), while the user identity is used to identify users that are logged in to the machine. Having multiple user identities is possible because most modern operating systems support multiple users.

The 802.1X supplicant has the capability to distinguish between a machine authenticating to the network and a user authenticating to the network. The different approaches to authenticating entities from the viewpoint of the supplicant are as follows:

• User authentication: This approach involves the user logging in to the machine, which in turn provides authenticated access to the network. If a user is not logged in (successfully authenticated), the machine cannot access network resources.

• Machine authentication: The computer has its own credentials, such as a password or certificate, with which it can authenticate itself to the network. The machine has access to the network even when there is no user logged in.

• User and machine authentication: This approach is a combination of both methods. The computer will be authenticated to the network using its credentials while there is no user logged in. When a user logs in, the machine authentication is revoked and the computer has access to the network through the user’s authentication. When the user logs out, the computer can once again authenticate itself using its own credentials.

When would you use machine authentication by itself, and when would you use user and machine authentication? Table 7-2 provides some guidelines to help you make that decision.

image

Table 7-2. Machine Authentication Versus User and Machine Authentication

image

Configuring User and Machine Authentication Tasks

The tasks that must be configured on Cisco IBNS components to support user and machine authentication are as follows:

Task 1. Install user and/or machine credentials (password or certificates) on client systems.

Task 2. Configure EAP-TLS features on Cisco Secure ACS.

Task 3. Configure support of machine authentication on the Cisco Secure ACS.

Task 4. (Optional) Configure support for machine (computer) authentication on the Microsoft Windows native 802.1X supplicant if required.

Task 5. (Optional) Configure support for machine (computer) authentication on the Cisco Secure Services Client (CSSC) 802.1X supplicant if required.

Task 6. (Optional) Configure user authentication in addition to machine authentication if a combination of both authentication methods is required.

Configuration Scenario

Figure 7-9 shows the configuration that will be used to accompany the configuration tasks that will be performed in this section.

Figure 7-9. Components and Sections of an EAP-TLS with 802.1X Authentication

image

Assume the following:

• Clients can automatically retrieve user and machine identity certificates from Active Directory certificate services.

• The Cisco Secure ACS has its identity certificate from PKI.

• EAP-TLS will be used for mutual authentication.

• RADIUS is configured on the switch and ACS server.

• EAP-TLS support is configured on the ACS server.

• Switch ports are configured with 802.1X port control.

Task 1: Install Identity and Certificate Authority Certificates on All Clients

The procedure for installing identity certificates and CA certificates on clients is specific to the certificate authority and the client operating system. Consult the vendor documentation for this procedure.

Task 2: Configure Support of EAP-TLS on Cisco Secure ACS Server

Task 2 configures support of EAP-TLS on Cisco Secure ACS Server. Task 2 is comprised of two subsets of steps. The first set configures EAP-TLS and some of its basic properties. The second set configures user accounts for comparison to identity certificates received from supplicants:

Step 1: Navigate to System Configuration > Global Authentication Setup.

Step 2: Select the Allow EAP-TLS option in the EAP-TLS section of the Global Authentication Setup page.

Step 3: Select the Certificate CN Comparison option in the EAP-TLS section to specify which field in the certificate will be compared against the ACS internal or external database. This step is to verify that the user specified in the client identity certificate does exist in an authentication database.

Step 4: Click Submit + Restart.

The second subset of tasks creates the user account in the ACS internal database. Alternatively, an external database such as Active Directory can be used. Either way, the user account that is read from the client’s identity certificate must match an account that exists. Use the following steps to create user accounts in the ACS internal database:

Step 1: Click User Setup, and the User Setup screen opens.

Step 2: In the User field, enter a unique name and click the Add/Edit button. The Edit User page opens. The username should match the format of the username in the identity certificate. For example, if the name in the certificate is in the user@domain.com format, the username created in ACS must also be created in that format.

Step 3: Even though the user’s password will never be used for EAP-TLS, because authentication is verified by certificates, enter a password in the user’s password field. The password chosen should be a strong password with adequate length in case the user account is ever used for an authentication purpose that uses the password.

Step 4: Click Submit.

Task 3: Configure Support of Machine Authentication on Cisco Secure ACS Server

Task 3 configures support of machine authentication and uses a Microsoft Active Directory external database to authenticate machine accounts.

Perform the following steps:

Step 1: Navigate to External User Databases > Unknown Uses Policy.

Step 2: Select the Check the Following External Databases option, and move the Windows database from the External databases pane to the Selected Databases pane.

Step 3: Navigate to External User Databases > Database Configuration > Windows Database > Configure and choose the Enable EAP-TLS Machine Authentication option.

Task 4: Configure Support of Machine Authentication on Microsoft Windows Native 802.1X Supplicant

Task 4 provides the steps necessary to configure machine authentication on the Microsoft Windows native 802.1X supplicant. The supplicant is configured in the LAN adapter properties window.

Perform the following steps:

Step 1: Open the properties dialog box of the LAN adapter that will be authenticating using 802.1X and click the Authentication tab.

Step 2: On the Authentication tab, select the Enable IEEE 802.1X Authentication check box, choose Smart Card or Other Certificate EAP type, and make sure that the Authenticate as Computer When Computer Information Is Available option is selected and that the Authenticate as Guest When User or Computer Information Is Available option is not selected.

Step 3: Click the Properties button to open the EAP-TLS properties window.

Step 4: Select the Use a Certificate on This Computer option in the When Connecting screen.

Step 5: To enable bidirectional authentication and ensure that the client authenticates the network (authentication server), select the Validate Server Certificate option, as shown in Figure 7-10.

Figure 7-10. Machine Authentication

image

Step 6: Select the Connect to These Servers option, and enter the name in the canonical name (CN) field on the ACS server’s identity certificate.

Step 7: Find and select the installed CA certificate that issued the ACS certificate in the Trusted Root Certificate Authorities section.

The supplicant should now be configured to support machine authentication.

Task 5: (Optional) Configure Machine Authentication Support Using the Cisco Secure Services Client (CSSC) Supplicant

Task 5 provides the steps necessary to configure the support of machine authentication on the CSSC 802.1X supplicant.

Perform the following steps:

Step 1: On the Network Connection Type page, select the option that makes this connection type a Machine Connection type, which will result in the supplicant performing only machine authentication without trying user authentication.

Step 2: On the Machine Authentication (EAP) Method page, select EAP-TLS as the protocol. Click the Configure button to configure EAP-TLS specific settings.

Step 3: Select the Validate Server Certificate option in the EAP-TLS Settings window. The Enable Fast Reconnect option can be selected to allow reauthentication between the supplicant and the ACS server. Essentially, the TLS session keys are cached, thus allowing faster reauthentication by not having to perform a full TLS handshake. This is an optional setting that must be configured on the ACS server and the supplicant if used.

Step 4: On the Machine Credentials page, select the Use Machine Credentials option to use the machine certificate that the ACS server obtained from the Active Directory Certificate Service.

The supplicant should now be configured to support authentication with EAP-TLS and 802.1X.

Task 6: (Optional) Configure Additional User Support Using the Cisco Secure Services Client (CSSC) Supplicant

Task 6 provides the steps necessary to configure additional user support on the CSSC 802.1X supplicant. This would be necessary if machine and user authentication is required.

Perform the following steps:

Step 1: From the Network Connection Type page, shown in Figure 7-11, select the option that makes this connection a Machine and User Connection type, which will result in the supplicant performing only machine and user authentication depending upon whether a user is logged in.

Figure 7-11. Deploy Machine and User Authentication

image

Step 2: On the User Authentication page, select EAP-TLS as the protocol.

Implementation Guidelines

Consider the following when deploying user and machine authentication:

• Using both authentication methods adds complexity to your authentication mechanism and to the resources needed to process authentication requests. Unless necessary, only use one or the other method, if possible.

• All the authentication configuration and other details covered thus far have been done under the assumption of a wired connection. The same configuration tasks can be extended to 802.11 wireless networks using the same EAP modes and authentication credentials.

Feature Support

Minimum versions to support machine and user authentication features are v3.1 for Cisco Secure ACS and all versions of the Cisco Secure Services Client (CSSC).

Deploying VLAN and ACL Assignment

Dynamic assignment of VLAN or ACL can be made possible through interaction between the Cisco Catalyst IOS Software–based switch and the Cisco Secure ACS server. The process of assigning a user to a specific VLAN or applying an ACL to that user’s access is handled by the ACS server. After 802.1X authentication is successful, these dynamic features are assigned to users by the ACS server sending the information to the authenticator (switch) in the form of a RADIUS attribute, and the switch enforces the assignments.

Deploying VLAN and ACL Assignment Tasks

image

The tasks to configure dynamic VLAN and ACL assignments are as follows:

Task 1. Configure Cisco IOS Software 802.1X authenticator authorization.

Task 2. (Optional) Configure VLAN assignment on a Cisco Secure ACS server.

Task 3. (Optional) Configure the Cisco IOS Software switch for ACL assignment.

Task 4. (Optional) Configure ACL assignment on a Cisco Secure ACS server.

Configuration Scenario

Figure 7-12 shows the configuration that will be used to accompany the configuration tasks that will be performed in this section.

Figure 7-12. Components and Sections of an EAP-TLS with 802.1X Authentication

image

Cisco Secure ACS will dynamically assign the client supplicant switch port to VLAN 10 and dynamically assign an ACL that allows HTTP, DNS, and PING access to the network to users in Group 1 of the ACS database.

Assume that the RADIUS configuration exists on both the switch and the ACS server and that basic 802.1X port authentication is already configured on the switch, as discussed in the previous chapter.

Configuration Choices

You have to make some choices when configuring VLAN and ACS assignment, including the following:

• Dynamic VLAN assignment should be used when there are other security controls in place in the environment to provide access control between the users and other resources.

• If the other security controls do not exist, consider using dynamic ACL assignment instead of or in addition to the dynamic VLAN assignment.

Task 1: Configure Cisco IOS Software 802.1X Authenticator Authorization

Task 1 provides the steps necessary to configure the 802.1X switch with basic authorization features. Consult the vendor documentation for this procedure.

Perform the following steps:

Step 1: Enable default network AAA authorization using the aaa authorization network default global configuration command. Example 7-1 shows how to configure the switch with global authorization to use the default RADIUS servers (group radius) to provide authorization to all 802.1X ports.

Example 7-1. Commands to Enable Default Network Authorization Using RADIUS


Router# configure terminal
Router(config)# aaa authorization network default group radius
Router(config)# exit
Router# copy running-config startup-config


Step 2: As an option, configure an access VLAN that has very restricted access. This will be the default VLAN assigned to clients if 802.1X is not configured on the switch or automatic VLAN assignment is not configured on the ACS server. Example 7-2 shows the commands for configuring the port in a default VLAN with limited access.

Example 7-2. Commands to Put Interface in Default Access VLAN


Router# configure terminal
Router(config)# interface range GigabitEthernet0/1-24
Router(config-if-range)# switchport access vlan 99
Router# copy running-config startup-config


Task 2: (Optional) Configure VLAN Assignment on Cisco Secure ACS

Task 2 provides the steps necessary to configure the optional assignment of VLAN membership for an interface that is authenticated by a user or group of users in ACS.

Perform the following steps:

Step 1: Enable VLAN assignment globally in the Cisco Secure ACS by including the option in the user interface. Log in to ACS with administrative access and choose Interface Configuration.

Step 2: From the Interface Configuration window, choose RADIUS (IEFT).

Step 3: Enable the following tunnel attributes for the group by selecting their check boxes in an ACS group profile:

• [064] Tunnel-type

• [065] Tunnel-Medium-type

• [081] Tunnel-Private-Group-ID

Step 4: Select the Submit button and restart Cisco Secure ACS to enable the changes.

Step 5: From the ACS home page, select Group Setup.

Step 6: On the Group Setup page, choose Group 1 and click Edit.

Step 7: On the Edit page, scroll down and find the IETF RADIUS Attributes section. Select the three tunnel attributes and complete their values as shown in IETF:

• Tunnel-Type (64), Tag 1 Value = VLAN

• Tunnel-Medium-Type (65), Tag 1 Value = 802

• Tunnel-Type (81), Tag 1 Value = 10

The value for the Tunnel-Type (81) is the name or number of the VLAN that is dynamically assigned to the interface upon successful authentication.

Task 3: (Optional) Configure and Prepare for ACL Assignment on Cisco IOS Software Switch

Task 3 provides the steps necessary to configure the optional assignment of an ACL to an authenticated entity. Several things must be accomplished on the switch, such as tuning RADIUS settings, enabling the IP device tracking feature, and assigning a default port to 802.1X-enabled user ports.

Perform the following steps:

Step 1: Enable default network AAA authorization with the aaa authorization network default global command.

Step 2: Configure the RADIUS client (switch) to send and also recognize vendor-specific attributes (VSA) that are needed for ACL assignment by using the radius-server vsa send authentication global configuration command.

Step 3: Enable the IP tracking feature, which is needed to learn and verify the presence of MAC and IP addresses on ports. This is done with the ip device tracking global configuration command.

Step 4: Configure and apply a default ACL using the ip access-group interface command. This default port ACL is required and will specify the traffic that is allowed by default on the port. At a minimum, it should allow Dynamic Host Configuration Protocol (DHCP) traffic.

Example 7-3 shows the commands discussed in this task being used to apply an ACL named “inbound-ACL” to interface FastEthernet 0/1 as well as the commands needed to enable ACL assignment.

Example 7-3. Preparing 802.1X Authenticator for Automatic ACL Assignment


Router# configure terminal
Router(config)# aaa authorization network default group radius
Router(config)# radius-server vsa send authentication
Router(config)# ip device tracking
Router(config)# interface FastEthernet0/1
Router(config-if)# ip access-group inbound-ACL in
Router(config)# end
Router(config)# copy running-config startup-config


Task 4: (Optional) Configure ACL Assignment on Cisco Secure ACS Server

Task 4 consists of two sets of steps. With the Cisco IOS Software authenticator prepared to receive downloadable ACLs, the Cisco Secure ACS server can now be configured. The first set of steps creates the downloadable ACL on Cisco Secure ACS, and the second set of steps configures assignment of the ACL for a group of users in Cisco Secure ACS. When configuring downloadable ACLs to be assigned to users upon authentication, always use any as the source IP address.

Perform the following steps:

Step 1: Create a downloadable ACL by logging in to Cisco Secure ACS as an administrator, navigating to Shared Profile Components > Downloadable IP ACLs, and then selecting Add to create a new ACL.

Step 2: On the Downloadable IP ACLs page, enter a name for the downloadable ACL (inbound-ACL is used in the example) and then click the Add button to add rules to the downloadable ACL.

Step 3: On the Downloadable IP ACLs page, as shown in Figure 7-13, enter a name for the first set of rules in the downloadable ACL and then enter the required access control elements (ACE) in the format of a Cisco IOS Software extended ACL in by clicking the Add button..

Figure 7-13. Downloadable ACLs on Cisco Secure ACS

image

Step 4: Click the Submit button to save the downloadable ACL.

The second set of rules will assign the downloadable ACL to a user or group of users in Cisco Secure ACS. The downloadable ACL has no size limitation except for that posed by the resource limitation of the authenticator to which it will be downloaded.

Perform the following steps:

Step 1: From the ACS home page, select Group Setup.

Step 2: On the Group Setup page, choose Group 1 and click Edit.

Step 3: On the Edit page, scroll down and find the Downloadable ACLs section, select the Assign IP ACL option, as shown in Figure 7-14, and select the downloadable ACL with the name that was used when creating the ACL.

Figure 7-14. Assign Downloadable ACL to a Group in Cisco Secure ACS

image

Step 4: Click the Submit button to save the configuration.

This completes the configuration for ACL assignment. You can test the assignment of the ACL by reauthenticating the users to the authenticator (switch).

Note

Downloadable ACLs are not the only way to assign an ACL to users or groups of users. Alternatively, an ACL that exists locally on the switch can be assigned. Downloadable ACLs are a better choice because they are easier to manage as they are centrally located on the ACS server as opposed to being on each switch.

Verification of VLAN and ACL Assignment with Cisco IOS Software CLI

To verify VLAN assignment, use the show vlan command to display port VLAN memberships. After the user has been authenticated by the Cisco Secure ACS server, the port should show membership in the correct dynamically assigned VLAN.

To verify ACL assignment, use the show epm session ip command with the argument of the user’s IP address to display the dynamically generated per-user ACL that is applied to the user’s session. The show access-list command can be used to display the contents of the assigned ACL. Example 7-4 shows the usage of both of these Cisco IOS Software commands.

Example 7-4. show vlan and show access-list Commands to Verify VLAN and ACL Assignment


Switch# show vlan

VLAN Name                          Status                            Ports
---- --------------------------- ------------------------------  ---------------
1    default                       active
10   USERS                         active                            Gi0/1


Switch# show epm sessions ip 192.168.254.3
Admission feature           : DOT1X
AAA Policies                :
ACS ACL                     : xACSACLx-IP-inboundACL-4b834e1a

Switch# show access-list xACSACLx-IP-inboundACL-4b834e1a
Extended IP access list xACSACLx-IP-inboundACL-4b834e1a (per-user)
          10 permit tcp any any eq www
          20 permit udp any host 172.16.1.10 eq domain
          30 permit icmp any any echo


Verification of VLAN and ACL Assignment on Cisco Secure ACS

Select the Downloadable ACL field in the Passed Authentications report to verify correct assignment to authenticating users.

Configure and Verify Cisco Secure ACS MAC Address Exception Policies

image

There will be cases in which devices that do not support 802.1X authentication will need network connectivity. Examples of these devices include printers, PDAs, or some operating systems that do not support 802.1X or possibly the EAP method that is deployed in an environment. There are several ways in which exceptions can be made for these devices:

• Disable 802.1X on ports where these devices will connect and assign the same VLAN to the port as the 802.1X users receive upon authentication. There is risk associated with this approach. Unless these devices are static and the ports are physically secured, anyone can disconnect his network connection and connect an unauthorized machine and receive unauthenticated access to network resources.

• Disable 802.1X on ports where devices will connect and assign a VLAN that has access restrictions. This is similar to the previous option but mitigates some of the risks associated with unauthorized connections.

• The decision to authenticate a device can be made based upon the MAC address of the device. This option has the risk of being susceptible to MAC address spoofing but can be used in conjunction with dynamic VLAN or ACL assignment as well.

• Utilize web-based authentication to have users authenticate using a web interface, which provides the opportunity to authenticate to gain access to network resources.

Cisco Catalyst IOS Software MAC Authentication Bypass (MAB)

The MAC Authentication Bypass (MAB) configuration enables the switch to authorize clients based on their client MAC address. If MAB is enabled, the switch will try to authenticate the client by using MAB after the 802.1X authentication times out because of failure to receive the EAP response from the client.

With MAB enabled, the switch uses the client’s MAC address as the client identity. The authentication server has a database of MAC addresses that are allowed to access the network against which the client’s MAC address will be checked. When a device connects to a port on which 802.1X is configured, it will wait for an Ethernet packet from the client. The switch will send a RADIUS access/request frame with a username and password that are based on the MAC address to the authentication server. Successful authorization results in the switch granting access to the client, whereas a failed authorization results in the switch either assigning the port to a guest VLAN if one exists or the switch does not grant access to the client.

Reauthentication of clients is possible for clients that authenticate using MAB. The process is the same as it is for 802.1X clients. The Session-Timeout RADIUS attribute is used as the basis of reauthentication; the authorization period ends and connectivity will be lost to the client during reauthentication.

If an EAP over LAN (EAPOL) packet is received on a port that was authenticated using MAC Authentication Bypass, the switch determines that the connected client is an 802.1X supplicant and will use 802.1X to authorize the interface. If the interface is already authorized using MAB and detects an 802.1X supplicant, the client will not be deauthorized and disconnected. The switch will use 802.1X at the time of reauthentication instead of MAB.

image

MAB will interact with the following features:

• 802.1X authentication: MAB can be enabled only if 802.1X authentication is enabled on the port.

• Guest VLAN: If a client has an invalid MAC address ID, the switch will assign the user to the guest VLAN if one exists.

• Restricted VLAN: Restricted VLANs are not supported for a client that authenticates through MAB on a port configured for 802.1X authentication.

• Port security: MAB can be used in conjunction with port security.

• Voice VLAN: MAB can be used along with voice VLANs.

• VLAN Membership Policy Server (VMPS): 802.1X and VMPS are mutually exclusive and, therefore, not used together.

• Private VLANs (PVLAN): It is possible to place a port in a PVLAN and then configure it for MAB.

Configuration Tasks

The tasks that are required to configure MAB exception policies are as follows:

Task 1. Configure MAB on the authenticator (switch).

Task 2. Configure MAB on Cisco Secure ACS.

Configuration Scenario

Figure 7-15 depicts the scenario used in the configuration tasks that follow. In this scenario, Cisco Secure ACS will permit a host with a MAC address of 000a.3453.cf2d to bypass the 802.1X authentication process. The switch and ACS are configured with their RADIUS association, EAP is enabled and configured, and the access ports on the switch are configured with 802.1X port control.

Figure 7-15. Network Topology for Configuration Scenario

image

Tasks 1 and 2: Configure MAC Authentication Bypass on the Switch and ACS

The steps that are required to configure MAB exception policies on the switch are as follows:

Step 1: Enter either interface or interface range configuration mode on the switch.

Step 2: Use the authentication order command to set the order of authentication processes on the interfaces. In the example, the switch will first perform a MAB check based on the client’s MAC address and falls back to normal 802.1X EAP if needed.

Step 3: Use the mab interface configuration command to enable the MAC Authentication Bypass feature.

Building a database of MAC addresses can be a challenging part of setting up MAB on the ACS server. If the number of hosts is relatively small, it might be feasible to simply add them individually to the Cisco Secure ACS internal database:

Step 1: Click User Setup on the navigation pane from the ACS home page.

Step 2: Enter the MAC address of the device without any symbols or special characters in the User field. Click the Add/Edit button.

Step 3: Enter the MAC address of the device without any symbols or special characters in the Password and Confirm Password fields.

Step 4: Click the Submit button when finished to create the MAC address-based user.

There are several ways that are beyond the scope of this material to populate the Cisco Secure ACS internal database with MAC address–based user accounts if the number of hosts is too large for manual entry, including

• Creating the MAC database by using existing ACS tools

• Creating the MAC database from log files

• Creating the MAC database using third-party tools

Verification of Configuration

To verify operation of MAB on the Cisco Catalyst IOS Software switch, use the show authentication interface command. On the ACS server, you can verify MAB by checking the Passed Authentication to find the hosts using MAC address to authenticate.

Implementation Guidelines

image

Consider the following guidelines when deploying MAB in your environment:

• Ensure that users cannot use the MAB credentials (MAC address) to authenticate to other processes, such as logging on to network devices. The Network Access Restriction feature can be configured on the Cisco Secure ACS to limit this access.

• If MAB is placed before 802.1X authentication in the interface configuration, it will optimize the speed of MAB authentication at the expense of excess load on the ACS server because the ACS server must answer two queries from the user (a MAB query and an EAP query). Ensure that the ACS servers are sized appropriately.

• Consider that you can use the guest VLAN and the restricted/authentication failed VLAN when both MAB and 802.1X fail for a user.

• When adjusting 802.1X EAPOL timers to optimize authentication speed, be careful to not be too aggressive because this could allow 802.1X-capable machines to authenticate using MAB before 802.1X can respond to EAPOL identity requests.

In addition to the authentication order command, the authentication priority command can be used to choose a preferred authentication method over another. An example would be to use the authentication order command to first perform MAB and then 802.1X, but the authentication priority command would prefer the 802.1X authentication result over the MAB authentication result. These advanced configurations are beyond the scope of this study guide. See the “Flexible Authentication Order, Priority, and Failed Authentication” white paper for more information. The link is located in the “References.”

Configure and Verify Web Authentication on Cisco IOS Software LAN Switches and Cisco Secure ACS

The web authentication feature puts in place a web-based access control on an 802.1X network. Web authentication can be used in conjunction with 802.1X authentication or as a replacement for 802.1X authentication for hosts that do not support it. One method is to configure the port to try 802.1X authentication first and then use web authentication if the client has no 802.1X supplicant.

The web authentication process is as follows:

• The user is allowed basic DHCP connectivity on a port configured with a restrictive ACL.

• The user’s HTTP session is intercepted by the authenticator (the switch).

• The user authenticates to the AAA server and is assigned a per-user ACL.

Note

The VLAN of the port cannot be changed with web authentication.

After an 802.1X EAP Request/Identity times out, the switch will put a preconfigured ACL on the port to control access to the network until the web authentication is successful. The switch intercepts the user’s HTTP request and redirects the browser to a login page that is provided by the switch. Upon successful authentication, the switch downloads the per-user ACL from the Cisco Secure ACS server and adds it to the existing ACL. The browser then redirects the user to the original URL. Reauthentication takes place when the client does not respond to an Address Resolution Protocol (ARP) probe for Layer 2 interfaces and when the client does not send traffic within the idle timeout for Layer 3 interfaces.

If the web authentication fails, the user is presented with a Login-Fail web page that prompts the user to retry the login attempt.

Configuration Tasks

Deploying web authentication on Cisco IBNS components consists of the following tasks:

Task 1. Configure web authentication support on the authenticator (switch).

Task 2. Configure web authentication support on Cisco Secure ACS.

Configuration Scenario

Figure 7-16 shows the process involved in web authentication:

In this scenario, the switch will assign users that cannot authenticate using 802.1X to the guest VLAN of 700 (not shown). The port will be configured with an ACL that only permits DHCP requests. Cisco Secure ACS will use a unique group for web authentication users and assign an ACL to successfully authenticated users that allow HTTP access to 172.16.1.80 and DNS access to 172.16.1.53. User authentication will use a password as its authentication credential. Assumptions include that the switch and ACS are configured for RADIUS, that the EAP method is enabled, and that the basic 802.1X port control is already in place.

Figure 7-16. Web Authentication Scenario

image

Task 1: Configure Web Authentication on the Switch

In Task 1, support of web authentication will be enabled on the 802.1X authenticator switch, and local AAA and RADIUS parameters will be configured. Also, the switch HTTP server, IP device tracking, and web authentication interception will be enabled. Perform the following steps:

Step 1: Log in to the switch and enter global configuration mode.

Step 2: Enable default AAA login authentication using the aaa authentication login default global configuration command and set it to use the local RADIUS client. In the example, the switch will use all the configured RADIUS servers in the default group (group-radius).

Note

It is recommended that any changes to the AAA configuration be made from a console connection until connectivity can be verified after making the changes. It is extremely easy to lock yourself out of a router/switch when modifying AAA configurations.

Step 3: Enable default AAA authorization for the auth-proxy that is used by web authentication. It is enabled with the aaa authorization auth-proxy default global configuration command. In the example, the switch will use all the configured RADIUS servers in the default group (group-radius).

Step 4: Configure the local RADIUS client to send and recognize vendor-specific attributes (VSA) required for dynamic ACL assignment using the radius-server vsa send authentication global configuration command.

Step 5: Configure a new IP admission ruleset for proxy HTTP using the ip admission name command in global configuration command. The example uses the WEBAUTH name for this ruleset.

Step 6: Enable the HTTP server on the switch using the ip http server command.

Step 7: Enable IP tracking, which is required to learn and periodically verify the existence of hosts’ MAC and IP addresses on interfaces. This is enabled with the ip device tracking global configuration command.

Step 8: On all 802.1X ports, enable web authentication as the last method using the webauth and authentication order interface commands. Configure a default input ACL that permits minimal traffic (restrict to DHCP) using the ip access-group interface command and apply the IP admission ruleset using the ip admission interface command.

Example 7-5 shows the command usage from Steps 1–5.

Example 7-5. Web Authentication on Cisco Catalyst IOS Software Switch


Router# configure terminal
Router(config)# aaa authentication login default default group radius
Router(config)# aaa authorization auth-proxy default group radius
Router(config)# radius-server vsa send authentication
Router(config)# ip admission name WEBAUTH proxy http
Router(config)# ip http server
Router(config)# ip device tracking
Router(config)# interface range GigabitEthernet0/1 - 24
Router(config-if)# authentication order mab dot1x webauth
Router(config-if)# ip access-group DEFAULT-ACL in
Router(config-if)# ip admission WEBAUTH


Task 2: Configure Web Authentication on the Cisco Secure ACS Server

In Task 2, user accounts that are to be used by web authentication users will be configured on the Cisco Secure ACS server. The accounts are the same as other accounts except for the ACL that will be downloaded to the switch to provide additional access to web authentication users:

Step 1: Log in to the Cisco Secure ACS with administrative privilege.

Step 2: Navigate to the Edit Settings page in Group Setup for the group being configured.

Step 3: Scroll down to the Cisco IOS/PIX 6.X RADIUS Attributes section and select the [009/001] cisco-av-pair option. In the Attributes Content field, enter the following to enforce the desired policy (web access to 172.16.1.80 and DNS access to 172.16.1.53):

• Priv-lvl=15 to enable the execution of the following commands at the enable levels.

• Multiple proxyacl lines with a sequence number. Each proxyacl line represents a line (access control element [ACE]) in the dynamic ACL that is applied to the interface upon authentication. The syntax is proxyacl#sequencenumber=ACE.

Web Authentication Verification

In the CLI on a Cisco IOS Software device, the show ip admission cache command will show the client’s IP address. In the Cisco Secure ACS, consult the Passed Authentication report to see authentication records (logs) of web authentication users.

User Experience

When the user sends an HTTP request to the web server, the switch intercepts the user’s HTTP session request and presents the user with a pop-up dialog box that has a username and password field. After being authenticated successfully, the user is redirected to the original URL that was requested.

Choose a Method to Support Multiple Hosts on a Single Port

To support scenarios in which there might be more than one host per 802.1X port, Cisco Catalyst IOS Software provides several 802.1X authenticator modes:

• Default single-host mode: The authenticator authorizes the port and allows only the authenticated host’s MAC address to forward traffic through the port.

• Multihost mode: The switch allows multiple hosts on a port where all MAC addresses are allowed to forward traffic after the first host authenticates.

• Multi-auth mode: The switch allows multiple hosts on a port, but each host must authenticate individually by using EAPOL to authenticate to the network.

• Multidomain mode: The switch allows multiple hosts on a port that are in multiple VLANs (a trunk port), such as a user computer and an IP phone.

Multiple Hosts Support Guidelines

Each of these modes supports various requirements. Some examples are provided to assist in determining which authentication mode is appropriate for a given set of requirements. The default single-host mode is for when there will only be a single host on each switch port. Multihost mode is used when there are several hosts per port and they are all considered authenticated by virtue of the initial authentication. This mode is appropriate for supporting virtual machines running in bridged mode.

The multi-auth mode is essentially for when there is another multiport device such as a hub connected to the port that is configured with 802.1X authentication port control. The “secondary” multiport device cannot be a switch unless it has the capability to forward EAPOL frames. Typically a switch will not forward EAPOL frames. Finally, multidomain authentication mode is to support IP phones that require the use of trunking to allow separate VLANs for the IP phone and the user’s computer on the same switch port.

Configuring Support of Multiple Hosts on a Single Port

The default single-host mode requires no additional configuration.

Configuring multihost mode requires using the dot1x host-mode multi-host interface command. It is also recommended to use port security to limit the number of additional hosts that are allowed to forward traffic based off of the initial host’s authentication. Example 7-6 shows its usage.

Example 7-6. Configuring Multihost Authentication Mode


Router# configure terminal
Router(config)# interface FastEthernet0/1-24
Router(config-if)# dot1x host-mode multi-host
Router(config-if)# switchport port-security
Router(config-if)# switchport port-security maximum 3
Router(config-if)# switchport port-security aging time 1
Router(config-if)# end
Router# copy running-config startup-config


Configuring multi-auth mode requires using the dot1x host-mode multi-auth interface command. Implementing port security with this mode in unnecessary because all hosts must authenticate to gain access to network resources. Example 7-7 shows its usage.

Example 7-7. Configuring Multi-Auth Authentication Mode


Router# configure terminal
Router(config)# interface FastEthernet0/1-24
Router(config-if)# dot1x host-mode multi-auth
Router(config-if)# end
Router# copy running-config startup-config


Configuring multidomain mode requires using the dot1x host-mode multi-domain interface command. Example 7-8 shows its use along with configuring VLAN 10 for the data VLAN and VLAN 20 for IP phone traffic.

Example 7-8. Configure Multihost Authentication Mode


Router# configure terminal
Router(config)# interface FastEthernet0/1-24
Router(config-if)# dot1x host-mode multi-domain
Router(config-if)# switchport access vlan 10
Router(config-if)# switchport voice vlan 20
Router(config-if)# end
Router(config)# copy running-config startup-config


Note

Prior to Release 12.2(33) SXI, the interface command to configure support for multiple hosts on a single port was the dot1x host-mode interface command. After Release 12.2(33) SXI, the authentication host-mode command replaced the dot1x host-mode command.

Configuring Fail-Open Policies

The Cisco Catalyst IOS Software 802.1X authenticator will, by default, not allow traffic to traverse a port that is not in the authorized state. RADIUS server failures, network outages, or any other reason that prevents a user from being authenticated will cause the port to remain in the unauthorized state.

This default, fail-closed mode can be changed to enable an optional fail-open behavior. This can be helpful in certain situations:

• Critical ports: For parts of the network that have unreliable connectivity to the RADIUS server and the risk of authentication failure exists, a permanent solution involves enabling the Inaccessible Authentication Bypass feature, which can authorize access to critical ports. This feature will place an interface in the authorized state if all configured RADIUS servers are unreachable.

• Open Authentication: Fail-open policies can alternatively be temporarily enabled, for example, during deployment, to work out any problems with the deployment. The Open Authentication feature implements this by allowing 802.1X verification without enforcing any access control on ports that fail to authorize.

image

Configuring Critical Ports

With the Inaccessible Authentication Bypass feature enabled, the switch checks the availability of the configured RADIUS servers. The switch will authenticate the user if a server is available. If none of the servers are available, the switch allows network access by placing the port in critical authentication state. The port must have transitioned to “critical” state to bypass authentication. The behavior of this bypass feature depends on the authorization state of the interface:

• If a host connected to a critical port tries to authenticate while the port is unauthorized and no RADIUS server is available, the switch puts the port in critical authentication state and places the port in the user-specified access VLAN.

• If the port is already authorized and a host attempts reauthentication, the switch places the port in the critical authentication state in the current VLAN, which could be the VLAN previously assigned by a RADIUS server.

• If the switch loses connectivity with the RADIUS server in the middle of an authentication attempt, the exchange will time out and the switch will put the interface in critical authentication state during the next authentication attempt.

When using the Inaccessible Authentication Bypass feature, consider using a special VLAN with access that is restricted to only critical assets.

Perform the following steps to configure ports as critical and enable Inaccessible Authentication Bypass:

Step 1: (Optional) Use the authentication critical recovery delay global configuration command to optionally set the time the switch will wait to reinitialize a port when a previously unavailable RADIUS server becomes available. The example sets this duration to 2 seconds.

Step 2: Label the port as critical and authorize the port to a specific VLAN using the authentication event server dead action authorize vlan interface configuration command.

Step 3: (Optional) Configure the port to reauthenticate immediately when a RADIUS server becomes available again using the authentication event server alive reinitialize interface configuration command.

Example 7-9 shows how to configure Inaccessible Authentication Bypass.

Example 7-9. Configure Critical Ports


Router# configure terminal
Router(config)# authentication critical recovery delay 2000
Router(config)# interface FastEthernet0/1-24
Router(config-if)# authentication event server dead action authorize vlan 10
Router(config-if)# authentication event server alive action reinitialize
Router(config-if)# end
Router(config)# copy running-config startup-config


The Inaccessible Authentication Bypass feature interacts with other features in the following ways:

• Guest VLAN: Inaccessible Authentication Bypass is compatible with guest VLANs. The interactions are

• If at least one RADIUS server is reachable, the switch assigns a host to the guest VLAN if it does not receive a response to its EAP Request/Identity frame or when there are no EAPOL packets from the client.

• If no RADIUS server is available and the client is connected to a critical port, the switch authenticates the client and puts the interface in the critical authenticated state and in the user-specified access VLAN.

• If no RADIUS server is available and the client is not connected to a critical port, the switch assigns hosts to the guest VLAN if one is configured.

• If no RADIUS server is available and the client is connected to a critical port and was previously assigned to the guest VLAN, the switch will keep the port assigned to the guest VLAN.

• Restricted VLAN: If no RADIUS server is available and the interface is already authorized in a restricted VLAN, the switch puts the interface in the critical authentication state and leaves it in the restricted VLAN.

• 802.1X accounting: Accounting will not be affected by the RADIUS server being unreachable.

• PVLAN: Inaccessible Authentication Bypass can be configured on a PVLAN port as long as the VLAN is a secondary PVLAN.

• Voice VLAN: Inaccessible Authentication Bypass is compatible with voice VLANs, but the access VLAN and voice VLAN must be different.

• RSPAN: The Remote SPAN (RSPAN) VLAN should never be configured as the access VLAN on an interface configured with Inaccessible Authentication Bypass.

Configuring Open Authentication

Open authentication assists with deploying a Cisco IBNS 802.1X solution more smoothly. It is typically used temporarily and only during the initial implementation phase. However, it can be considered as an alternative to Inaccessible Authentication Bypass for locations with unstable connectivity to the RADIUS infrastructure. If this feature is deployed permanently, consider using per-user ACLs that provide additional access upon authentication.

To enable open authentication, use the authentication open interface configuration command.

Resolve 802.1X Compatibility Issues

There are several situations in which configuring 802.1X authentication on a switch port can create unanticipated problems. Cisco IOS Software provides solutions that can fix these issues.

image

Wake-on-LAN (WOL)

Wake-on-LAN is a networking standard that defines a specific type of packet, known as a “magic” packet, that allows a computer to be turned on or “woken” up upon receiving this magic packet. Switch ports that have 802.1X port control configured on them will not allow traffic to pass through an interface that is in the unauthorized state. The computer cannot wake up to authenticate, but yet it cannot receive that packet that is intended to wake it up. Cisco Catalyst IOS Software provides a solution to this by configuring an interface as unidirectionally controlled by using the authentication control-direction in interface command. In this configuration, the switch will still not allow ingress packets to traverse unauthenticated ports but will allow egress packets to flow through them. This allows the magic packet to be received and “wake up” the host. Example 7-10 shows the command in use.

Example 7-10. Configure Interface as Unidirectionally Controlled


Router# configure terminal
Router(config)# interface FastEthernet0/1-24
Router(config-if)# authentication control-direction in
Router(config-if)# end
Router(config)# copy running-config startup-config


Non-802.1X IP Phones

Most Cisco IP Phones support an 802.1X supplicant, enabling them to authenticate to the network using multidomain authentication on switch ports, as discussed earlier in this chapter. As depicted in Example 7-11, you can use multidomain authentication with MAB to authenticate these non-802.1X IP phones based on their MAC addresses.

Example 7-11. Multidomain Authentication with MAB


Router# configure terminal
Router(config)# interface FastEthernet0/1-24
Router(config-if)# dot1x host-mode multi-domain
Router(config-if)# switchport access vlan 10
Router(config-if)# switchport voice vlan 20
Router(config-if)# mab
Router(config-if)# end
Router(config)# copy running-config startup-config


Preboot Execution Environment (PXE)

Computers that are in a Preboot Execution Environment (PXE) need to use access to the network to boot themselves from a network resource. Switch ports configured with 802.1X port control will not let the necessary traffic pass because of the port being in an unauthorized state. Cisco Catalyst IOS Software provides two possible solutions to this:

• Use open authentication with a default ACL, as shown in Example 7-12, that permits network boot traffic and then further restricts the traffic with a per-user downloadable ACL that will be applied after successful authentication.

• Use MAB to initially authenticate the computer based on its MAC address, and use authentication order and authentication priority to prefer 802.1X authentication after the 802.1X supplicant is running.

Example 7-12. Configure Interface as Unidirectionally Controlled


Router# configure terminal
Router(config)# interface FastEthernet0/1-24
Router(config-if)# authentication open
Router(config-if)# ip access-group DHCP-PXE in
Router(config-if)# end
Router(config)# copy running-config startup-config


Exam Preparation

As mentioned in the section, “How to Use This Book,” in the Introduction, you have several choices for exam preparation: the exercises here, the memory tables in Appendix D, the final exam preparation chapter, and the exam simulation questions on the CD-ROM. The following questions present a bigger challenge than the exam itself because they use an open-ended question format. By using this more difficult format, you exercise your memory better and prove your conceptual and factual knowledge of this chapter. You can find the answers to these questions in Appendix A, “Answers to the DIKTA Quizzes and Fill in the Blanks Questions.”

Review All Key Topics

Review the most important topics in this chapter, noted with the Key Topics icon in the margin of the page. Table 7-3 lists a reference of these key topics and the page numbers on which each is found.

Table 7-3. Key Topics

image

Complete Tables and Lists from Memory

Print a copy of Appendix C, “Memory Tables” (found on the CD), or at least the section for this chapter, and complete the tables and lists from memory. Appendix D, “Memory Table Answers,” also on the CD, includes completed tables and lists to check your work. Although there were no memory tables in this chapter, you will find some for other chapters.

Define Key Terms

Define the following key terms from this chapter, and check your answers in the Glossary:

mutual authentication

supplicant

Public-Key Infrastructure (PKI)

public key cryptography

Certificate Signing Request (CSR)

Certificate Authority (CA) certificate

user certificate

machine certificate

Fill in the Blanks

  1. The _____ and _____ do not both authenticate to the network at the same time. _____ authentication is only needed when the user logs off.
  2. With the _____ optional EAP-TLS parameter, the TLS session keys are essentially cached, thus allowing faster reauthentication by not having to perform a full TLS handshake.
  3. The _____ command can be used to choose a preferred authentication method over another.
  4. When the user sends an _____ request to the web server, the switch intercepts the user’s HTTP session request and presents the user with a pop-up dialog box that has a username and password field.
  5. Beginning with _____ of Cisco IOS Software, the dot1x host-mode command was replaced with the _____ command.
  6. When configuring fail-open policies, label an interface as critical by using the _____ interface configuration command.
  7. To handle Wake-on-LAN devices in an 802.1X environment, configure the interface as _____ by using the _____ interface command.
  8. Use the _____ with _____ to authenticate non-802.1X IP phones based on their MAC addresses.

References

Cisco IOS Security Configuration Guide: Securing User Services, Release 12.4T, www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/12_4T/sec_securing_user_services_12.4t_book.html.

Cisco IOS Security Command Reference - 12.4, www.cisco.com/en/US/docs/ios/security/command/reference/sec_book.html.

Cisco IOS Security Command Reference - 15.0M, www.cisco.com/en/US/partner/docs/ios/security/command/reference/sec_book.html.

Cisco IOS Security Configuration Guide: Securing User Services, Release 15.0, www.cisco.com/en/US/partner/docs/ios/sec_user_services/configuration/guide/15_0/sec_user_services_15_0_book.html.

Configuring IEEE 802.1X Port-Based Authentication - Cisco IOS Configuration Guide 12.4, www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_cfg_ieee802_pba_ps6441_TSD_Products_Configuration_Guide_Chapter.html.

Catalyst 6500 Release 12.2SXH and Later Software Configuration Guide: Configuring IEEE 802.1X Port-Based Authentication, www.cisco.com/en/US/partner/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/dot1x.html.

Flexible Authentication Order, Priority, and Failed Authentication, www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6586/ps6638/application_note_c27-573287_ps6638_Products_White_Paper.html.