Chapter 5. 802.1X and Cisco Identity-Based Networking Services (IBNS)

This chapter covers the following subjects:

• Identity-Based Networking Services (IBNS) and IEEE 802.1x overview: Describes Cisco IBNS and IEEE 802.1x and discusses how IBNS extends on 802.1x.

• 802.1x internetworking: Covers the detailed interworking of the 802.1x specification.

• EAP type selection: Covers the most commonly used EAP types that are deployed.

Cisco Identity-Based Networking Services (IBNS) is a technology framework for delivering logical and physical network access authentication. IBNS combines several Cisco products that offer authentication, user policies, and access control to provide a comprehensive solution for increasing network access security. An identity-based network (IBN) incorporates capabilities defined in the IEEE 802.1x standard. The 802.1x standard is a framework defined by the IEEE 802.1 working group to provide a standard link layer protocol for port-based access control and authentication.

This chapter discusses IBNS and 802.1x features and functionality.

“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 ten-question quiz, derived from the major sections in “Foundation Topics” section of this chapter, helps you determine how to spend your limited study time.

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

Table 5-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. Which of the following is a framework defined by the IEEE 802.1 working group that provides a standard link layer protocol for port-based access control and authentication?

a. 802.1q

b. 802.11b

c. 802.1x

d. 802.1w

2. What are the three roles the IEEE 802.1x framework defines in the authentication process?

a. Authentication server

b. Administrator

c. Authenticator

d. Supplicant

e. Client

f. Object

3. Prior to the client authentication, which protocols are allowed to pass through a port? (Select three.)

a. EAPOL

b. RADIUS

c. CDP

d. TACACS+

e. SNMP

f. Spanning Tree Protocol (STP)

4. Which of the following are valid IBNS deployment modes?

a. Monitor Mode

b. High-Security Mode

c. Low-Security Mode

d. Unlocked Mode

e. Low-Impact Mode

5. Which of the following are valid EAP packet types?

a. EAPOL-Alert

b. EAPOL-Start

c. EAPOL-Logoff

d. EAPOL-Private

e. EAP-Packet

6. Which of the following are valid configurable 802.1x port states?

a. Auto

b. Unauthorized

c. Forced-Authorized

d. Authorized

e. Forced-Unauthorized

7. Which of the following port authentication host modes allows a single data and single voice host to be authenticated?

a. Single-Host

b. Multi-Host

c. Multi-Domain

d. Multi-Auth

e. Open

8. Which of the following is the correct Ethernet type value used with EAPOL?

a. 88:8E

b. 08:00

c. 88:E5

d. 86:DD

e. 88:08

9. Which field in the EAP frame format is 1 octet and aids in matching responses with requests?

a. Code

b. Identifier

c. Length

d. Data

10. Which of the following EAP types utilizes tunnels to encapsulate EAP traffic?

a. PEAP

b. EAP-TLS

c. EAP-TTLS

d. EAP-FAST

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:

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

• 9 or 10 overall score: If you want more review on these topics, skip to the “Exam Preparation” section. Otherwise, move on to Chapter 6, “Implementing and Configuring Basic 802.1X.”

Foundation Topics

Identity-Based Networking Services (IBNS) and IEEE 802.1x Overview

IEEE 802.1x is a standard set by the IEEE 802.1 working group. It is a data link layer (Layer 2) protocol designed to provide port-based network access control using authentication unique to a device or user. This service is called port-level authentication.

In today’s network environments, many enterprises have implemented virtual LANs (VLAN), wireless LANs (WLAN), Dynamic Host Configuration Protocol (DHCP), and other dynamic technologies to accommodate user mobility and flexibility. Although these technologies have increased the benefits for the users in terms of network availability, they also render the corporate networks vulnerable to unauthorized access. In an unsecured environment, it is much easier for hackers and unauthorized entities to launch denial of service (DoS), hijack, or other types of attacks.

Cisco IBNS is an IEEE 802.1x-based technology solution that increases network security by authenticating users based on personal identity in addition to device MAC and IP address verification. IBNS controls who and what is on the network, keeping outsiders out through authentication and authorization, keeping the insiders honest through accountability, and increasing the overall network visibility.

IBNS also defines a framework for deployment that allows a smooth transition to a fully enforced environment. This framework operates by defining three modes that are used at each transitional point in implementation and are detailed in Table 5-2.

image

Table 5-2. IBNS Deployment Modes1

image

IBNS and 802.1x Enhancements and Features

Several enhancements to the IEEE 802.1x standard are offered by Cisco IBNS, including the following:

• VLAN assignments: In a standard 802.1x implementation, authenticated users are placed in a VLAN preconfigured for the connected port. With IBNS, VLAN assignments can be obtained through the user or device identity. This is accomplished using the username-to-VLAN and device-to-VLAN association maintained in the RADIUS server. When the user successfully authenticates, the RADIUS server sends the VLAN information to the switch, and the switch dynamically configures the attached port for the specific VLAN.

• 802.1x guest VLAN: This is an important feature in environments where there is a mix of 802.1x clients and clients that do not support 802.1x. Using this feature, the non-802.1x-compatible users or devices gain access to network resources through the guest VLAN. A guest VLAN normally provides restricted access for basic network resources that would allow limited functions such as browsing, email, or access to an 802.1x client.

• Restricted VLAN: This feature allows 802.1x-compatible clients to still gain some restricted access, even if they fail authentication. If the client fails authentication three times, it will be automatically put into the restricted VLAN; without a successful authentication, the port will remain in the restricted VLAN indefinitely. After the client is put into the restricted VLAN, a fake Extensible Authentication Protocol (EAP) success message is sent to the client to stop constant reauthentication. The level of access given to this VLAN is configurable depending on the needs of the specific organization. For example, it is possible to make a guest and a restricted user have the same access.

• Port security: 802.1x provides the option to enable port security on a switch port. If this feature is enabled to allow only a single MAC address on the port, it will deny multiple MAC addresses to be used on that port. This eliminates the risk of users attaching hubs to a switch port to add more devices to the same port.

• Voice VLAN ID: This is a feature that incorporates the benefits of Voice over Internet Protocol (VoIP) and dynamic port security mechanisms such as 802.1x. It enables administrators to configure an auxiliary VLAN for voice VLAN ID.

• Access control list (ACL) assignment: ACLs can be dynamically assigned using 802.1x authentication policy. This feature enables administrators to restrict the user to specific network segments or limit access to sensitive resources to specific users without compromising user mobility.

• Inaccessible Authentication Bypass: This feature allows devices attached to critical ports to still be authenticated and allowed to pass traffic even if the RADIUS server(s) is (are) inaccessible. When the RADIUS server(s) become accessible again, the ports are then automatically reauthenticated using the server.

• MAC Authentication Bypass (MAB): When using this feature, it is possible for a device to be authenticated without 802.1x support. This is done by referencing a MAC database that is held on the RADIUS server. The MAB feature is only enabled after the client fails to respond to Extensible Authentication Protocol over LAN (EAPOL) requests and causes a timeout.

• Network Admission Control Layer 2 Validation: When using this feature, it is possible to check the posture of the client before granting access to the client. This can be used to verify items such as firewall settings and the status of virus and spam software updates.

• Web Authentication (WebAuth) with Automatic MAC Check: This feature provides the capability to authenticate a port through a web browser. The automatic MAC check feature allows the automatic authentication of devices based on their MAC address; this is typical for devices like printers that do not support 802.1x.

• Flexible Authentication Sequencing (FlexAuth): FlexAuth provides the ability to change the default behavior in making authentication decisions. By default, the port attempts 802.1x authentication, then MAB, and then WebAuth.

• Open Access: When using this feature, the clients have the ability to authenticate using 802.1x or MAB; however, regardless of the outcome, the port will always allow normal access. This feature is typically used to perform a running audit of the clients on the network that support 802.1x. Typically, this is used during a transition to full 802.1x/IBNS enforcement.

• Multi-Domain Authentication: When using this port host mode, the port allows a device to be authenticated to both the data and the voice domains.

• Multiple Authentications (MultiAuth): When using this port mode, the port allows multiple devices to be separately authenticated while attaching through the same port. By default, the first device on a port authenticates the port for everyone else on the port. If that client goes offline, the access for the other clients is cut off until authentication from another client takes place.

• Remote Site IEEE 802.1x Local Authentication Service: This feature enables you to configure an access point or wireless-aware router to act as a local RADIUS server. This capability provides backup authentication in the event that the WAN link or the central RADIUS server fails.

802.1x Components

image

The IEEE 802.1x framework defines three roles in the authentication process. The terminology for these roles is as follows:

• Supplicant: The endpoint requesting access to the network. For example, this could be an end-user device, a printer, or an IP phone.

• Authentication server: The entity that validates the identity of the supplicant and notifies the authenticator to allow or deny the client request for access. For example, a RADIUS server, such as ACS, can provide authentication server services.

• Authenticator: The device between the supplicant and the authentication server that facilitates authentication. The client is normally directly connected to the authenticator. For example, a switch or a wireless access point would provide authenticator services to clients attempting to access LAN.

Figure 5-1 shows the specific roles of the devices in the network during 802.1x port-based authentication.

Figure 5-1. 802.1x Device Roles

image

Prior to the client authentication, the port will only allow EAPOL, Cisco Discovery Protocol (CDP), and Spanning Tree Protocol (STP) traffic through the connected port. After the authentication is successful, normal traffic can pass through the port.

802.1x Interworking

The following sections go over the basic topics that are used when implementing 802.1x internetworking.

Extensible Authentication Protocol (EAP)

EAP is the transport mechanism used in 802.1x to authenticate supplicants against a back-end data store, typically a RADIUS server. EAP was initially defined in RFC 2284 as a general authentication framework running over Layer 2 Point-to-Point Protocol (PPP). In RFC 3748, the EAP definition has been updated to include IEEE 802 as a link layer. The IEEE 802 encapsulation of EAP does not involve PPP, and IEEE 802.1X does not include support for link or network layer negotiations. As a result, within IEEE 802.1X, it is not possible to negotiate non-EAP authentication mechanisms, such as Password Authentication Protocol (PAP) or Challenge Handshake Authentication Protocol (CHAP), without specialized tunneling support. EAP does not select a specific authentication mechanism during the link layer phase but rather postpones it until the authentication phase. Figure 5-2 depicts the EAP packet format.

Figure 5-2. EAP Packet Format

image

image

The field descriptions are as follows:

• Code: The Code field is 1 byte and identifies the type of EAP packet. Table 5-3 shows the assigned EAP codes.

Table 5-3. EAP Codes

image

Any EAP packets with other codes are silently discarded.

• Identifier: The Identifier field is 1 byte and aids in matching responses with requests.

• Length: The Length field is 2 bytes and indicates the length, in bytes (octets), of the EAP packet, including the Code, Identifier, Length, and Data fields. Bytes outside the range of the Length field should be treated as data link layer padding and will be ignored upon reception. A message with the Length field set to a value larger than the number of received bytes will be silently discarded.

• Data: The Data field is 0 or more bytes. The Code field determines the format of the Data field.

EAP over LAN (EAPOL)

On LAN media, the supplicant and the authenticator communicate using an encapsulation technique known as EAPOL. EAPOL supports various media types including Ethernet, Token Ring, Fiber Distributed Data Interface (FDDI), and WLANs. EAPOL provides the capability to encapsulate EAP messages that can be handled directly by a LAN MAC service.

The EAPOL frame is rather simple, as shown in Figure 5-3. The EAP packet is encapsulated within the frame and is located in the Packet Body field.

image

Figure 5-3. EAPOL Frame Format

image

The Destination and Source MAC Address fields are both 6 bytes and are used the same as with all normal Ethernet traffic; however, the Destination MAC Address field always holds the Port Access Entity (PAE) group address, which is defined as 01:80:C2:00:00:03.

The PAE Ethernet Type field is 2 bytes, taken to represent an unsigned binary number and always set to 88:8E.

The Packet Type field is 1 byte in length, taken to represent an unsigned binary number. Its value determines the type of packet being transmitted. Table 5-4 displays the types that are defined.

The Packet Body Length is 2 bytes, taken to represent an unsigned binary number and defines the length of the packet body. The field being set to 0 indicates that the Packet Body field is not present.

The Packet Body field is only present when the Packet Type field is set to EAP-Packet, EAPOL-Key, or EAPOL-Encapsulated-ASP-Alert.

Table 5-4. EAPOL Packet Types

image

EAP Message Exchange

EAP message exchange can be complex to understand. Figure 5-4 shows an example EAP exchange using the One-Time Password EAP method. It is important to understand that the EAP packets are only encapsulated by EAPOL from the supplicant to the authenticator; from the authenticator to the authentication server, the EAP packets are encapsulated within the RADIUS packets.

Figure 5-4. Sample EAP Conversation

image

The following list describes what happens in each step of an EAP conversation:

Step 1: The supplicant sends an EAPOL-Start frame to the authenticator to notify that it is ready to authenticate. If the authenticator initiates the connection, there will be no EAPOL-Start message sent.

Step 2: The authenticator sends an EAP-Request/Identity packet to the supplicant as soon as it detects that the link is active (for example, the client has connected to a switch port).

Step 3: The supplicant sends an EAP-Response/Identity packet to the authenticator, which is then passed on to the authentication (RADIUS) server. Communications between the supplicant and authentication server also leverage the RADIUS protocol carried over User Datagram Protocol (UDP).

Step 4: The authentication server sends back a challenge to the authenticator, such as with a token password system. The authenticator unpacks this from IP and repackages it into EAPOL and sends it to the supplicant. Different authentication methods will vary this message and the total number of messages. EAP supports client-only authentication and strong mutual authentication. Only strong mutual authentication is considered appropriate in wireless environments.

Step 5: The supplicant responds to the challenge through the authenticator and passes the response on to the authentication server.

Step 6: If the supplicant provides proper identity, the authentication server responds with a success message, which is then passed on to the supplicant. The authenticator now allows access to the LAN, possibly restricted based on attributes that came back from the authentication server. For example, the authenticator might switch the supplicant to a particular VLAN or install a set of access control rules.

Port States

When using 802.1x, there are three defined port states, as described in Table 5-5.

image

Table 5-5. 802.1x Port States

image

If IEEE 802.1x is configured on a switch port, the port starts in the automatic port authentication state (Auto). When in the Auto state, the port will start in the unauthorized state and require the supplicant to successfully authenticate. After the supplicant authenticates, the port changes to the authorized state and allows through traffic from the client to network resources. If the client does not support IEEE 802.1x, the switch cannot authenticate the client unless MAB is configured to be used or a guest VLAN is preconfigured to provide some level of necessary network access.

Port Authentication Host Modes

Numerous host modes of operation are supported for 802.1x port authentication, as outlined in Table 5-6.

image

Table 5-6. Port Authentication Host Modes

image

EAP Type Selection

There are several types of EAP authentication available for wired and wireless networks. The most used types and methods for EAP authentication include the following:

• EAP-MD5

• PEAPv0-MSCHAPv2

• LEAP

• EAP-TLS

• EAP-TTLS

• EAP-FAST

The following sections describe the most common methods of 802.1x authentication.

EAP–Message Digest Algorithm 5

EAP-MD5 uses message digest algorithm 5 (MD5)–based challenge-response for authentication. Using this method, the client identity is transmitted over the network, but a hash is sent in lieu of a password. The server generates a random string and sends it to the user as a challenge. The client MD5 hashes the challenge using its password as the key and sends it back to the server. The server then authenticates the subscriber by verifying this hash.

This type of authentication is well supported and provides a simple mechanism for authentication using username and passwords. It also does not burden the server or the client because of its lightweight processing requirements.

The cons of using MD5 are the security weaknesses inherent in this authentication method. MD5 requires the storage of plain-text or reversible passwords on the authentication server.

Figure 5-5 displays a sample of the EAP data field.

Figure 5-5. EAP-MD5 Data Field Example

image

Protected EAP w/MS-CHAPv2

Protected EAP (PEAP) is an IETF draft RFC submitted by Cisco Systems, Microsoft, and RSA Security. It supports various EAP-encapsulated methods within a protected Transport Layer Security (TLS) tunnel.

PEAP supports an extensible set of user authentication methods, such as one-time token authentication and password change or aging. It uses server-side digital certificate authentication based on the public-key infrastructure (PKI) standard. In environments where certificates are not issued to every client, PEAP can use a Microsoft Windows username and password instead by querying the Windows domain controller, Active Directory, or other existing user database.

PEAP uses two phases:

• Phase 1 of the authentication sequence is the same as that for EAP-TLS (server-side TLS). A server-side TLS authentication is performed to create an encrypted tunnel and complete server-side authentication. At the end of Phase 1, an encrypted TLS tunnel is created between the user and the RADIUS server for transporting EAP authentication messages.

• In Phase 2, the RADIUS server authenticates the client through the encrypted TLS tunnel through another EAP type, the most common being MS-CHAP version 2 (as defined by the PEAP draft). The RADIUS server will relay the MS-CHAP credentials to a server to validate the user login. When this is complete, an EAP-Success message is sent to the client.

Figure 5-6 displays a sample of the EAP data field.

Figure 5-6. PEAP with MS-CHAPv2 Data Field Example

image

Cisco Lightweight EAP

Cisco Lightweight Extensible Authentication Protocol (LEAP) uses the concept of mutual authentication to validate a user. Mutual authentication relies on a shared secret and the user’s password, which is known by the client and the network. The authentication server sends a challenge to the client. The client uses a one-way hash of the user password to send a response to the challenge. The server creates its own response based on the user database information and compares it to the response received from the client. When the server authenticates the client, the same process is repeated in reverse so that the client can authenticate the server. When this process is completed, an EAP-Success message is sent to the client.

EAP–Transport Layer Security

EAP-TLS is a standard developed by Microsoft and accepted by the Internet Engineering Task Force (IETF) as RFC 2716. It is based on the Transport Layer Security (TLS) protocol as described in another standard (RFC 2246).

Similar to the Cisco LEAP method, EAP-TLS mutually authenticates the client and the server; however, in this case, passwords are not used. Instead, public key cryptography based on the Rivest, Shamir, and Adelman (RSA) handshake is used. EAP-TLS uses digital certificates or smart cards to validate both the user’s and the server’s identity.

The RADIUS server sends its certificate to the client in Phase 1 of the authentication sequence (server-side TLS). The client validates the RADIUS server certificate by verifying the issuer of the certificate, a certificate authority (CA) server entity, and the contents of the digital certificate. When this is complete, the client sends its certificate to the RADIUS server in Phase 2 of the authentication sequence (client-side TLS). The RADIUS server validates the client’s certificate by verifying the issuer of the certificate (CA server entity) and the contents of the digital certificate. When this is complete, an EAP-Success message is sent to the client.

The advantage of EAP-TLS is that it can be configured for two-factor authentication systems; it is one of the strongest forms of authentication available today.

The cons of EAP-TLS are that it can be more complex to deploy because of the various components, such as a certificate authority (CA). It is also more computationally intensive on both the client and the server.

Figure 5-7 displays a sample of the EAP data field.

Figure 5-7. EAP-TLS Data Field Example

image

EAP–Tunneled Transport Layer Security

EAP-TTLS is defined in RFC 5281, extends on the concepts used for EAP-TLS, works similarly to PEAP, and uses two phases. Like EAP-TLS, EAP-TTLS utilizes TLS to form a tunnel between the authentication server and the supplicant and is created in Phase 1. Like PEAP, EAP-TTLS utilizes the TLS tunnel to encapsulate another form of EAP authentication but differs from PEAP in that it also can support non-EAP methods like PPP Authentication Protocol (PAP) and PPP Challenge Handshake Authentication Protocol (CHAP). However, unlike EAP-TLS, EAP-TTLS does not require that both the server and client be authenticated, which makes configuration easier.

Figure 5-8 displays a sample of the EAP data field.

Figure 5-8. EAP-TTLS Data Field Example

image

EAP–Flexible Authentication via Secure Tunneling

EAP–Flexible Authentication via Secure Tunneling (EAP-FAST) was developed by Cisco and is documented in RFC 4851. Cisco developed EAP-FAST to support customers that require strong password policy enforcement but do not want to deploy digital certificates. EAP-FAST provides protection against a variety of network attacks, including man-in-the-middle, replay, and dictionary attacks.

Phase 1 establishes a mutually authenticated tunnel. The client and server use a Protected Access Credential (PAC) to authenticate each other and establish a secure tunnel.

Phase 2 performs client authentication in the established tunnel. The client sends a username and password to authenticate and establish client authorization policy.

EAP-FAST tunnel establishment relies on a PAC that can be provisioned and managed dynamically by EAP-FAST through the authentication server during Phase 2.

Figure 5-9 displays a sample of the EAP data field.

Figure 5-9. EAP-FAST Data Field Example

image

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 questions that follow 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 5-7 lists a reference of these key topics and the page numbers on which each is found.

Table 5-7. 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.

Define Key Terms

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

Cisco Discovery Protocol (CDP)

hash

Transport Layer Security (TLS)

Voice over IP (VoIP)

wireless LAN (WLAN)

Fill in the Blanks

  1. The _____ deployment mode reduces known issues with other protocols’ timeouts and networked services.
  2. The _____ feature provides the ability for a host without 802.1x support to gain full network access.
  3. The _____ feature provides the ability for a host to gain some network access even after failing authentication.
  4. When implementing 802.1x, the _____ is the entity that validates the identity of the requesting host.
  5. The _____ and _____ protocols are not supported by 802.1x natively without external tunneling support.
  6. In a LAN environment, the _____ protocol is used to transport EAP traffic.
  7. When the supplicant initiates the 802.1x connection, it sends an _____ frame to start the connection.
  8. When using EAP-MD5, a _____ is sent in lieu of a password on the network.
  9. The _____ is relied on by EAP-FAST to help establish tunneling.
  10. When using EAPOL, the PAE group address is always set to _____.

References

For additional information, refer to these resources:

1 http://www.cisco.com/go/ibns