Smoothwall not enforcing safe search on Ecosia.org search engine

[dapaulio]

I have been asked by Senior Staff whether we would be able to use Ecosia as our search engine (A charity org that plants trees for every search - sound very world changing YAWN sorry), however I have found that restricted users are able to disable the safe search filter and search for all sorts. Our smoothwall enforce safesearch rule does not prevent users from disabling this feature.

 

Evidently this is definitely a no go if students are able to circumnavigate our smoothwall safe search policy.

 

Given that it is for a "good cause" I would like to go back to the senior management with a little more than a straight "no" and also knowing that i have tried my best to facilitate this.

 

TIA

[Steve21]

It runs Bing underneath (yes really ) so did you try doing the Bing safesearch (or strict whatever it called it nowadays) terms on it?

 

Steve

[ibpalle]

If HTTPS inspection is not turned on, then it likely won't be able to enforce the safesearch. I'll ask our blocklist team as well to see if they have some insight.

[dapaulio]

On my smoothwall, i have content mod policies enforcing safesearch and safesearch via connect header (Everyone, everything, everywhere)

 

Https inspection to decrypt and inspect all traffic.

 

just come to realise whilst testing Google, yahoo, bing, etc i can now manually override safesearch setting on all search engines as a restricted user.

 

Can anyone else confirm as i am suspicious i may need to open smoothwall ticket?

[Steve21]

Not at work to test it currently, but just from the way you phrased that I take it you have decrypt before modify?

 

Steve

[dapaulio]

Not at work to test it currently, but just from the way you phrased that I take it you have decrypt before modify?

 

Steve

 

Hi Steve,

 

Unless i have misunderstood, Content Modification Policy and Https inspection Policy are configured within separate windows therefore I would expect content mod enforce safesearch policies would be executed if https inspection policies are defined as they are.

 

Is that not the case. are they overlapped somewhere else?

[ibpalle]

Hi all

 

A couple of replies:

 

Ecosia.org - you have to use enforce safesearch and https inspection currently. It should be possible with the content header safesearch content mod but this is currently being looked into by our blocklist team.

 

Safesearch setting may be able to be set by the user but should revert once they perform a search if the via content header content mod is enabled (google/bing etc).

 

The enforce safesearch content mod will need HTTPS inspection in order to work. Both can be used simultaniously.

 

Also be aware that the QUICK protocol may cause some weird results if not blocked. Here is a KB about QUICK