This document describes how to configure Jamf Pro to distribute the SurePath AI proxy PAC URL and root CA certificate to Apple devices.

This document covers creating the required policy that distributes the proxy configuration and the root CA certificate via the Jamf Pro platform. It does not include steps on any other parts of the Jamf platform including initial Jamf configuration or device enrollment.

SurePath AI distributes its proxy information via a Proxy Auto-Config (PAC) file. This PAC file contains all the information needed to direct only generative AI traffic to the SurePath AI proxy service while sending other traffic via their normal route.

The use of a PAC file also allows SurePath AI to update the list of generative AI domains. Most operating systems and browsers will request the PAC file every 1-2 hours and if a new file can’t be retrieved the current one will continue to be used.

Just like other network security and SASE vendors, certificate trust allows SurePath AI to intercept and apply policy to connections to generative AI website. The SurePath AI root CA certificate needs to be trusted by all devices that need to be governed by SurePath AI.

Jamf Pro does not natively support the Global HTTP Proxy MDM payload however, Jamf does allow via profile signing, to push non-native Apple MDM payloads. SurePath AI has created a signed Apple profile mobileconfig file that when uploaded to Jamf Pro will distribute both the SurePath AI proxy PAC URL and the SurePath AI root CA certificate via a single Jamf Pro configuration profile.

Please reach out to your SurePath AI account team to get your signed Apple profile (mobileconfig) file which contains both the proxy PAC URL and the SurePath AI root CA certificate necessary for this integration.

SurePath AI provides a tool for verifying that an endpoint is configured to properly integrate with SurePath AI's platform. After completing the steps above and verifying the configuration has been deployed to the desired devices administrators can verify the integration by visiting https://ready.surepath.ai.

A test will be run as soon as the page is loaded. If both tests show green Valid results, the endpoint is properly integrated and GenAI traffic originating from that endpoint will be processed by SurePath AI.

If the Certificate Trust test shows a red Invalid result, it means that the SurePath AI root certificate is not trusted by the device or browser. This could be the result of certificate not being deployed to the device yet. Please check the device's local certificate trust store for the SurePath AI Root CA certificate. If the certificate has been deployed (and/or verified installed), it's possible the device might need to be restarted for the browser to read the newly added SurePath AI root CA certificate.

If the Network Configuration test shows a red Invalid result, it means that the SurePath AI platform is not receiving traffic from the endpoint. This is most likely due to the network configuration not being pushed to the device. Some browsers or applications, like Firefox, ignore system-level proxy settings and have internal proxy settings that will need to be configured separately from the system-level settings that are configured in this document.

Please reach out to your SurePath AI account team if you have any questions or issues with the SurePath AI integration.