Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Safe Search Enhancement for Web Filtering

SUMMARY Learn about our safe search enhancement for Unified Threat Management (UTM) Web filtering solutions to enforce the safest Web browsing mode available, by default.

What's Next

Now that you’ve learned about safe search enhancement for Web filtering, you'll be interested to know how to disable the safe search function. Check out juniper-local, websense-redirect, and juniper-enhanced for more information.

Safe Search Enhancement for Web Filtering Overview

Benefits of Safe Search Enhancement for Web Filtering

  • Provides the safest Web browsing mode available, by default.

  • Protects the HTTPS-based search engine cache. This protection is a key security feature requirement for organizations with multiple Web users in educational, financial, health-care, banking, and corporate segments. In a campus or branch, enabling a default safe search solution for all users and blocking the search engine cache provides secure and comfortable Web browsing.

Features of Safe Search Enhancement for Web Filtering

You use UTM Web filtering to manage Web browsing by preventing access to inappropriate Web content. To do this, you use the following Web filtering solutions:

  • Redirect Web filtering

  • Local Web filtering

  • Enhanced Web Filtering (EWF)

We've enhanced the safe search functionality for these UTM Web filtering solutions to provide an extremely safe search environment for the Web user. Table 1 describes the features of the safe search enhancement.

Table 1: Safe Search Enhancement Features

Safe Search Feature

Description

Default safe search

By enabling the safe search enhancement feature, you enforce the safest Web browsing mode available by default on the well-known search engines. Doing so helps those users that are not using the strictest safe search settings.

If you enable the safe search feature on your security device, it enforces the search service to the strictest mode by URL query rewriting, which is transparent to you. For example, when you do a search request on the search engines Google, Bing, Yahoo, or Yandex, the safe search feature rewrites the requested URLs to the safest search URLs.

Here're a few examples of requested and converted URLs:

Blocking search engine cache

By blocking the search engine cache on the well-known search engines, you can hide your Web-browsing activities from other users if you are a part of an organization that has multiple Web users in educational, financial, health-care, banking, and corporate segments.

To block the search engine cache, you configure a general URL block pattern and category for the search engine cache service.

You can disable the safe search option at the Web filtering-level and profile-level configurations. See juniper-local, websense-redirect, and juniper-enhanced.

Limitations of Safe Search Enhancement for Web Filtering

  • For HTTP safe search enhancement, you must enable stream mode by enabling the http-reassemble option at the [edit security utm default-configuration web-filtering] hierarchy level. If you don't enable stream mode, you can't use the safe search feature. As a result, the system sends an HTTP 302 redirect message to the user.

  • For HTTPS safe search enhancement, you must enable the SSL proxy service on the security policy. If SSL proxy bypasses the HTTPS traffic, then the safe search feature also bypasses the HTTPS traffic.