GuardianEdge Device Control is a component of the more robust GuardianEdge Data Protection Platform. This tool includes the GuardianEdge Device Control Auditor utility.
Even though the GuardianEdge Device Control package has fewer components than the entire GuardianEdge Data Protection Platform, it still makes use of a three-tiered architecture.
The GuardianEdge Device Control Server should first be installed on a server that is a member of an Active Directory domain. After installing the GuardianEdge Device Control Server, the GuardianEdge Device Control Management Console is installed. Last, the GuardianEdge Device Control Auditor is installed. To make use of the Auditor functionality that the audit scans remotely on endpoints, GuardianEdge Device Control Auditor needs to communicate remotely with the registry of Microsoft Windows machines.
This remote access to the registry can be obtained using one of two methods. The default scan protocol is Setup API. An additional scan protocol, WMI, may be useful if the endpoints in your network do not allow file and print sharing. Irrespective of how the auditor accesses the client machine, the Auditor will check policies created in the Management Console and are almost always distributed through the AD framework. The Novell eDirectory can also be used.
The policies can grant or restrict access to physical ports on the client machine to most devices, which would be attached to an endpoint.
The installation was a breeze and the device was running well inside of a half hour.
The documentation comes in a PDF download. The manuals are named similarly, and this can be a bit confusing.
Support is offered through phone, email and a website. Phone support for the regular class of customer is 20 percent of the purchase price, and premium support is 30 percent.
The pricing for the Guardian-Edge Device Control is $50 per endpoint. This places it in the upper echelon of products in