Configuring Redirect Web Filtering (J-Web Procedure)

Configuring Redirect Web Filtering Custom Objects (J-Web Procedure)

To configure Web filtering using the J-Web configuration editor, if you are using custom objects, you must first create those custom objects. (URL pattern list, custom URL category list).

Note: Rather than or in addition to custom object lists, you can use included default lists and included whitelist and blacklist categories. See Integrated Web Filtering Profiles for profile list information.

Configure a URL Pattern List Custom Object as follows:

Note: Because you use URL pattern lists to create custom URL category lists, you must configure URL pattern list custom objects before you configure a custom URL category list.

Select Configure>Security>UTM>Custom Objects.
From the URL Pattern List tab, click Add to create URL pattern lists.
Next to URL Pattern Name, enter a unique name for the list you are creating. This name appears in the Custom URL Category List Custom Object page for selection.

Next to URL Pattern Value, enter the URL or IP address you want added to list for bypassing scanning.

Note: URL pattern wildcard support—The wildcard rule is as follows: \*\.[]\?* and you must precede all wildcard URLs with http://. You can only use “*” if it is at the beginning of the URL and is followed by a “.”. You can only use “?” at the end of the URL.

The following wildcard syntax IS supported: http://*.juniper.net, http://www.juniper.ne?, http://www.juniper.n??. The following wildcard syntax is NOT supported: *.juniper.net , www.juniper.ne?, http://*juniper.net, http://*.

Click Add to add your URL pattern to the Values list box.
The list can contain up to 8192 items. You can also select an entry and use the Delete button to delete it from the list. Continue to add URLs or IP addresses in this manner.
Click OK to check your configuration and save the selected values as part of the URL pattern list you have created, then click Commit Options>Commit.
If the configuration item is saved successfully, you receive a confirmation and you must click OK again. If it is not saved successfully, you can click Details in the pop-up window that appears to discover why.

Configure a custom URL category list custom object as follows (see Understanding URL Whitelists for overview information on URL whitelists):

Note: Because you use URL Pattern Lists to create custom URL category lists, you must configure URL pattern list custom objects before you configure a custom URL category list.

Select Configure>Security>UTM>Custom Objects.
From the URL Category List tab, click Add to create URL category lists.
Next to URL Category Name, enter a unique name for the list you are creating. This name appears in the URL Whitelist, Blacklist, and Custom Category lists when you configure Web filtering global options.
In the Available Values box, select a URL Pattern List name from the list for bypassing scanning and click the right arrow button to move it to the Selected Values box.
Click Add to add your entry to the Values list box.
Within this box, you can select an entry and use the up and down arrows to change the order of the list. You can also select an entry and use the X button to delete it from the list. Continue to add URLs or IP addresses in this manner.
Click OK to check your configuration and save the selected values as part of the URL category list you have created, then click Commit Options>Commit.
If the configuration item is saved successfully, you receive a confirmation and you must click OK again. If it is not saved successfully, you can click Details in the pop-up window that appears to discover why.

Configuring Redirect Web Filtering Feature Profiles (J-Web Procedure)

Now that your custom objects have been created, you can configure the redirect Web filtering feature profile.

Select Configure>Security>UTM>Global options.
In the Web Filtering tab, next to URL whitelist, select the Custom URL list you created from the available options.
This is the first filtering category that both integrated and redirect Web filtering use. If there is no match, the URL is sent to the Websense server.
Next to URL blacklist, select the Custom URL list you created from the list. This is the first filtering category that both integrated and redirect Web filtering use. If there is no match, the URL is sent to the Websense server.
In the Filtering Type section, select the type of Web filtering engine you are using.
In this case, you would select Websense Redirect.
Click OK to save these values.
If the configuration item is saved successfully, you receive a confirmation and you must click OK again. If it is not saved successfully, you can click Details in the pop-up window that appears to discover why.
Select Web Filtering, under UTM, in the left pane.
Click Add o create a profile for redirect Web filtering. (To edit an existing item, select it and click the Edit button.)
In the Main tab, next to Profile name, enter a unique name for this Web filtering profile.
Select the Profile Type. In this case, select Websense.
Next to Account, enter the user account for which this profile is intended.
Next to Server, enter the Websense server name.
Next to Port, enter the port number for communicating with the Websense server (default ports are 80, 8080, and 8081).
Next to Sockets, enter the number of sockets used for communicating between the client and server (the default here is 1).
Next to Timeout, enter a timeout limit for requests.
Once this limit is reached, fail mode settings are applied. The default here is 10 seconds. You can enter a value from 10 to 240 seconds.
Next to Custom Block Message, enter a custom message to be sent when HTTP requests are blocked.
Select the Fallback options tab.
Next to Default Action, select Log and permit or Block.
Next to Server Connectivity, select Log and permit or Block as the action to occur when a request fails for this reason.
Next to Timeout, select Log and permit or Block as the action to occur when a request fails for this reason.
Next to Too Many Requests, select Log and permit or Block as the action to occur when a request fails for this reason.
Click OK to check your configuration and save it as a candidate configuration, then click Commit Options>Commit.
If the configuration item is saved successfully, you receive a confirmation and you must click OK again. If it is not saved successfully, you can click Details in the pop-up window that appears to discover why.

Configuring Redirect Web Filtering UTM Policies (J-Web Procedure)

Next, you configure a UTM policy for Web filtering to which you attach the content filtering profile you have configured.

Select Configure>Security>Policy>UTM Policies.
From the UTM policy configuration window, click Add to configure a UTM policy.
The policy configuration pop-up window appears.
Select the Main tab in the pop-up window.
In the Policy Name box, enter a unique name for the UTM policy you are creating.
In the Session per client limit box, enter a session per client limit from 0 to 20000 for this UTM policy.
For Session per client over limit, select one of the following: Log and Permit or Block.
This is the action the device takes when the session per client limit for this UTM policy is exceeded.
Select the Web Filtering profiles tab in the pop-up window.
Next to HTTP profile, select the profile you have configured from the list.
Click OK to check your configuration and save it as a candidate configuration, then click Commit Options>Commit.
If the policy is saved successfully, you receive a confirmation and you must click OK again. If the profile is not saved successfully, you can click Details in the pop-up window that appears to discover why.

Attaching Redirect Web Filtering UTM Policies to Security Policies (J-Web Procedure)

Next, you attach the UTM policy to a security policy that you create.

Select Configure>Security>Policy>FW Policies.
From the Security Policy window, click Add to configure a security policy with UTM. This takes you to the policy configuration pop-up window.
In the Policy tab, enter a name in the Policy Name box.
Next to From Zone, select a zone from the list.
Next to To Zone, select a zone from the list.
Choose a Source Address.
Choose a Destination Address.
Choose an Application. Do this by selecting junos-<protocol> (for all protocols that support Web filtering, http in this case) in the Application Sets box and clicking the —> button to move them to the Matched box.
Next to Default Policy Action, select one of the following: Deny-All or Permit-All.
Note: When you select Permit for Policy Action, several additional fields become available in the Applications Services tab, including UTM Policy.
Select the Application Services tab in the pop-up window.

Next to UTM Policy, select the appropriate policy from the list.

This attaches your UTM policy to the security policy.

Note: There are several fields on this page that are not described in this section. See the section on Security Policies for detailed information on configuring security policies and all the available fields.

Click OK to check your configuration and save it as a candidate configuration, then click Commit Options>Commit.
If the policy is saved successfully, you receive a confirmation and you must click OK again. If the profile is not saved successfully, you can click Details in the pop-up window that appears to discover why.
You must activate your policy in order to apply it.