Setting up Watchdog requires some patience. Because the sensors use Network Chemistry's hardware, sensor installation was the easy part. But the MySQL installation, subsequent database modifications, JRE install and server software installation made the configuration tedious. Further, the product's Web-based interface is neither intuitive nor appealing; more extensive use of color and graphics would convey WLAN data better than the primarily text approach.
Without any summary or dashboard to display alert information, we had to rifle through audit reports for system alerts. Events are listed by location in chronological order, but grouping them by device is impossible. Packet capturing isn't supported either.
We tested the device-location feature by drawing several sets of boxes into the location editor to represent rooms in our lab environment. We indicated which sensors were installed where and, through the Web interface, initiated RF signature training with our clients. The system then displayed our client locations. Rogue devices determined to be outside our perimeter were of less concern to Watchdog than those inside. The included RADIUS authentication system allows or denies access based on location.
We defined simple security policies, such as "no rogue APs," but our choices were limited. Reporting consists mostly of one security audit report and device lists; only a few location-related reports are available.
The attacks Watchdog discovered were likewise limited. Although the company claims to catch DoS attacks, we couldn't trigger those alarms.