User Identification for Policy Enforcement

Administrator Help | TRITON AP-WEB and Web Filter & Security | Version 8.0.x

To apply policies to users and groups, Websense software must be able to identify the user making a request, given the originating IP address. Various identification and authentication methods are available for the on-premises software:

A Websense transparent identification agent works in the background to communicate with a directory service and identify users (see Identifying on-premises users transparently).

Websense software prompts users for their network credentials, requiring them to log on when they open a web browser (see Manual authentication).

(TRITON AP-WEB only) Content Gateway uses one or more several supported methods (including Integrated Windows Authentication, Legacy NTLM, LDAP, and RADIUS) to authenticate user requests (see the Content Gateway manager Online Help).

This option may be used in conjunction with a transparent identification agent to provide a fallback method for applying user-based policies when user authentication is unavailable.

(Web Filter & Security only) A third-party integration product identifies or authenticates users, and then passes user information to Websense software.

A list of supported integration products is available in the Deployment and Installation Center.

With the Web Hybrid module, the hybrid service must likewise be able to identify or authentication users to apply user and group based policies.

A component called Websense Directory Agent collects the information used to identify users (see Identification and authentication of hybrid users).

The TRITON AP-WEB client software is installed on client machines to provide transparent authentication, enforce use of the hybrid service, and pass authentication details to the hybrid service.

Single sign-on provides authentication using an identity provider that communicates with your directory service.

Ping Federate is currently the only supported identity provider.