Posted on 05-17-2025 03:31 PM
Hi there,
I’m wondering if it’s possible to configure Jamf Protect to alert on all activities related to Jamf Connect Privilege Elevation.
If not directly supported, how do you typically monitor these events using Jamf Protect?
Thanks in advance!
Posted on 05-18-2025 03:29 PM
To write custom analytics in Jamf Protect, besides understanding the syntax, you need to know what the log looks like, what fields are present in the log, and which field corresponds to what value in the custom analytics. I don’t understand how to figure this out. For example, I generate events where I escalate privileges using Jamf Connect — how can I understand what this activity looks like on macOS? How can I find out how events are mapped to those used for custom analytics?
05-19-2025 05:04 AM - edited 05-19-2025 05:15 AM
To Monitor Jamf Connects Privilege Escalation you just need to make a custom log filer for "subsystem == "com.jamf.connect.daemon" && category == "PrivilegeElevation"".
I don’t think you can directly hook in what was done only while admin access is granted by Jamf Connect as Connect is adding the user to the admin group then setting a daemon to remove the user at a predetermined time. In essence you are still making the user an unsupervised Admin, which is why I recommend against using this function of Jamf Connect and just getting an EPM tool.
You can monitor for sudo events simply enough with $event.type == 1 AND $event.process.tty != nil AND $event.process.signingInfo.appid == "com.apple.sudo". Though You would need to write analytics as you go along for the different things you want to monitor for.
I recommend browsing Jamf Protects GitHub, there are some pretty useful analitics in there. Also make sure what you are needing is not baked in to the CIS L1 and L2 reporting that Jamf Protect has built in.
https://github.com/jamf/jamfprotect
https://docs.jamf.com/jamf-protect/administrator-guide/Configuring_Unified_Log_Filters.html
Posted on 05-20-2025 03:26 AM
You can get alerts for elevation, but to see what was done, you need to enable Telemetry and then import those logs to a SIEM or an S3 bucket.