A network administrator is designing an enterprise wireless infrastructure with varying security requirements across departments. Match each wireless authentication protocol or framework to its specific technical deployment requirement or operational security characteristic.
- EAP-TLSMandates digital certificates installed on both the RADIUS server and every connecting client device for mutual authentication.
- PEAPCreates an encrypted TLS tunnel using a server-side certificate only, allowing client authentication via password protocols like MS-CHAPv2.
- WPA3-Enterprise (192-bit Mode)Requires GCMP-256 encryption and HMAC-SHA384 integrity protection for high-security enterprise environments.
- WPA2-PersonalUtilizes a Pre-Shared Key (PSK) with CCMP (AES) cipher suites, remaining vulnerable to offline dictionary attacks if weak passphrases are used.
Answer
EAP-TLS pairs with server and client certificate requirement; PEAP pairs with server-side certificate creating a TLS tunnel for password authentication; WPA3-Enterprise (192-bit Mode) pairs with GCMP-256 encryption and HMAC-SHA384; WPA2-Personal pairs with PSK and CCMP vulnerable to offline dictionary attacks.
Each wireless framework is correctly matched based on standard 802.11 and 802.1X specifications: EAP-TLS mandates mutual PKI certificate verification; PEAP builds a server-authenticated TLS tunnel to protect user password challenges; WPA3-Enterprise (192-bit mode) elevates enterprise security with GCMP-256; and WPA2-Personal relies on static PSKs paired with CCMP encryption.
Step-by-Step Solution
Key Concept
Wireless Authentication Protocols and Enterprise Encryption Standards