Match each wireless authentication protocol or security framework on the left with its correct operational requirement and cryptographic mechanism on the right.
- EAP-FASTEstablishes a secure tunnel using Protected Access Credentials (PACs) generated and managed by an authentication server, avoiding mandatory PKI certificate deployment.
- PEAP-MSCHAPv2Encapsulates user credentials inside an encrypted TLS tunnel established using only a server-side digital certificate while authenticating the client via MS-CHAPv2.
- EAP-TLSEnforces mutual authentication by requiring valid X.509 digital certificates installed on both the RADIUS authentication server and every connecting client endpoint.
- WPA3-SAEReplaces static pre-shared keys with a dragonfly key exchange mechanism that provides forward secrecy and protects against offline password dictionary attacks.
Answer
EAP-FAST matches with Protected Access Credentials (PACs) without mandatory PKI certificates; PEAP-MSCHAPv2 matches with server-side certificate tunneling user password authentication; EAP-TLS matches with mutual X.509 certificate authentication on both client and server; WPA3-SAE matches with dragonfly key exchange protecting against offline dictionary attacks.
Each protocol is accurately matched to its distinct architecture: EAP-FAST uses PACs in lieu of server certificates; PEAP-MSCHAPv2 uses a single server certificate to encrypt user password authentication; EAP-TLS enforces mutual authentication using digital certificates on both endpoints; WPA3-SAE implements Dragonfly zero-knowledge key exchange for pre-shared key environments.
Step-by-Step Solution
Key Concept
Wireless Authentication Protocols and EAP Frameworks