Implementing a Wireless Protocol for Mobile Device Authentication

D.

RADIUS generally includes 802.1X that pre-authenticates devices.

The best option for the systems administrator to implement a wireless protocol that will allow the organization to authenticate mobile devices prior to providing the user with a captive portal login is EAP-TTLS.

EAP-TTLS (Extensible Authentication Protocol-Tunneled Transport Layer Security) is an authentication protocol that is commonly used in wireless networks. EAP-TTLS provides a secure method for wireless clients to authenticate to a wireless network before being granted access.

With EAP-TTLS, the client device first establishes a secure connection with the access point using TLS. Once the TLS connection is established, the client device then provides its credentials, such as a username and password, to the authentication server. The authentication server verifies the credentials and then informs the access point whether the client device is authorized to access the network.

In this scenario, implementing EAP-TTLS would allow the organization to authenticate mobile devices prior to providing the user with a captive portal login. This means that mobile devices would first have to authenticate using EAP-TTLS before being able to access the captive portal login page. This helps to ensure that only authorized devices are able to access the network and the organization's resources.

Option A, L2TP with MAC filtering, is not a suitable solution for this scenario. L2TP (Layer 2 Tunneling Protocol) is a tunneling protocol that is often used in VPNs. MAC filtering is a security feature that is used to restrict access to a network based on the MAC address of a device. While both of these features can provide some security benefits, they are not suitable for the specific scenario described in the question.

Option C, WPA2-CCMP with PSK, is a wireless security protocol that provides encryption and authentication for wireless networks. However, it does not provide the specific type of authentication required in this scenario, which is device authentication prior to a captive portal login.

Option D, RADIUS federation, is a network protocol that is used for remote authentication and accounting. While RADIUS can be used to authenticate wireless clients, it does not provide the specific type of authentication required in this scenario, which is device authentication prior to a captive portal login.