Hello everyone,
I’m curious how other organizations handle Jamf ownership, administrator access, and peer reviews, particularly for the engineers responsible for managing the environment day to day.
I’m currently our only certified Jamf Engineer. About 10 months ago, ownership of Jamf moved to our another team. Since then, certain tasks involving our primary Apple Business account have required me to go through that department, even when those tasks directly support my responsibilities.
For example, it took nearly 30 days to renew the push certificate in our development environment. Thankfully, this wasn’t production, but it raised concerns for me about how we would handle something similar in Prod.
We have separate Apple accounts for our primary administrative functions, production, and development. The primary account is considered a “break glass” account, and my request for access was declined because of its elevated permissions, including the ability to release devices.
I understand the need to protect privileged accounts. What I’m trying to work through is how to balance those controls with the access engineers need to maintain the environment and respond to issues. I’d be interested in hearing whether other teams use delegated permissions, privileged access tools, or a documented emergency access process.
I’m also curious how you handle peer reviews. Our Jamf production changes are reviewed by colleagues who are knowledgeable in their own areas but don’t have much Jamf experience. I value their input, although sometimes the review becomes more about explaining Jamf functionality than evaluating the risk of the change.
A recent example was a request to deploy one app to one device for an employee’s accessibility needs. The reviewer questioned why I hadn’t created a Smart Group. I explained that I had scoped the app directly to the device by serial number and used an “ADA” category to organize it. We already have a large number of Smart Groups, so I’m trying to avoid adding unnecessary ones while identifying older groups we can retire. That led to a longer discussion than I expected for a small deployment.
For context, I hold Jamf 100, 170, 200, and 300 certifications, and I’m working toward 400 as time permits. I certainly don’t believe certifications are required to be a capable Jamf administrator. My concern is making sure responsibility, access, and technical review are aligned so the people supporting the platform can do their jobs effectively.
I enjoy the work and respect my colleagues. At times, though, I feel accountable for the environment while depending on others to complete some of the tasks needed to support it.
How does your organization approach this?
Who owns Jamf, and what access do your day-to-day engineers have? How do you manage privileged Apple accounts and certificate renewals? And do Jamf changes require review by someone with Jamf experience, or do you use a broader infrastructure review process?
I’d appreciate hearing what has worked well for other teams, especially in larger or healthcare environments. I’m hoping to bring back some practical ideas for clearer responsibilities and a smoother support process.
I look forward to hear from others on how you use Jamf based on certs, knowledge of the platform, etc.
Thanks, everyone!
