Question

Difficulty: HardIdentity and Access Management Operations

A network security administrator is deploying 802.1X EAP-TLS network access control across enterprise switches to enforce mutual authentication and dynamic VLAN authorization. Place the operational stages of the EAP-TLS authentication and authorization sequence in the correct chronological order from session initiation to final access enforcement.

  1. 1The endpoint (supplicant) transmits an EAP-Response/Identity to the switch (authenticator), which encapsulates the payload into a RADIUS Access-Request packet forwarded to the AAA server.
  2. 2The endpoint and AAA server complete a mutual TLS handshake, verifying the client certificate against the enterprise PKI and establishing an encrypted EAP tunnel.
  3. 3The AAA server queries the central directory service to evaluate the authenticated identity's group memberships and associated authorization policies.
  4. 4The AAA server returns a RADIUS Access-Accept message containing Vendor-Specific Attributes (VSAs) specifying the assigned VLAN and security group ACLs.
  5. 5The switch applies the received Vendor-Specific Attributes, transitions the network port to an authorized state, and applies the dynamic VLAN and ACL configuration to the session.

Answer

The correct operational sequence begins with identity encapsulation via RADIUS Access-Request, followed by EAP-TLS mutual certificate validation, directory policy authorization evaluation, RADIUS Access-Accept with VSAs return, and final port enforcement by the switch.
In 802.1X network access control, the sequence strictly follows: (1) Identity initiation where EAPoL responses are encapsulated into RADIUS Access-Request messages; (2) EAP-TLS mutual authentication via X.509 certificates; (3) Directory lookup to determine identity privileges; (4) RADIUS Access-Accept transmission containing dynamic authorization parameters (VSAs); and (5) Local port authorization and VLAN/ACL enforcement by the switch.

Step-by-Step Solution

1
Identify the initial protocol exchange between Supplicant, Authenticator, and AAA Server.
The supplicant responds to EAP-Request/Identity with an EAP-Response/Identity, which the switch encapsulates into a RADIUS Access-Request packet.
802.1X uses EAP encapsulation over LAN (EAPoL) between endpoint and switch, converted to RADIUS between switch and AAA server.
2
Determine the authentication mechanism step.
EAP-TLS mutual authentication completes via X.509 certificate validation over a TLS handshake.
EAP-TLS requires both server certificate validation by the client and client certificate validation by the AAA server before granting access.
3
Determine the authorization lookup phase.
The AAA server evaluates identity group memberships and directory policies.
Authentication (verifying who the user/device is) must succeed before authorization policy (determining allowed access level) can be evaluated.
4
Identify the return authorization payload.
The AAA server issues a RADIUS Access-Accept containing VSAs (e.g., RFC 2868 VLAN attributes).
The AAA server communicates policy enforcement parameters back to the network access device using RADIUS attributes.
5
Identify final enforcement at the network layer.
The switch transitions the port state to authorized and applies dynamic VLAN/ACL rules.
The authenticator network switch is responsible for enforcing physical/logical port controls based on the AAA server's directive.

Key Concept

802.1X EAP-TLS AAA Operation and Dynamic Enforcement
Rate this question