<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Block pornographic Google images. in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46584#M34244</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It appears that the safesearch files are working, but...&amp;nbsp;&amp;nbsp; when I go to Google and type a search for something explicit, it does the search via https: and goes through, if I search again by stripping the S off of https: the policy is in affect. If I&amp;nbsp; lock safesearch in chrome the policy still works. The policy also disables the ability to unlock safesearch, but I can bypass that by closing the browser, cleaning out cashed pages and starting all over again, I can again reach explicit images bypassing my URL filter. What am I doing wrong and what else can I do, so that this control is effective. First step is google, next will be Bing and Yahoo, but I first want to understand what I'm doing wrong with Google.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 Mar 2013 20:48:02 GMT</pubDate>
    <dc:creator>JeffC_</dc:creator>
    <dc:date>2013-03-14T20:48:02Z</dc:date>
    <item>
      <title>Block pornographic Google images.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46580#M34240</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have URL filtering configured that blocks pornography, but if I search in Google for pornography and then click on images, pornographic images are accessible.&amp;nbsp; I know that I can block these in Chrome browser, but how do I block them as a policy via the firewall?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Mar 2013 20:34:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46580#M34240</guid>
      <dc:creator>JeffC_</dc:creator>
      <dc:date>2013-03-13T20:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: Block pornographic Google images.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46581#M34241</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here is how you can do it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A __default_attr="1399" __jive_macro_name="document" class="jive_macro jive_macro_document" href="https://live.paloaltonetworks.com/"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Mar 2013 22:07:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46581#M34241</guid>
      <dc:creator>wesa</dc:creator>
      <dc:date>2013-03-13T22:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: Block pornographic Google images.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46582#M34242</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you, will safesearch 4.1 work with PAN-OS 5.0?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Mar 2013 22:25:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46582#M34242</guid>
      <dc:creator>JeffC_</dc:creator>
      <dc:date>2013-03-13T22:25:37Z</dc:date>
    </item>
    <item>
      <title>Re: Block pornographic Google images.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46583#M34243</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it works with 5.0&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Mar 2013 13:17:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46583#M34243</guid>
      <dc:creator>wesa</dc:creator>
      <dc:date>2013-03-14T13:17:07Z</dc:date>
    </item>
    <item>
      <title>Re: Block pornographic Google images.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46584#M34244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It appears that the safesearch files are working, but...&amp;nbsp;&amp;nbsp; when I go to Google and type a search for something explicit, it does the search via https: and goes through, if I search again by stripping the S off of https: the policy is in affect. If I&amp;nbsp; lock safesearch in chrome the policy still works. The policy also disables the ability to unlock safesearch, but I can bypass that by closing the browser, cleaning out cashed pages and starting all over again, I can again reach explicit images bypassing my URL filter. What am I doing wrong and what else can I do, so that this control is effective. First step is google, next will be Bing and Yahoo, but I first want to understand what I'm doing wrong with Google.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Mar 2013 20:48:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46584#M34244</guid>
      <dc:creator>JeffC_</dc:creator>
      <dc:date>2013-03-14T20:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: Block pornographic Google images.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46585#M34245</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ya, I looking at the same thing, what I notice is if you set your PA as a Cert authority on your network you can set it to decrypt the search traffic only. This should allow you to block that traffic in theory. I have not had a chance to test it out yet. As for Bing I have been looking into that myself and noticed a couple of things. You don’t have to worry about the https with Bing it doesn’t really search that way. As for the filter:&lt;/P&gt;&lt;P&gt;adlt=off is when safesearch is set to off&lt;/P&gt;&lt;P&gt;adlt=moderate is when moderate search is turned on&lt;/P&gt;&lt;P&gt;adlt=strict is for Strict searching&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I have not had time to create and application for it to test yet.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 16 Mar 2013 21:32:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46585#M34245</guid>
      <dc:creator>murphyj</dc:creator>
      <dc:date>2013-03-16T21:32:14Z</dc:date>
    </item>
    <item>
      <title>Re: Block pornographic Google images.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46586#M34246</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;JeffC, true, google search uses SSL, so you would need also to configure Decryption Policy. Page 361 of PAN-OS 6.1 Admin Guide, has basic information on it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Apr 2015 16:34:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46586#M34246</guid>
      <dc:creator>Sobolenko</dc:creator>
      <dc:date>2015-04-24T16:34:38Z</dc:date>
    </item>
    <item>
      <title>Re: Block pornographic Google images.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46587#M34247</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Without ssl decryption the PaloAlto won't be able to see what is traversing in https.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Apr 2015 13:32:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-pornographic-google-images/m-p/46587#M34247</guid>
      <dc:creator>hvcomputech</dc:creator>
      <dc:date>2015-04-27T13:32:53Z</dc:date>
    </item>
  </channel>
</rss>

