Crack Ssid Name Convention

So these are basic questions. Just looking for a consensus and ideas 1. Are you guys standardizing on an SSID format? I realize it is not.
I think I've seen the pre-fab rainbow tables you're talking about before, but they were from years ago. I see a lot of new routers randomizing their default SSIDs now, so those tables might not be super helpful to anyone anymore. I'm pretty sure as long as you've got a decent password setup and change it every so often that it'll be more than sufficient to protect you from that vector of attack. Also, for the people that are going to check this thread to see if there is actually a list of the most common wifi SSIDs, check out wigle.net if you're looking for a list of common SSID names, manufacture stats, or if you're interested in common SSIDs in your area.
Hey folks, Just looking to see how most of y’all name your SSIDs. I’m upgrading our wireless network here (decided to go with UniFi) from what has always been a single SSID to multiple SSIDs going forward. I’m probably overthinking this but figured I’d ask anyways. The first two are obvious to me, it is the third one for our company owned devices, with access to all internal servers, that I’m unsure about the best name to use. Company-Guest Company-Staff (BYOD, personal phones, etc.) Company-? My first inclination was -Secure, but am I being paranoid to think that might make it a bigger target for someone up to no good? Our current network is simply “Company” so I’m planning to not re-use it to avoid any issues when I switch over with devices trying to connect to the same old SSID.
Let me know what y’all think, I’m curious to hear how you all name your networks. Molan wrote: Why create to WLANs for guests and employee personal devices?

Just create one WLAN and make staff use the guest network if all they need is internet. Less to manageI'm going with time-liminted Vouchers on the guest network. We don't have many visitors that need access (general customers do not get it) and in the past we've always had to give out the password that grants the visitor access to everything. Wild Horses Garth Brooks Download. Staff BYOD I'm going to authenticate against AD so I can control access in in the same place I do for everything else. For our secure internal wifi, users don't even get any info about it. IT throws a connection profile onto user laptops so that it automatically connects if the laptop is in the building. The open one, for phones and guest, is our company name with all lowercase and is available through access points throughout the building (biggest thing was for wifi calling).
We have a third one that's just our company name capitalized correctly, and that one takes our AD credentials to authenticate. I believe the only one that has full access to the network is the first one. I use: = guest wifi/staff for lunch (no LAN access) = staff network access to LAN (only two people need this). For example: Spiceworks = SSID1 Spiceworks Network = SSID2 (Hidden - although that does not really do anything). Both are WPA/WPA2 (PSK), with long passwords which are changed every two weeks. For example: kxei6-xzG! Quantum Chemistry 2nd Edition Donald Mcquarrie Chemistry here. wt#lN8wLh9pK0nF#]12WFeAro9 For the LAN WiFi access SSID, its set to auto deny unless MAC is on approved list to use said SSID within the Firewall.
(Disclaimer, maybe a bit industry specific) We just have a guest network (companyname) as we have 300 delegates and 70 staff. Staff then use our vpn to access what they need (rolled out by Group policy). Wifi is in an isolated vlan, with no traffic allowed to company vlan or between clients. Staff use a microsoft vpn which the core switch redirects, when it comes from the internal wifi, back to the server to authenticate. This works for us because the vpn termination point is not overloaded.
If your VPN device or server could not cope with the load, this may be of no help to you, (again see disclaimer!). So VPN users can access everything, after they connect the vpn. No need for mutiple ssid's. I am redoing our wireless network here also, we are about to move to a new HQ, so this is the moment to get it right for me. I came up with the following: COMPANY-Office ->for company owned notebooks, tablets COMPANY-Guest ->for visitors and mobile phones. (our employees known they have to connect there mobile to the guest network) COMPANY-ConstructionSite ->The wireless network on all our construction sites.
All our branch office are getting the same SSID's so it doesn't matter were you sit, you are always connected. Construction sites also have the COMPANY-Guest network for the mobiles phones. And VLAN the Guest network for internet access only.