Wardriving is the practice of moving through an area, on foot or in a vehicle, and recording the wireless networks that a device can hear. The map itself is passive. The risk comes from what it reveals: networks that are open, weakly protected or poorly configured.
What does wardriving actually collect?
Public projects show the typical data. The WiGLE site describes itself as wireless network mapping and lets visitors search by location, network name (SSID) and the access point's hardware address (BSSID), and view networks by date range and signal quality. The records are about the existence and location of a network: its name, address, channel and rough signal strength.
Collecting this is not the same as breaking into anything. Rules about scanning radio signals and recording network details differ between countries and places, so check local law before doing it yourself.
Why does NIST care?
NIST SP 800-153, guidelines for securing wireless local area networks, divides WLAN attacks into passive and active. A passive attack is one where an unauthorized party only monitors communications without generating, altering or disrupting them, such as eavesdropping or traffic analysis. The guide notes the use of passive sensors cannot be detected through monitoring controls. It lists the use of active WLAN scanners, giving war driving tools as an example, among the things monitoring can detect, because they generate traffic.
The guide also flags rogue access points: an attacker sets up an access point that appears to be part of your network, which can give a backdoor into the wired network that bypasses perimeter controls like firewalls, and lets the attacker view and manipulate the communications of clients that connect to it.
What does wardriving expose in your own network?
Anything a stranger can learn from outside: the network name, that it exists, which hardware it runs, and above all how it is protected. An open network or old, weak encryption is visible in the beacon information. A network name that includes your company name tells an attacker which building to target. Mapping does not break anything, but it lets someone choose.
What does CISA recommend for wireless networks?
CISA's guidance on securing wireless networks warns that unsecured public wireless traffic is often sent in the clear, so sniffing tools can capture passwords and other data, and says to ensure all access points you connect to use at least WPA2 encryption. It advises confirming the name and password of a public hotspot before use to make sure you connect to a trusted access point, and denying file sharing on public networks.
A constructed example
A small clinic runs an old access point on its default settings with the clinic's name as the network name. A security student mapping the neighborhood for a class project records it with its encryption type. The clinic never knows. A review prompted by a neighbor's question finds that the access point is on the same network segment as the patient records server. The fix takes an hour: strong WPA2 or newer with a long passphrase, a guest network that is separate from the clinical network, a firmware update, and a neutral network name.
How to check or apply this
- Look at your network from outside: use a phone to list nearby networks and see what yours broadcasts.
- Use WPA2 at minimum, and newer where your devices support it, with a long unique passphrase.
- Change default administrator passwords and update access point firmware.
- Put guests and unmanaged devices on a separate network from systems with sensitive data.
- Choose a network name that does not identify your organization or device make.
- For business networks, scan for unknown access points and compare them with your inventory, as NIST describes for rogue device detection.
- On the road, avoid sensitive work on open networks and confirm hotspot names before connecting.
- Turn off file sharing when on public networks.
Quick check
Is wardriving illegal?
It depends on where you are and what you do. Passive listing may be treated differently from accessing a network. Check local law, and never connect to or use a network without permission.
Does hiding my network name make Wi-Fi safe?
No. Hiding the name does not replace strong encryption and a strong passphrase. Rely on the latter.
Sources
- WiGLE: Wireless Network Mapping
- NIST SP 800-153: Guidelines for Securing Wireless Local Area Networks (WLANs)
- CISA: Securing Wireless Networks
Last reviewed: 18 October 2026.