Which three protocols are supported for an endpoint in the Device Profile configuration?

In the context of endpoint configuration within the Device Profile of Cisco Identity Services Engine (ISE), RADIUS stands out as a key protocol because it facilitates centralized Authentication, Authorization, and Accounting (AAA) services for network access.

RADIUS is widely used to manage authentication and to transport user credentials securely between the client and the RADIUS server. When endpoints communicate with ISE, RADIUS plays a critical role in verifying their identities and permissions before granting access to the network.

While PEAP and 802.1X are important protocols associated with authentication mechanisms, they are not standalone protocols like RADIUS. Instead, PEAP operates over the context of a RADIUS server and is commonly used in conjunction with EAP (Extensible Authentication Protocol) methods for secure wireless and wired network access. Likewise, 802.1X serves as a network port access control framework that typically utilizes RADIUS for its backend authentication processes, making both reliant on RADIUS as part of their operation but not primary protocols as standalone options in device profile configurations.

HTTP, on the other hand, is primarily used for web traffic and management interface access, and does not directly relate to endpoint authentication or profile configuration in the same way that RADIUS does. Thus, among the options provided,