An open discussion on "Bring your own device" to corporate networks, specifically wireless but the concepts can be applied to wired if you want to go that route. It IS coming if not already on your network and you just don't know it. The thing to keep in mind is it touches all aspects of the business and IT - client management, security, network, support, etc. So I'll start off with a few easily deployable models that can be tailored to your environment. 1) Stick them on the guest wireless. That's usually the first step - let them on, but ONLY to access the internet, nothing internal. It sounds good at first but then the questions come from the business "what good is my smart phone/tablet if I can't access internal systems?" You WILL get that. But this is a good first step. Along with this you should start putting services on the public Internet to support these devices. 2) Guest+ network. Allows access to Internet and only specific internal hosts/services/applications - drop them off in a DMZ and let a few things in. 3) Put them on production internal/secure wireless network. This is ideal, but security concerns come into play. But it is the end goal. So that takes care of access and some security/firewall control. The next BIG question - do you want these devices to be controlled by IS or are you OK with somebody and their personal, true "bring your own" device being on your net? There are many MDM (mobile device managers) out their with AirWatch currently the leader of the pack. You can use this to truly provision and control devices. The holy grail of real BYOD is the concept of "self provisioning and profile/posturing". This is where more advanced authentication methods and intelligence come into play. I'm most familiar with Cisco's ISE platform, it can pretty much do anything you want, all on one box/platform. Right now, the direction for BYOD is self provisioning using EAP-TLS as the wireless authentication protocol. This means the device must request and get a certificate = you MUST have a solid certificate infrastructure already in place, most of you likely do or at the least it's not too difficult (depending on size) to get it going if you're an MS AD shop. If it's a large 1000+ server network, some real planning and design will have to be done. Lastly, these devices have VERY poor radios meaning they'll connect at much lower data rates than laptops with high power, high quality radios in them. Plan and design the wireless aspect of it accordingly.