- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
We are trialling Jamf Protect but this doesn't support SSL decryption which we use as standard (https://docs.jamf.com/jamf-protect/documentation/Network_Communication_Used_by_Jamf_Protect.html)
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. ec2-54-75-144-236.eu-west-1.compute.amazonaws.com by the time they hit Palo Alto.
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?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!