Which framework negotiates authentication methods that enable hardware-based identifiers and establishes secure tunnels for credential submission?

Which framework negotiates authentication methods that enable hardware-based identifiers and establishes secure tunnels for credential submission?

• A. Extensible Authentication Protocol (EAP)
• B. RADIUS
• C. Supplicant
• D. Compute

Answer: (A)

Extensible Authentication Protocol is a framework that allows the negotiation of different authentication methods between a client and an authentication server, often mediated by an authenticator. It supports hardware-backed credentials, such as certificates stored on smart cards, TPMs, or hardware tokens, enabling strong, hardware-based identities. Importantly, many EAP methods establish a secure tunnel (for example, EAP-TLS creates a TLS tunnel) to protect credentials as they’re submitted over the network. RADIUS, while a common back-end protocol used with EAP to carry authentication data to a server, is not the method-negotiating framework itself. The supplicant is the client-side entity, not a framework, and Compute isn’t related to the authentication framework in question.

Extensible Authentication Protocol is a framework that allows the negotiation of different authentication methods between a client and an authentication server, often mediated by an authenticator. It supports hardware-backed credentials, such as certificates stored on smart cards, TPMs, or hardware tokens, enabling strong, hardware-based identities. Importantly, many EAP methods establish a secure tunnel (for example, EAP-TLS creates a TLS tunnel) to protect credentials as they’re submitted over the network.

RADIUS, while a common back-end protocol used with EAP to carry authentication data to a server, is not the method-negotiating framework itself. The supplicant is the client-side entity, not a framework, and Compute isn’t related to the authentication framework in question.