To ensure secure communication between the agent and Jamf Protect server, the following items are created in the system keychain:
The certificate signing request (CSR) certificate named for your organization and the associated private key
The root certificate authority, named for your organization
A Jamf Protect client certificate, named “JamfProtect Client <UUID>”, and the associated private key named "Jamf Protect Private Key"
A Jamf Protect Public Key
A Jamf Protect Web-Services Security (WSS) Authorizer Key
A Jamf Protect Verification Certificate used to verify signed updates from backend operations
The following data points are secured in the keychain and used to manage Jamf Protect:
- The last check-in time of the agent
com.jamf.protect.daemon.checkin- The last compliance check-in of the agent
com.jamf.protect.daemon.insights- Bootstrap information for initial communication and configuration
com.jamf.protect.daemon.token- The configuration of the Jamf Protect agent
com.jamf.protect.daemon.config