Security of Wi-Fi Infrastructure
- UBC has a large and complex Wi-Fi network that plays an integral role in the operations of the University. Consequently, intruders and hackers may consider the Wi-Fi network an attractive target to breach the security of UBC Electronic Information and Systems.
- This standard defines requirements to ensure that Wi-Fi devices, such as Wireless Access Points (WAPs), which allow Wi-Fi devices to connect to a wired network, are deployed in a secure, controlled and centrally managed way to reduce the likelihood of a security breach. Unless otherwise indicated, the UBC IT NETwork and Infrastructure Team is responsible for ensuring compliance with this standard. This policy applies to areas where WAPs installed by UBC IT provide Wi-Fi coverage.
- In addition to this standard, UBC IT Wi-Fi networks provisioned by UBC IT are governed by Policy SC11, Management of the Wireless Network.
- The Chief Information Officer has issued this standard under the authority of Policy SC14, Acceptable Use and Security of UBC Electronic Information and Systems. Questions about this standard may be referred to email@example.com.
Deployment of WAPs
- All deployment of WAPs must be authorized by UBC IT.
- WAP hardware must be protected to ensure physical security mechanisms (e.g. locked cabinet, high ceiling mount, etc.) are in place to prevent theft, alteration, or misuse.
- All WAPs should be secured using a minimum of Wi-Fi Protected Access (WPA2) with a minimum of AES 128-bit encryption.
- Wired Equivalent Privacy (WEP) is prohibited for Wi-Fi network security, as it is insecure.
- It is recommended that Users connecting to WAPs, providing access to the UBC LAN, be configured to use the ”AutoConnect” ubcsecure automated client configuration tool. This will help prevent connecting to rogue WAPs, which have been setup with the same name (spoofing) to steal credentials.
- Console access must be password protected in compliance with the Passphrase and Password Protection standard.
- WAP and wireless controller management must be handled as follows:
- utilize secure protocols such as HTTPS, SSH, and CAPWAP;
- management must only be over the LAN interface;
- if SNMP is used in the management environment, all default SNMP community strings must be changed, otherwise it must be disabled;
- vendor defaults such as encryption keys, and administrative passwords must be changed.
- The use of Telnet or other insecure protocols is prohibited.
- The operating system or software code on WAP and wireless controllers should be patched and kept current to ensure proper protection from the latest security vulnerabilities.
- WAPs and wireless controllers must be replaced if they have reached end of life for software support.
Additional Requirements for Merchant Systems
- Users responsible for Merchant Systems must:
- ensure that a perimeter firewall is in place between any Wi-Fi network and Merchant Systems processing Payment Card Industry (PCI) Information. These firewalls must be configured to deny or control any traffic from the Wi-Fi environment to Merchant Systems;
- test for the presence of unauthorized WAPs on a quarterly basis. Note: Methods that may be used in the process include, but are not limited to, Wi-Fi network scans, physical/logical inspections of system components and infrastructure, network access control NAC), or Wi-Fi IDS/IPS; and
- report any unauthorized WAPs as a security incident, in compliance with the Reporting Information Security Incidents standard.
Related Documents and Resources
- Policy SC11, Management of the Wireless Network
- Policy SC14, Acceptable Use and Security of UBC Electronic Information and Systems
- UBC IT AutoConnect Secure Wireless Setup
- Passphrase and Password Protection standard
- Reporting Information Security Incidents standard
Last Revised: 2021-01