wifisecurity1If you have attended any of my presentations of WLAN/Wi-Fi Security or even my Security Courses,you know that the design of WLAN/Wi-Fi networks leaves a lot to be desired when it comes to security.  This is also evidenced by the law suit against Amazon with hackers allegedly controlling Ring cameras.
I have always said that like a teeter totter, Security is always a trade off between ease of use and difficult to break into.  You have to find balance between these two end points and what works for you.
The bottom line is that ordinary people like you and I are a key part of the security equation.  While we cannot change the design flaws of the equipment or standards, we can very much reduce the vulnerabilities through good practices.  Searching the web you will find good suggestions for the most part, but I have found them to be lacking in one way or another, especially when it comes to thoroughness.  
I think in this time of short attention spans, and shock information, not enough time is spent contemplating the issues and listening to detailed advice.  When it comes to security, one little weakness is all it takes to bring down an entire system or network.  Invest some time, and read the advice below.
Everyone is vulnerable when it comes to WLAN/Wi-Fi, even those in the countryside.  You cannot prevent someone from scanning your network.  To verify this go to  https://www.wigle.net/index and search for your address.  Have you been scanned?  Another place to look is  https://www.shodan.io/
So here are my "Best Practices for Consumer WLAN/Wi-Fi Security":
  1. Do not trust the built-in security alone of any WLAN/Wi-Fi system.  Understand the the inherent security of WLAN/Wi-Fi is not good.  Your WLAN/Wi-Fi traffic is not 100% encrypted, and it never has been.  Understand this, and assume that it is not.
  2. ALWAYS use HTTPS:// when browsing to any web site because that guarantees that the traffic you are sending and receiving is encrypted.
  3. If you don't already know, use strong passwords, and only use WPA2 or WPA3.  Frankly we should not even say passwords anymore, we should say pass phrases.  Use sentences without spaces: "Ineedtostartworkby800am!" is a great, easy to remember, almost uncrackable pass-phrase.  Always replace default passwords.  Lastly, change them routinely, like every quarter.
  4. Use different passwords/passphrases and manage then using a password manager.  Think about this: if you use the same password over and over and one of your sites that you have an account on is compromised, and your password is leaked, now the people with your password for that site can access all the other sites you have accounts on!  Here is an answer for this: use a passphrase that increments like "IwishmybirthdaywasonJanuary10th!"  You can increment the month or the date, or both.  This also works for regularly changing the passphrase on a particular site.
  5. Your wireless SSID: this is the name of your wireless network that is seen by anyone near your wireless router (assume 100 yards).  Use the SSID that your service provider requires, but make sure it does not contain your name, or any other identifying factor for your home.  Never use the default factory SSID (examples: dlink, Linksys, 2wire, Netgear, ATT, etc.).  Further, make sure your SSID is not on this list:  https://www.wigle.net/stats#ssidstats
    1. Don’t use first or last name, address, phone number, or anything else personal. Broadcasting personal information identifies who owns the network, and may aid the hacker in cracking the wireless password.
    2. Be unique when selecting an SSID, but too much creativity may draw attention to the networks name along with attempts to hack the network.
    3. With a maximum of 32 characters you have some creative capabilities, but also think camouflage, so the network name blends in with the other networks in range and does not stand out.
    4. Follow these rules even if your SSID is hidden or not being broadcast. Hidden network SSID's can very easily be discovered and they are not immune.
  6. Turn off devices that act as Access Points (like printers, some Wi-Fi Cameras, etc.) when you do not need them to be WLAN/Wi-Fi access points.  This will reduce interference with your actual Access Point and reduce your vulnerabilities.
  7. Make sure that systems like IP Cameras, security systems, computers you do your banking on, in other words systems that you depend on are wired via Ethernet, not on the WLAN/Wi-Fi.  This is not a guarantee, but it will minimize those systems being exposed to someone listening to your wireless network.
  8. Don't let anyone other than authorized technical service people touch, or change settings on your wireless router.  If your service provider allows you administrative access to the wireless router configuration, take the same precautions with using passwords mentioned above.  In some cases you may need to access the system remotely, while away, but if this is not necessary, disable remote access to the configuration.
  9. Disable WPS - this system to ease wireless connectivity is horribly flawed.  No exceptions.
  10. Disable WEP security - this system is also horribly flawed.  No exceptions.
  11. This is going to sound a little counter-intuitive, but you should limit WLAN/Wi-Fi signal strength wherever possible.  The goal should be to provide enough signal only to the areas where it’s required.  Your WLAN/Wi-Fi network signal can reach way beyond building walls and out into public spaces, and when that happens, you risk allowing bad actors to attempt to connect to your network or interfere with the operation of your network.
    1. Having your Access Point (or AP) in the right place is critical to good operation of your wireless network, and it is good for controlling how far your signal goes beyond where you want.  Understand that this is not always possible, but making good trade-off's here is important.
    2. Make sure you know how to control the channel (if your service provider allows this), and manually set it to minimize interference.
    3. Use both 2.4 GHz and 5 GHz with different SSID's so you know which network you are on.  5 Ghz tends to travel less far, which is good to control access, but bad if you need distance.  Again, these are trade-offs.
    4. Be prepared to adjust over time, especially in populous areas.
  12. Pay very close attention to any changes: things like having to reconnect to the wireless network unexpectedly.  Make sure your system connect to the right wireless networks.  I can easily trick you into connecting to an insecure network using the same SSID as yours, unless you are vigilant.  This is easier to imagine in more crowded environments, but nonetheless it applies to all of us.
    1. It is a pain, but I prefer NOT to connect automatically to networks.  This ensures that I am always in control.
    2. If you are detailed oriented, look closely at the MAC addresses of your system and the wireless router.  Make sure these MAC addresses are always in play and not some rogue MAC address.  I personally keep track of the MAC addresses on my network, and I check them against my known good list.
  13. Giving out your SSID passphrase is an issue as you are extending your circle of trust.  I prefer, if it is available, to have a guest wireless network with a relatively simple passphrase like "Welcometoournetwork!" or "ThewaytotheInternet!" that I change routinely.  Guest networks can be set up on most modern wireless routers (ask your service provider for help here).
    1. Turn these off when not needed.
    2. Change the passphrase routinely.
    3. You will be helping to educate your friends and family on how they should set up their own networks!
  14. Ultimately, there are always weak spots in every network.  Know where they are.  Know how to occasionally scan your network if you suspect something is not right (I will add a link on how to do this here).  Or, simply reset the system and change the passphrases.  This always puts any possible bad actors back to square one.
I hope this helps you to secure your home or small business wireless network.
What am I missing?  Please feel free to comment below.
P.S. Corporate networks are a bit more involved, though fundamentally everything above applies.  I will write a separate article on that.

Comments powered by CComment

The nicest thing you can do is use these inks to support us!  Thank you!

Support our research!

Become a Patron!

Find by Tag

4G Networks 5G Networks 6in4 6LoWLAN 6LoWPAN 802.11 802.11ah 802.11ax 802.11ay 802.11az Addressing Analysis Ansible Architecture ARP AToM BGP Bloom's Taxonomy Broadband Cable CBRS CellStream Cellular Central Office Cheat Sheet Chrome Cisco Cloud Coloring Rules Computer Consulting Course Design CPI CSR Customer Support Data Center Data Networking Decryption DHCPv6 DNS Documentation dumpcap ECMP Ethernet Ethics Flipping the Certification Model Fragmentation G-MPLS Git GNS3 Google GQUIC Hands-On History Home Network HTTPS ICMP ICMPv6 IEEE 802.11p IEEE 802.15.4 Interface Control Internet IoT IPsec IPv4 IPv6 IS-IS L2VPN L3VPN LDP Linux LLN LoL M-BGP MAC MAC OSx Macro Microsoft mininet Monitoring Monitor Mode MPLS Multicast My Room Name Resolution Netcat Netmiko NetMon netsh Networking Network Science nmap Npcap Online Learning Online School OpenFlow OSPF OSPFv2 OSPFv3 OSX OTT Parrot PIM pktmon Policy POTS POTS to Pipes PPP Profile Programming Project Management Protocol 41 PW3E Python QoS QUIC Remote Desktop Requirements RIP Routing RPL RSVP Rural SAS SDN Security Self Certification Service Provider Small Business SONET Speed SS7 SSH SSL Subnetting T-Shark TCP TCP/IP Telco Telecom 101 Telecommunications Telephone termshark TLS Tools Traceroute Tracewrangler Traffic Engineering Training Travel Tunnel Ubuntu Utility Video Virtualbox Virtualization VoIP VRF VXLAN Web Based Delivery Webex WEP Wi-Fi Wi-Fi 6 Wi-Fi 6/6E Windows Winpcap Wireless Wireless 5G Wireshark Wireshark Tip WLAN WPA2 ZigBee Zoom

Support us by clicking:

Twitter Feed