<?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 SSL Decryption Exclusions Jamf Protect in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/ssl-decryption-exclusions-jamf-protect/m-p/442125#M1908</link>
    <description>&lt;P&gt;We are trialling Jamf Protect but this doesn't support SSL decryption which we use as standard (&lt;A href="https://docs.jamf.com/jamf-protect/documentation/Network_Communication_Used_by_Jamf_Protect.html" target="_blank"&gt;https://docs.jamf.com/jamf-protect/documentation/Network_Communication_Used_by_Jamf_Protect.html&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above doc lists some URL's that need to be excluded from SSL decryption but we are having problems getting it to work. Packet captures show that the URL's given are being resolved to one of many different addresses e.g.&amp;nbsp;&lt;EM&gt;ec2-54-75-144-236.eu-west-1.compute.amazonaws.com&amp;nbsp;&lt;/EM&gt;by the time they hit Palo Alto.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We obviously can't add every possible address to our exclusions so the Jamf Environment Test Tool comes back with SSL errors. Has anyone had any luck getting Jamf Protect to work? Or have any suggestions on how to add amazonaws.com URL's to SSL decryption?&lt;/P&gt;</description>
    <pubDate>Wed, 20 Oct 2021 08:50:21 GMT</pubDate>
    <dc:creator>Craig-f3</dc:creator>
    <dc:date>2021-10-20T08:50:21Z</dc:date>
    <item>
      <title>SSL Decryption Exclusions Jamf Protect</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/ssl-decryption-exclusions-jamf-protect/m-p/442125#M1908</link>
      <description>&lt;P&gt;We are trialling Jamf Protect but this doesn't support SSL decryption which we use as standard (&lt;A href="https://docs.jamf.com/jamf-protect/documentation/Network_Communication_Used_by_Jamf_Protect.html" target="_blank"&gt;https://docs.jamf.com/jamf-protect/documentation/Network_Communication_Used_by_Jamf_Protect.html&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above doc lists some URL's that need to be excluded from SSL decryption but we are having problems getting it to work. Packet captures show that the URL's given are being resolved to one of many different addresses e.g.&amp;nbsp;&lt;EM&gt;ec2-54-75-144-236.eu-west-1.compute.amazonaws.com&amp;nbsp;&lt;/EM&gt;by the time they hit Palo Alto.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We obviously can't add every possible address to our exclusions so the Jamf Environment Test Tool comes back with SSL errors. Has anyone had any luck getting Jamf Protect to work? Or have any suggestions on how to add amazonaws.com URL's to SSL decryption?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Oct 2021 08:50:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/ssl-decryption-exclusions-jamf-protect/m-p/442125#M1908</guid>
      <dc:creator>Craig-f3</dc:creator>
      <dc:date>2021-10-20T08:50:21Z</dc:date>
    </item>
  </channel>
</rss>

