An engineer is designing a BYOD environment utilizing Cisco ISE for devices that do not support native supplicants. Which portal must the security engineer configure to accomplish this task?
C
Some network devices that need network access are not supported by native supplicant provisioning and cannot be registered using the BYOD portal. However, employees can add and register personal devices, whose operating systems are not supported or do not have web browsers (such as printers, internet radios, and other devices), using the My Devices portal.
https://www.cisco.com/c/en/us/td/docs/security/ise/3-0/admin_guide/b_ISE_admin_3_0/b_ISE_admin_30_byod.html
I will go for B too.
the question is about design and put in production a solution for let authenticate devices that do not have native supplicant.
The need to log in into the My device portal for add the device is not the right answer for me.
In this guide is clear how to configure BYOD without the need of a native supplicant policy configured
https://community.cisco.com/t5/security-blogs/ise-byod-registration-only-without-native-supplicant-or/ba-p/3099290
We can also define how many devices that does not support the native supplicant.
After that we need to configure the specific authorization policies for these devices.
https://www.google.com/search?sca_esv=584485115&sxsrf=AM9HkKl4Nf8vU-mivr0QzBoio-yaTCjJwQ:1700626451946&q=my+devices+portal+cisco+ise&tbm=vid&source=lnms&sa=X&ved=2ahUKEwik_8Cc39aCAxWIhv0HHV3eDxAQ0pQJegQICBAB&cshid=1700626456264194&biw=2400&bih=1138&dpr=0.8
The correct answer is - Client Provisioning.
Client Provisioning is a portal in Cisco ISE that allows administrators to customize the settings for devices that connect to the network. This includes settings such as the device's username and password, the location of the compliance module, and the type of authentication that is required.
For devices that do not support native supplicants, administrators can use the Client Provisioning portal to configure the device to use PEAP or TTLS authentication. PEAP and TTLS are both tunneling protocols that allow devices to authenticate to Cisco ISE even if they do not support native supplicants.
The other options are not correct. The BYOD portal is used to manage the settings for a user's endpoint device. The My Devices portal is used by users to manage the settings for their own endpoint devices. MDM is a mobile device management platform that can be used to manage devices that connect to the network.
Thanks YmerG!
As per : https://www.cisco.com/c/en/us/td/docs/security/ise/2-6/admin_guide/b_ISE_26_admin_guide/b_ISE_admin_26_byod.html#task_323AFE02F568400B93FFB3448D0CA3F3
My Devices Portals: Enables employees to add and register personal devices, including those that do not support native supplicant provisioning, and then manage them.
The key point of question is "Which portal must the security engineer configure to accomplish this task?" So security engineer should configure for that not a user. Answer is B Client Provisioning
Reference: Official Guide - Page 562
Provided answer is correct (C)
My Devices Portals: Enables employees to add and register personal devices, including those that do not support native supplicant provisioning, and then manage them.
https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/admin_guide/b_ISE_admin_guide_24/m_ise_devices_byod.html
We can configure that on CP portal.
https://community.cisco.com/t5/security-blogs/ise-byod-registration-only-without-native-supplicant-or/ba-p/3099290
upvoted 1 times
...
This section is not available anymore. Please use the main Exam Page.300-715 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Cachaman
2 months, 1 week agoluismg
3 months, 2 weeks agoKnightHeart
6 months agoXBfoundX
1 year, 5 months agoXBfoundX
1 year, 5 months agoXBfoundX
1 year, 5 months agodenverfly
1 year, 11 months agoCnoteone
2 years, 1 month agoHan2022
1 year, 9 months agoYmerG
2 years, 2 months agokornalt
2 years, 4 months agoYmerG
2 years, 2 months agoIlPerdan0
2 years, 4 months ago