Name the network authentication protocol that provides strong authentication for client/server applications through secret-key cryptography.

Name the network authentication protocol that provides strong authentication for client/server applications through secret-key cryptography.

• A. Kerberos Authentication
• B. NTLM
• C. SSH Public Key
• D. OAuth 2.0

Answer: (A)

This item tests recognizing a network authentication protocol that provides strong client/server authentication using secret-key cryptography. Kerberos does this by using a trusted Key Distribution Center (KDC) to issue tickets. The client authenticates once, then receives a ticket-granting ticket and, later, service tickets that grant access to servers. All ticket exchanges and session keys are protected with symmetric (secret-key) cryptography, so passwords never travel over the network and mutual authentication is achieved as the server and client prove knowledge of the shared session keys. Time synchronization helps prevent replay attacks and ensures tickets are valid. NTLM is an older Windows protocol based on challenge-response rather than tickets and is weaker in many scenarios. SSH uses public-key (asymmetric) cryptography rather than secret-key. OAuth 2.0 is an authorization framework, not primarily a authentication protocol for client/server identity using symmetric keys.

This item tests recognizing a network authentication protocol that provides strong client/server authentication using secret-key cryptography. Kerberos does this by using a trusted Key Distribution Center (KDC) to issue tickets. The client authenticates once, then receives a ticket-granting ticket and, later, service tickets that grant access to servers. All ticket exchanges and session keys are protected with symmetric (secret-key) cryptography, so passwords never travel over the network and mutual authentication is achieved as the server and client prove knowledge of the shared session keys. Time synchronization helps prevent replay attacks and ensures tickets are valid.

NTLM is an older Windows protocol based on challenge-response rather than tickets and is weaker in many scenarios. SSH uses public-key (asymmetric) cryptography rather than secret-key. OAuth 2.0 is an authorization framework, not primarily a authentication protocol for client/server identity using symmetric keys.