Which supplicant(s) and server(s) are capable of supporting EAR-CHAINING?

The correct answer is A. Cisco AnyConnect NAM and Cisco Identity Service Engine. EAP-Chaining (also written EAP-FASTv2 with chaining) allows both machine and user authentication to be performed within a single EAP session, enabling ISE to make policy decisions based on whether both the machine AND user are authenticated. This capability requires specific…

Policy Enforcement

Question

Options

ACisco AnyConnect NAM and Cisco Identity Service Engine
BCisco AnyConnect NAM and Cisco Access Control Server
CCisco Secure Services Client and Cisco Access Control Server
DWindows Native Supplicant and Cisco Identity Service Engine

How the community answered

(41 responses)

A
90% (37)
B
2% (1)
D
7% (3)

Explanation

EAP-Chaining (also written EAP-FASTv2 with chaining) allows both machine and user authentication to be performed within a single EAP session, enabling ISE to make policy decisions based on whether both the machine AND user are authenticated. This capability requires specific support on both ends. Cisco AnyConnect NAM (Network Access Manager) is the supplicant that supports EAP-Chaining, and Cisco Identity Services Engine (ISE) is the RADIUS server that supports it. The older Cisco Access Control Server (ACS) does not support EAP-Chaining. The Windows Native Supplicant also does not support EAP-Chaining - it requires a third-party supplicant like AnyConnect NAM. Cisco Secure Services Client (SSC) was a legacy supplicant that has been replaced by AnyConnect NAM and also does not support this feature.

Topics

#EAP-Chaining#Cisco ISE#Supplicant#Network Access Control

Community Discussion

No community discussion yet for this question.

Full 300-715 Practice