For version 3.0, we have redesigned the how Policy Filters are configured and applied. Two distinct benefits came out of this.

  • Granular targeting is now a lot more intuitive in terms of applying combinations of Policy Filters.
  • It is now a lot easier for us to add additional filters to Privilege Guard.

The new Computer Filter allows you to target Privilege Guard (Edit: now Defendpoint) Policies based on the hostname or the IP Address of the endpoint. This can be used as an alternative to, or in combination with, Group Policy based computer targeting.

Hostnames can be defined as an explicit list in each Computer Policy or, if you use a naming convention within your infrastructure, you can use wildcards to target a wider scope of computers.

If you prefer to use IP Addresses, then these can also be defined as explicit lists. You can also add wild cards and ranges to any octet in the IP Address.

In addition to local computers, Privilege Guard Policies can also target privileges based on remote clients connecting via Remote Desktop Services. This means that privileges can be granted or revoked depending on the relative location of the user.

For example, you can now grant admin rights for an application, script or task to a user who is connecting from within the corporate network (based on IP Address), but prohibit admin rights to the same user if they are connecting through a tunneled VPN.

Used in combination with application whitelisting, the Computer Filter can also be used to restrict access to corporate applications licensed under volume license and client license agreements.

Introducing Defendpoint

Edit: Privilege Guard has now evolved into the brand new security suite, Defendpoint, which encompasses Privilege Management, Application Control and Sandboxing. For more information, please visit