<?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: Content filtering for MAC OSx in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/content-filtering-for-mac-osx/m-p/428201#M94684</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/188254"&gt;@RussMc&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Do you use on-site Exchange at all? If not, you are essentially left with two options.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;GlobalProtect&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;GlobalProtect can be used to provide user-id information and your users would essentially just sign-in to GlobalProtect (or configure user certificates and always-on ideally) so that your macOS users map to their AD credentials (assuming you create users for them).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Authentication Policy&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;You can setup an authentication policy so that your macOS users are actually authenticated and map to a user properly. Essentially you would just trigger for any unknown user accessing any service and they would need to login via a web form.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Personally I would give these users GlobalProtect and tell them that they have to use it, or even enforce it across your entire network, because there's less friction and user involvement. You would simply setup a GlobalProtect internal gateway and allow the gateway and the GlobalProtect agent to keep the user-id information in place. This is less friction then authentication policy even if you don't setup an always-on certificate based method and simply have the users utilize on-demand mode.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 20 Aug 2021 20:19:01 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2021-08-20T20:19:01Z</dc:date>
    <item>
      <title>Content filtering for MAC OSx</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/content-filtering-for-mac-osx/m-p/428116#M94669</link>
      <description>&lt;P&gt;I am trying to finalize my content filtering for our PA 820 rollout. I have the user-ID, group mapping and content filtering rules (By group) working just fine for my windows PC's. Where I am stuck is trying to figure it out for all of our MAC OSx users. None of our MAC's are joined to our domain and I am not sure about adding them at this time. Is there a good source for configuring content filtering in this scenario?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Aug 2021 15:41:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/content-filtering-for-mac-osx/m-p/428116#M94669</guid>
      <dc:creator>RussMc</dc:creator>
      <dc:date>2021-08-20T15:41:20Z</dc:date>
    </item>
    <item>
      <title>Re: Content filtering for MAC OSx</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/content-filtering-for-mac-osx/m-p/428201#M94684</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/188254"&gt;@RussMc&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Do you use on-site Exchange at all? If not, you are essentially left with two options.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;GlobalProtect&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;GlobalProtect can be used to provide user-id information and your users would essentially just sign-in to GlobalProtect (or configure user certificates and always-on ideally) so that your macOS users map to their AD credentials (assuming you create users for them).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Authentication Policy&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;You can setup an authentication policy so that your macOS users are actually authenticated and map to a user properly. Essentially you would just trigger for any unknown user accessing any service and they would need to login via a web form.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Personally I would give these users GlobalProtect and tell them that they have to use it, or even enforce it across your entire network, because there's less friction and user involvement. You would simply setup a GlobalProtect internal gateway and allow the gateway and the GlobalProtect agent to keep the user-id information in place. This is less friction then authentication policy even if you don't setup an always-on certificate based method and simply have the users utilize on-demand mode.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Aug 2021 20:19:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/content-filtering-for-mac-osx/m-p/428201#M94684</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2021-08-20T20:19:01Z</dc:date>
    </item>
    <item>
      <title>Re: Content filtering for MAC OSx</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/content-filtering-for-mac-osx/m-p/428503#M94747</link>
      <description>&lt;P&gt;Yes, we have an onsite exchange server. With that said, what are my options there? I do have user ID set up for my exchange server. Should I add my file servers as well? Is this the best choice?&lt;/P&gt;</description>
      <pubDate>Mon, 23 Aug 2021 15:11:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/content-filtering-for-mac-osx/m-p/428503#M94747</guid>
      <dc:creator>RussMc</dc:creator>
      <dc:date>2021-08-23T15:11:45Z</dc:date>
    </item>
  </channel>
</rss>

