An employee must access the internet through the corporate network from a new mobile device that does not support native supplicant provisioning provided by Cisco ISE. Which portal must the employee use to provision to the device?

The My Devices Portal in Cisco ISE is specifically designed for end-users to manage their personal devices for network access under a Bring Your Own Device (BYOD) policy. When a device does not support automated methods like Native Supplicant Provisioning (NSP), the employee must manually register it. The My Devices Portal provides the interface for the employee to add their device's MAC address, which registers the device with ISE. This registration is a critical first step in the provisioning process, allowing ISE to identify the device and apply the appropriate authorization policies for network access.

A. BYOD: This is the name of the overall process or policy (Bring Your Own Device), not the specific portal used for manual device registration.
B. Personal Device: This describes the type of device being connected to the network; it is not a portal within Cisco ISE.
D. Client Provisioning: This portal is used to download and install supplicants (like AnyConnect) or configuration profiles, which typically occurs after a device has been successfully registered.

1. Cisco Identity Services Engine Administrator Guide, Release 3.2, "Cisco ISE Portals" Chapter, "My Devices Portal" section: "The My Devices portal allows users to add and manage their personal devices. After users log in to the portal, they can add, edit, and remove their devices. Users can add devices by entering the MAC address of the device."

2. Cisco Identity Services Engine Administrator Guide, Release 3.2, "Configure BYOD" Chapter, "BYOD Onboarding Process" section: This section describes the flow where users are redirected to register their devices. The My Devices Portal is the component that facilitates this user-driven registration. It states, "The user registers the device in the My Devices portal."

3. Cisco Identity Services Engine Administrator Guide, Release 3.2, "Client Provisioning" Chapter, "Client Provisioning Portals" section: "The Client Provisioning portal is used to provide the required supplicants, clients, and agents to the endpoints." This confirms its role is for agent distribution, distinct from initial device registration.