|
|||||||||||||||||||||||||||
|
Wireless LAN Tools Part 3: Discovery and Planning continued
Continuous rogue detection To more easily recognize your own devicesand those you've investigated and then decided to ignoreedit name tables to add aliases, categories, and authorizations. In the preceding example, devices have been categorized based on observed traffic (i.e., APs send beacons, stations send probes). Aliases like "WAPG" have been added to improve readability. Some tools also let you mark devices as "authorized" or "trusted" so that monitors, alarms, and reports can highlight new (unmarked) devices. If you're responsible for watching for rogues 24/7 in a large network, consider deploying a wireless intrusion detection system (IDS). For example, Network Instruments Observer can gather traffic from Remote Probes placed at strategic locations throughout your network, letting you store, view, and analyze results from a central console. Other WLAN analyzers associated with paired sensor and IDS products include Network Chemistry, WildPackets, and AirMagnet. Dedicated WIDS engines like AirDefense can also export packet captures for review by third-party WLAN analyzers. Once you've detected a suspicious device, a WLAN analyzer can be used to drill-down and (hopefully) find the device as described previously. But wireless devices are by definition mobileby the time you investigate, a device could be long gone. Automated event responses can reduce the damage done. For example, scripts may be invoked to disable switch ports, block IP addresses, reset APs, or even issue 802.11 requests to disassociate/deauthenticate stations. WLAN analyzers don't usually take actions by themselves, but can invoke scripts or relay events to management systems that do.
|
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||