Wi-Fi Security — Practitioner
Publication details and purpose
- Publication: Wi-Fi Security — Practitioner
- Authority: Issued under the authority of the Head of the Canadian Centre for Cyber Security (Cyber Centre); unclassified.
- Effective date: March 31, 2022.
- Revision history: Revision 1, first release, March 31, 2022.
- Audience: Organizations of all sizes, public and private, that use Wi-Fi.
- Wi-Fi is used in homes, workplaces, and public places; increasing reliance on it makes wireless-network security essential to reducing cyber-threat risks.
- Wi-Fi performs critical tasks and may transmit sensitive or confidential information, including trade secrets, personal information (PI), and copyrighted material.
- A network is only as secure as its weakest link; Wi-Fi is an easy target for threat actors.
- Publication scope: vulnerabilities, recommended policies, technical controls, security measures, and additional network-wide security considerations.
1. Wi-Fi threat awareness
- First steps in securing a network:
- Build awareness.
- Identify risks.
- Remediate known vulnerabilities in poorly secured Wi-Fi.
1.1 Network attacks and risk reduction
| Risk or attack | Key facts and recommended response |
|---|---|
| Unpatched firmware | Outdated firmware can leave wireless networks vulnerable to breaches; threat actors may exploit unpatched firmware. Establish a patching policy with regular updates for all device firmware, including access points (APs) and controllers. |
| Insecure defaults | Devices may ship with known usernames/passwords, bridges between network ports or virtual local area networks (VLANs), firewall rules allowing all traffic, and AP client isolation turned off. Change default usernames and passwords to strong, unique credentials; harden every network device’s settings. |
| Shared networks | Separate spaces for roles such as staff and guests using client isolation, VLANs and switches, and firewall rules. Segment into security zones to reduce risk and attack surface. Within each division, separate wired and wireless networks into different segments. If firewall and network hardware block access between them, Wi-Fi attacks cannot directly reach wired devices and clients. Example: separate guest and staff networks, then split each into wired and wireless zones → four zones: two Wi-Fi and two wired. |
| Internet of Things (IoT) devices | Common in small office home office (SOHO) and small medium business (SMB) organizations. Poor security design and lack of software/firmware updates create significant risk. Avoid IoT devices if possible; otherwise segregate them onto a separate network. |
| Wardriving and parking-lot attacks | Wardriving is mobile reconnaissance, sometimes also an attack operation. Equipment may range from a van with wireless analysis tools (e.g., spectrum analyzer, powerful/highly directional antennas, mobile computing equipment) to a laptop, cell phone, or tablet. Wardriving is not always malicious and is often used to research common risks. Parking-lot attacks are more targeted and generally involve more than listening to wireless signals; targets may be outside conventional controls such as gates, secured doors, or cameras. Limit signal strength so nearby people sitting, driving, or walking cannot launch wireless attacks. |
| Device theft | Mobile Wi-Fi devices/modules may be easy to steal. A smart lightbulb in a public place may contain Wi-Fi credentials; an attacker who accesses it could later use them to connect to the network. Phones/tablets may hold sensitive data, including sensitive PI, and are easier to steal than desktop computers. Do not leave easily stolen devices containing sensitive information or access credentials in untrusted locations, unlocked, or physically unsecured. |
| Rogue APs | Common in public Wi-Fi locations (e.g., coffee shops, restaurants, airports). An attacker may impersonate a trusted local network; users searching for available networks or devices connecting automatically may authenticate to a malicious AP. Verify the correct network and use encrypted communication. A guest with organizational access can also spoof corporate Wi-Fi from nearby using a malicious AP, potentially causing data leaks and unauthorized access. |
| Weak authentication | Organizational use of a pre-shared key (PSK) rather than enterprise authentication is not recommended: everyone shares the passphrase, so it is not possible to identify who used it or whether access was legitimate. With Wi-Fi Protected Access (WPA) enterprise, use a password policy requiring passwords sufficiently long and complex to resist compromise. |
| Weak encryption algorithms | Weak or outdated algorithms can make Wi-Fi easy to compromise. Attackers can use wireless tools and need not physically plug into the network. Recommended algorithms are referenced in ITSP.40.062, Guidance on Securely Configuring Network Protocols, and ITSP.40.111, Cryptographic Algorithms for UNCLASSIFIED, PROTECTED A, and PROTECTED B Information. |
1.2 Breach examples
| Date / case | Details and consequences |
|---|---|
| 2015: ANTLabs InnGate routers | Zero-day vulnerability CVE-2015-0932 was discovered in InnGate routers. A zero-day is a computer or software vulnerability for which no patch is yet available. The vulnerability was quickly patched after discovery, but breaches affected 277 hotels, convention centres, and data centres. InnGate routers were commonly deployed on networks used by hotels and other organizations with guests. Attackers could take control of a router, install malware, attack connected systems, and completely control the Wi-Fi and wired networks to which guests connected. |
| 2015: WeWork | The commercial real estate company had poor Wi-Fi security for building tenants. Anyone could pay $25 to access a boardroom and Wi-Fi, scan the network, and obtain sensitive information from businesses using it. The issue was not limited to one building: many WeWork buildings used the same PSK. The incident exposed personal documents and other information, including driver’s licenses, passports, job applications, bank account credentials, contracts, and health records. |
| January–June 2021: IoT breaches | Kaspersky reported 1.51 billion IoT-device breaches, up from 639 million in 2020. Attacks typically used Telnet, which allows remote administration through a command-line interface. Attackers used them for distributed denial of service (DDoS) attacks, cryptocurrency mining, or pivoting to more valuable targets. The global pandemic increased the use and attention given to IoT devices. |
| Eduroam EAP misconfiguration | A misconfiguration was found on Eduroam, a free Wi-Fi network used by many universities across Europe. It could enable an “Evil Twin” attack: an attacker simulates the network and tricks devices into connecting to the wrong one. Since some operating systems do not validate the certificate when connecting, Wi-Fi credentials could be stolen. In the configuration described, Microsoft Challenge Handshake Authentication Protocol version 2 (MSCHAPV2) should have been used rather than the less secure Password Authentication Protocol (PAP). |
2. Best practices
2.1 Data structures
- Structuring resources makes provisioning, maintenance, and security easier, while ensuring sensitive data is accessible only to those who need it.
- Without structure, data may be placed anywhere, with no distinction between sensitive and public information.
2.1.1 Limiting information available
- Do not transmit sensitive information—e.g., business-proprietary, classified, confidential, or personal data—on open networks without additional encryption controls: nearby threat actors can intercept communications.
- Apply least privilege: each associate accesses only the files and resources required for their job.
- Further information: ITSG-33, IT Security Risk Management: A Lifecycle Approach.
2.1.2 Structuring classes of data
- Data classes help prevent sensitive data from leaving its protected area and limit damage from data or privacy breaches.
- Structure data to meet security and privacy needs and protect personal and confidential information.
| Class | Access and sensitivity | Examples and consequences |
|---|---|---|
| Class 1: Public data | Available to the public. Internal or external handling causes no harm to the business, clients, staff, or vendors. | Public webpages, brochures, business cards. |
| Class 2: Internal-only data | Intended for authorized personnel inside the organization; contains slightly sensitive information about operations, policies, or business plans. Unauthorized disclosure could cause minimal harm to the business. | Internal memos; business-related emails. |
| Class 3: Confidential data | Limited to a specific group with special clearance or clear permissions. May include PI whose compromise could cause great harm to the organization, individuals, and involved parties. | Proprietary business data, research data, software source code, other PI. Typically protected under federal and private-sector privacy legislation, including the Privacy Act and the Personal Information Protection and Electronic Documents Act (PIPEDA); may also be protected under Payment Card Industry Data Security Standard (PCI DSS) or regulated by the Investment Industry Regulatory Organization of Canada (IIROC) or the Mutual Fund Dealers Association (MFDA) of Canada. |
2.1.3 Structuring Wi-Fi and wired networks
- Wi-Fi devices can have multiple service set identifiers (SSIDs).
- Give each SSID its own VLAN to restrict access to internal network zones, alongside other security measures. Beware of defaults allowing all traffic between SSIDs or VLANs; see section 2.3.2.
- Guest Wi-Fi:
- Limit how long a guest password can be used (e.g., expire daily or issue guest passes), so only current guests can access the network.
- Further zoning information: ITSG-38, Network Security Zoning – Design Considerations for Placement of Services within Zones.
2.2 Policy-based controls
- Written policy should fully reflect the organization’s security and privacy position; technical controls implement policy.
- Technical controls without written policy may not withstand legal challenges.
| Policy | Required content |
|---|---|
| Acceptable use policy | Explains what a service, network, system, or website may and may not be used for; reduces legal liability and clarifies permitted use. Specify permitted classes of web access, since some website categories can draw attention to the organization and increase risk. Pair with enforcing controls such as a firewall web-filtering service. |
| Bring Your Own Device (BYOD) policy | For organizations allowing BYOD, enforce additional restrictions on devices in that environment. The policy must be enforceable and auditable. Anything that cannot be enforced or audited through technical controls should be treated as organizational risk. Define: (1) vetting process for applications and app/data permissions; (2) minimum security precautions; (3) classes of data stored on a device; (4) purpose of providing the connection method; (5) proper methods for discarding, copying, and synchronizing data; (6) requirements for method and type of device or application encryption; and (7) best practices considered necessary for secure operations. |
| Encryption and data security policy | Specify data that must be encrypted, acceptable algorithms, and parameters considered secure. Cover portable-media encryption, data at rest, and data in transit; define a standard according to data class. |
| Data governance policy | Define data retention, acceptable destruction methods, and general data lifecycle for each class. Set data-residency requirements and controls in place. |
| Password policy | Set requirements for secure, acceptable password use. Minimal best practices may suffice in low-sensitivity environments; high-sensitivity environments (e.g., finance and healthcare) should require stronger measures. Identify who can reset/change passwords and how credentials may be stored securely. The Cyber Centre does not typically recommend password expiration or password re-use. Further information: ITSAP.30.032, Best Practices for Passphrases and Passwords. |
| Patching policy | Specify equipment to patch and frequency. Cover mobile devices, computer operating systems (OSs), applications, anti-malware or anti-phishing systems, and network equipment. Schedule regular updates for all device firmware, APs, and controllers; identify authorized patching personnel; provide a back-out plan for failed updates; specify who must be notified of a failed update and within what time. |
| Public Wi-Fi policy | Standalone or part of another policy (e.g., IT and network communication policy); define appropriate use of coffee-shop, hotel, or unmanaged networks. May require encryption of all data in motion, restrict access to confidential data classes, or establish precautions to prevent threat actors obtaining sensitive organizational data. |
2.3 Technical controls
- Technical controls should prevent security incidents and ensure data integrity through safe, secure access.
- Without them, device data can be accidentally or maliciously intercepted, falsified, or compromised.
2.3.1 Wi-Fi encryption and PSK versus EAP
Encryption methods
| Method | Properties and recommendation |
|---|---|
| Wired Equivalent Privacy (WEP) | Easily compromised. Uses Rivest Cipher 4 (RC4), a stream cipher, for confidentiality and cyclic redundancy check (CRC32), a checksum algorithm, for integrity. |
| WPA 1 | Uses RC4 with Temporal Key Integrity Protocol (TKIP). Described as a fairly strong encryption algorithm, but not secure enough for businesses handling sensitive information; should be avoided. |
| WPA2 | Strong, widely used Wi-Fi encryption. Avoid Wi-Fi Protected Setup (WPS) with WPA2 to improve security. Uses 128bit Advanced Encryption Standard (AES) for encryption and Cipher Block Chaining Message Authentication Code Protocol (CCMP) for enhanced protection. |
| WPA3 | Newest and most secure form described. Uses 192bit AES in enterprise mode and 128bit in personal mode. Use for all new deployments if available. |
- Choose an encryption method compatible with all devices and network equipment.
PSK versus EAP
| Method | Use, strengths, limitations, and practices |
|---|---|
| PSK | Widely used for personal and SMB Wi-Fi; easy to implement, use, and support. Not recommended for business use of any kind because it lacks identity management and audit capabilities. A passphrase secures the network and encrypts traffic, but once shared, locking someone out requires changing the PSK. This disrupts users until they enter the new passphrase, and every device—including non-user devices such as wireless printers—must be updated. Small businesses have alternatives such as Lightweight Extensible Authentication Protocol (LEAP) and Protected Extensible Authentication Protocol Microsoft Challenge Handshake Authentication Protocol (PEAP-MS-CHAP). For large organizations, Extensible Authentication Protocol Transport Layer Security (EAP-TLS) is the most secure protocol that can be implemented. If PSK must be used, separate guests, staff, IT equipment, and IoT devices into different SSIDs, VLANs, and network segments, each with a unique passphrase. |
| EAP | Common in medium and large organizations. Supports username-and-password authentication for each device and TLS-based machine certificates. Most secure practice: use TLS certificates alongside EAP, allowing individual-device access to be disabled and improving visibility into Wi-Fi use; also makes attacks more difficult. Single-Sign On (SSO) with PEAP-MSCHAPV2 adds convenience by authenticating against a directory and reducing the number of logins users must remember. PEAP-MSCHAPV2 lets users enter credentials authenticated by the Remote Authentication Dial-In User Service (RADIUS) server inside the EAP-encrypted tunnel. |
2.3.2 VLANs and SSIDs
- An SSID is the commonly named Wi-Fi/network name that lets users identify a network to connect to.
- Never put PI or confidential data in an SSID.
- Personal users and small businesses commonly use one or two SSIDs (e.g., employee and guest networks).
- VLANs create virtual networks on the same physical infrastructure; most managed switches and firewalls support them.
- Combine VLANs with SSIDs to create separate security zones.
- Use a VLAN separate from all wired traffic for wireless traffic; configure the SSID accordingly.
- Put guest access on a restricted VLAN.
- Enable client isolation on all APs and SSIDs where available, preventing clients from communicating directly with one another.
- Printers and IoT devices may not support WPA-EAP because of cost constraints:
- Place them on a separate, secure network isolated from employee and guest networks.
- Do not let users access these networks; lock them down with a very strong password.
2.3.3 RADIUS
- RADIUS works with EAP to provide secure authentication using a RADIUS server reached from an AP or AP controller.
- Ensure the server uses a secure secret for devices to connect and authenticate; the secret is equivalent to a passphrase.
- Keep AP, AP-controller, and RADIUS-server software up to date; manage accounts closely.
- Many RADIUS servers connect to a directory for SSO authentication, typically Active Directory (AD) or an online cloud-directory service.
2.3.4 Directory security
- The directory validates credentials, in addition to the roles of APs, controllers, and RADIUS servers.
- Use role-based access control (RBAC) and physical and cyber security policies to protect the directory service.
- AD is commonly used as the directory for SSO authentication.
- Secure the entire directory server: OS, applications, services, accounts, permissions, firmware, and hardware.
2.3.5 Virtual private networks (VPNs)
| Type | Use and considerations |
|---|---|
| Public VPNs | Typically used to protect individual privacy or hide a point of origin on public Wi-Fi. Should never be used for business connections. Provider reliability may be difficult to assess if the organization lacks resources to investigate the service’s security and infrastructure. Public VPNs often run on servers in countries without strict privacy and data-protection laws. Providers may not vet technical staff who can access both unencrypted data and customer identification and payment information. |
| Corporate VPNs | Recommended for communicating with corporate resources over unmanaged networks, such as guest networks or public Wi-Fi. Create an encrypted tunnel from device to corporate network, protecting data in transit; an attacker listening on the network cannot understand data sent through the tunnel. |
2.3.6 WPS
- WPS makes network connection easier and is typically found on SOHO equipment.
- May allow connection by pressing a physical button on the AP instead of entering a password.
- Available only on WPA-encrypted networks.
- Modern versions also allow a 6-digit pin, which inherently bypasses network password requirements.
- Disable WPS completely on any wireless equipment used for business because it is not secure.
2.3.7 Endpoint security
- Every entry point into a wireless network is a potential attack vector; securing every endpoint helps mitigate risk.
- Mobile device management (MDM) software can identify mobile-device users and configure/push Wi-Fi, VPN, and authentication-token settings to devices.
- General endpoint-security recommendations: ITSP.70.012, Guidance for Hardening Microsoft Windows 10 Enterprise.
- General mobile-security information: ITSAP.00.001, Using Your Mobile Device Securely.
- Secure organizational BYOD devices through both policy and technical controls.
2.3.8 Physical security
- Physical security is as important as cyber security. It reduces the chance of:
- Someone resetting devices and connecting with default credentials.
- Connecting to the wired network through wireless equipment.
- Connecting to wireless equipment and stealing credentials.
- A factory-reset device may expose an entire subnetwork to anyone connecting to its default network—for example, where wireless devices or controllers are configured for trunking.
- An attacker may place a network-tapping device between a network and a wireless or wired device.
- Such products are readily available online and allow access to network traffic as a person-in-the-middle attack (PITMA).
- They can inject malicious code or websites into in-transit traffic, or provide remote access through a reverse VPN tunnel.
- Protect wireless infrastructure against physical access to both:
- Wireless components (e.g., Wi-Fi-connected IoT lightbulbs).
- Components bridging back into the wired network.
2.3.9 Wireless intrusion detection systems
- Wireless intrusion detection systems (WIDS) and wireless intrusion prevention systems (WIPS) detect and possibly mitigate active attacks carried out through radio frequency (RF).
- RF monitoring, combined with wired-network tools and protections, helps secure wireless infrastructure.
- One use: find and deactivate rogue APs connected to the wired network.
- These APs were not authorized and provisioned by the organization.
- They may use poor or no encryption and authentication, reducing visibility into connected devices and their locations.
- WIDS/WIPS can reduce how long rogue APs remain online; without them, rogue APs could go unnoticed indefinitely.
- Some systems are integrated into APs and use AP radios both to serve clients and monitor RF as sensors.
- Dual use may reduce user time or bandwidth because a radio can be in only one mode at a time: monitor mode, or sending and receiving as an AP.
2.4 Training-based controls
- Training should be mandatory for new and existing employees so new threats and policy changes are communicated.
- Everyone using Wi-Fi should understand:
- How to identify spoofed networks.
- How the organization’s Wi-Fi networks differ and why.
- Which uses are allowed on each SSID and VLAN segment.
- How to connect correctly.
- How and to whom to report wireless security incidents.
- How to obtain support.
2.4.1 General IT training
- Builds a foundation for wireless-device security, improves cyber-security practice at work, and raises awareness of personal cyber security.
- Topics: available systems, data classes, data lifecycle, user permissions, and policies for Wi-Fi and network resources.
- Users should have playbooks and procedures for secure interaction with systems and data.
- Review procedures regularly and update them when structure or software changes.
2.4.2 Device use
- Train users on wireless standards and device use.
- Showing users how to secure their own devices can improve workplace culture and security.
- Hands-on sessions demonstrating settings changes add variety and engage visual learners.
2.4.3 Wi-Fi security courses
- Online courses can improve general Wi-Fi security knowledge; select courses designed for average users.
- Cover best practices for unencrypted and public Wi-Fi, VPNs, and mobile devices, plus signs a device has been compromised and steps to address the issue.
3. Additional considerations
3.1 Legal implications
- Consider legal implications of policies and requirements before implementation; the publication is not legal advice.
- Seek a lawyer to ensure compliance with Canadian laws.
- Personal equipment, including BYOD or home equipment, may have legal implications.
- For penetration testers, set boundaries, limit scope to specific areas, and verify trustworthiness through industry reputation and references.
3.2 Increased technical support
- Implementing these technical controls requires additional technical support.
- Controls may prevent users working as they are accustomed to; devices may require extra steps or configuration.
- Protecting data is necessary, but the organization also needs resources to support users.
3.3 Availability
- Without available authentication or network infrastructure, users cannot access needed resources.
- Consider high availability and disaster recovery for critical infrastructure.
- Multiple APs can provide staggered coverage in nearby areas during an outage.
- Wireless signals are subject to jamming, so availability cannot be guaranteed.
- A robust wired network, ability to plug in critical devices, and segregation of wired and wireless networks are important.
- This can allow wireless attacks to be isolated from, and the wireless network disconnected from, the wired network if needed.
4. Summary
- Organizations need appropriate Wi-Fi policies, technical controls that enforce those policies, and staff training.
- The wireless landscape grows daily as more smart-enabled devices include Wi-Fi, and the threat landscape has never been larger.
- Securing the network and understanding threats helps protect a business environment for the future.
5. Supporting content
5.1 Abbreviations
| Abbreviation | Meaning |
|---|---|
| AD | Active Directory |
| AES | Advanced Encryption Standard |
| AP | Access Point |
| BYOD | Bring Your Own Device |
| CCCS | Canadian Centre for Cyber Security |
| CCMP | Cipher Block Chaining Message Authentication Code Protocol |
| CRC32 | Cyclic Redundancy Check |
| CSE | Communications Security Establishment |
| DDoS | Distributed Denial of Service |
| EAP | Extensible Authentication Protocol |
| GC | Government of Canada |
| HIPAA | Health Insurance Portability and Accountability Act |
| IIROC | Investment Industry Regulatory Organization of Canada |
| IoT | Internet of Things |
| IT | Information Technology |
| ITS | Information Technology Security |
| LEAP | Lightweight Extensible Authentication Protocol |
| MFDA | Mutual Fund Dealers Association |
| OS | Operating System |
| PCI DSS | Payment Card Industry Data Security Standard |
| PEAP | Protected Extensible Authentication Protocol |
| PEAP-MS-CHAP | PEAP Microsoft Challenge Handshake Authentication Protocol |
| PI | Personal Information |
| PITMA | Person-In-The-Middle-Attack |
| PSK | Pre-Shared Key |
| RADIUS | Remote Authentication Dial-In User Service |
| RBAC | Role-Based Access Control |
| RC4 | Rivest Cipher 4 |
| RF | Radio Frequency |
| SMB | Small Medium Business |
| SOHO | Small Office Home Office |
| SSID | Service Set Identifier |
| SSO | Single-Sign On |
| TKIP | Temporal Key Integrity Protocol |
| TLS | Transport Layer Security |
| VLAN | Virtual Local Area Network |
| VPN | Virtual Private Network |
| WEP | Wired Equivalent Privacy |
| WIDS | Wireless Intrusion Detection System |
| WIPS | Wireless Intrusion Prevention System |
| WPA | Wi-Fi Protected Access |
| WPS | Wi-Fi Protected Setup |
5.2 Glossary
- Authentication: A process or measure used to identify a user’s identity.
- BYOD: Employees use their own devices for business purposes; organizations may cover some of the cost. Because the organization does not own the device, it has little control over the security controls implemented on it.
- Classified information: A Government of Canada label for specific sensitive data whose compromise could harm the national interest, such as national defence, relationships with other countries, or economic interests.
- Confidentiality: The ability to protect sensitive information from access by unauthorized people.
- DDoS attack: An attack in which multiple compromised systems attack one target. The flood of incoming messages forces the target to shut down and denies service to legitimate users.
- Encryption: Converting information from one form to another to hide its content and prevent unauthorized access.
- Integrity: The ability to protect information from unintended modification or deletion, and to help determine whether information is what it claims to be. Integrity also applies to business processes, software application logic, hardware, and personnel.
- IoT: A network of everyday web-enabled devices capable of connecting and exchanging information with one another.
- Least privilege: Giving an individual only the privileges essential to authorized tasks. This limits damage from accidental, incorrect, or unauthorized use of an information system.
- Personal information (PI): Information about an identifiable individual recorded in any form.
- Threat: Any potential event or act, deliberate or accidental, or natural hazard that could compromise IT assets and information.
- Vulnerability: A flaw or weakness in the design or implementation of an information system or its environment that a threat actor could exploit to adversely affect an organization’s assets or operations.
- Wi-Fi: Wireless technology that connects devices such as laptops and smartphones to the Internet, using radio waves and a wireless router instead of a physical wired connection.
5.3 References
- Canadian Centre for Cyber Security, ITSP.40.062, Guidance on Securely Configuring Network Protocols, October 2020.
- Canadian Centre for Cyber Security, ITSP.40.111, Cryptographic Algorithms for UNCLASSIFIED, PROTECTED A, and PROTECTED B Information, August 2016.
- Cnet, “WeWork’s weak Wi-Fi security leaves sensitive documents exposed,” September 2019.
- IoT World Today, “IoT Cyberattacks Escalate in 2021, According to Kaspersky,” September 2021.
- Threat Post, “Thousands of university Wi-Fi networks expose log-in credentials,” September 2021.
- Canadian Centre for Cyber Security, ITSG-33, IT Security Risk Management: A Lifecycle Approach, November 2018.
- Canadian Centre for Cyber Security, ITSG-38, Network Security Zoning – Design Considerations for Placement of Services within Zones, May 2009.
- Canadian Centre for Cyber Security, ITSAP.30.032, Best Practices for Passphrases and Passwords, September 2019.
- Canadian Centre for Cyber Security, ITSP.70.012, Guidance for Hardening Microsoft Windows 10 Enterprise, March 2019.
- Canadian Centre for Cyber Security, ITSAP.00.001, Using Your Mobile Device Securely, December 2020.
Active recall
- What risks arise from unpatched firmware, insecure defaults, shared networks, IoT devices, rogue APs, weak authentication, and weak encryption—and what mitigations are recommended?
- How do the three data classes differ, and how should Wi-Fi, wired networks, SSIDs, VLANs, and guest access be structured?
- Compare WEP, WPA 1, WPA2, and WPA3; why is PSK not recommended for business use, and what authentication practices are recommended?
- What are the distinct roles of RADIUS, directory services, corporate VPNs, endpoint controls, physical security, and WIDS/WIPS in securing Wi-Fi?
- What policies, training, legal considerations, support needs, and availability measures should organizations address when securing Wi-Fi?