Match each centralized authentication protocol or framework to its corresponding architectural design and operational characteristic.
- TACACS+Uses TCP port 49 and encrypts the entire packet payload, separating authentication, authorization, and accounting into distinct, modular functions.
- RADIUSOperates statelessly over UDP ports 1812 and 1813, combining authentication and authorization while encrypting only the password attribute in request packets.
- KerberosRelies on a trusted Key Distribution Center (KDC) utilizing Ticket-Granting Tickets (TGT) and symmetric cryptography for single sign-on domain access.
- EAP-TLSEnforces mutual authentication within an 802.1X framework by requiring X.509 digital certificates on both the client supplicant and authentication server.
Cevap
TACACS+ matches the description of TCP port 49 operation with full-payload encryption and separated AAA services. RADIUS matches UDP ports 1812/1813 with combined authentication/authorization and password-only encryption. Kerberos matches the Key Distribution Center (KDC) utilizing Ticket-Granting Tickets (TGT). EAP-TLS matches mutual authentication requiring X.509 certificates on both supplicant and server.
Each protocol is accurately matched to its structural specifications: TACACS+ encrypts the entire body over TCP 49 with decoupled AAA components; RADIUS combines authentication and authorization over UDP 1812/1813 with password-only encryption; Kerberos leverages a KDC and Ticket-Granting Tickets for domain single sign-on; EAP-TLS enforces mutual authentication using dual X.509 certificates.
Adım Adım Çözüm
Anahtar Kavram
AAA Centralized Framework Protocols and EAP Authentication Characteristics