Configuring Client Settings Policy

Browser extension uses block pages to warn the end users about security incidents and prompts for additional permissions. There are four events which trigger a blocking page:

1. Accessing a site that is blocked by URL Filtering Check Point Software Blade on a Security Gateway that allows granular control over which web sites can be accessed by a given group of users, computers or networks. Acronym: URLF. policy – The block page blocks access to the site and warns the end user that attempted to enter the site that it is blocked by the policy.

2. Providing credentials in a phishing site – The block page warns the end user that it is a phishing site and the user is therefore blocked from providing credentials there.

3. Using corporate password in a non-corporate domain - End users are warned that use of corporate password in a non-corporate domain is prohibited, and that his/her corporate password was just exposed.

4. Accessing a local HTML file without the permission by the browser extension.

The blocking pages above are customizable. The following can be changed per each of them:

1. Company logo (replacing the Check Point logo).

2. Blocking page title.

3. Blocking page description.

The user may preview the change before saving the policy by pressing the preview button.

Note - The preview only works in the Chrome or Edge browsers, when the browser extension is installed.