|1107 / KB-51||Guardian||All|
This article explains how to enforce SafeSearch across all major search engines in order to help prevent unsuitable content from being presented to the user.
Many search engines provide some form of SafeSearch which when enabled aims to prevent unsuitable content from appearing in the search results. Guardian can force the use of SafeSearch on many services including Google™, Yahoo!®, Bing® and ASK™
This article will help you set up your content modification policies so that they are effective across all supported search engines.
Smoothwall provides two content modification policies to enforce SafeSearch.
The first content modification policy is named Force SafeSearch. This policy requires a HTTPS Decrypt and Inspect policy to be most effective. If you cannot or do not wish to employ a HTTPS Decrypt and Inspect policy then Guardian will not be able to enforce SafeSearch for any search engine which uses HTTPS.
To set up the Force SafeSearch content modification policy do the following:
- Ensure a HTTPS Decrypt and Inspect policy has been set up — see https://help.smoothwall.net/Latest/Content/modules/guardian3/cgi-bin/guardian/httpspolicywiz.htm
- Create a content modification where the What is Everything, and that it applies Force SafeSearch — see https://help.smoothwall.net/Latest/Content/modules/guardian3/cgi-bin/guardian/contentmodpolicywiz.htm
At this point you should find that SafeSearch is enforced across all major search engines. Any attempts to disable SafeSearch will fail and it will automatically be re-enabled by Guardian.
SafeSearch via CONNECT header
The second content modification policy is named SafeSearch via CONNECT header. This policy does not require a HTTPS Decrypt and Inspect policy to work but will only enforce SafeSearch for the below services:
- Google Search Engine
- Bing Search Engine
- Pixabay Image Search Engine
To set up the SafeSearch via CONNECT header content modification policy do the following:
- Create a content modification where the What is Web Search, and that it applies SafeSearch via CONNECT header — see https://help.smoothwall.net/Latest/Content/modules/guardian3/cgi-bin/guardian/contentmodpolicywiz.htm
|Last updated:||Author:||Contributions by:|
|27th January 2017||Christopher Smith|