09-03-2014 02:01 AM - edited 03-10-2019 09:59 PM
Hi experts,
I'm aware of this discussion https://supportforums.cisco.com/discussion/11962026/ise-12-device-registration-mab-only-no-client-provisioning#comment-9371166
but looking for a detailed configuration to get following to work:
Employee's have access to the network with their corporate devices. No problem
Now employees need to be able to use their own mobile devices to get access. There is no definition of what devices are allowed.
II guess to let employees register their private devices with MAC address on MyDevice portal would be the most sufficient solution.
Does anyone have a detailed configuration or link how to achieve that?
Thanks,
Frank
Solved! Go to Solution.
09-03-2014 06:34 AM
09-03-2014 06:34 AM
09-03-2014 08:47 AM
Having BYOD access be based on mac address only is not really ideal and also not secure. A mac address can easily be spoofed and consequently your security policy can be bypassed. If you have a PKI environment you can take the EAP-TLS with SCEP approach:
If you don't have a PKI environment and don't want to mess with certificates you can still use a more secure method than MAC addresses. For instance, you can perform PEAP user authentication. You can create a "special" BYOD AD group and place the authorized users there. Then they can use their AD credentials to authenticate. In the authorization policy you can limit the access for those type of authentications via dACLs (switches) or named access lists (WLCs)
Hope this helps!
Thank you for rating helpful posts!
09-03-2014 01:13 PM
Hi Neno,
thanks for taking the time to answer. (Un) fortunately a PKI/certificates is not an option at the moment.
I like your second suggestion but the idea Mohana refered via the link
http://www.cisco.com/c/dam/en/us/td/docs/solutions/Enterprise/Borderless_Networks/Unified_Access/BYOD_Use_Cases.pdf to seems to be even easier.
Starting from page 18-4 the example shows a very simple way to achieve my goal with minimum configuration effort. One of the major drawbacks I can see in this example is that an emplyee could us this AuthZ for access with a corporate device too.
Thanks,
Frank
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide