Skip to main content

Product Office Hours APAC - Jamf @ Jamf Perspectives on AI Governance - Nov 20th *Q&A in thread*

  • Oct 30, 2026 3:45 PM UTC
  • 2 replies
  • 144 views

LysetteB
Forum|alt.badge.img+20

Hi Nation,

Product Office Hours APAC Edition - Jamf @ Jamf Perspectives on AI Governance 

Session details: Friday, 20th November - 6 am AWST / 7 am JST / 9 am AEDT
Speakers: CCO, Sam Johnson, and Emily Kausalik (​@emily) 
Register here: https://jamf.it/ProductOfficeHoursAPAC

Join us! We’ll be talking all things AI in the Jamf world including how we manage and govern our internal AI tools.

This is a one off event and will not be recorded. The Q&A transcript will be shared after the event.


🧵 Got a question? Drop it in the comments below ahead of time if you want it on our radar, though you don't have to. We'll be taking questions live on the call! Anything we don't get to, we'll follow up right here.

See you Friday 20th!

2 replies

BookMac
Forum|alt.badge.img+16
  • Jamf Heroes
  • Nov 2, 2026 8:45 AM UTC

If i get it right Jamf Protects collects the data from macOS devices for AI Governance. How will it works in the future for iOS and Browser?


LysetteB
Forum|alt.badge.img+20
  • Author
  • Community Manager
  • Nov 20, 2026 6:21 PM UTC

This week's APAC Product Office Hours covered Jamf at Jamf: Perspectives on AI Governance, with Sam Johnson (Chief Customer Officer) and Emily Kausalik (Manager, Client Platform Engineering). Here's every question asked during the session, pulled from both the live Q&A and the chat. 

Session overview 

Jamf frames its AI work across three areas: AI governance, which gives visibility and control over which AI tools people use and whether that use delivers value; autonomous endpoint management, which is about getting the most from Apple devices, whether they run local or cloud models; and an agentic development platform for admins and security teams moving toward GitOps, APIs and MCP-driven workflows. This session focused on the AI governance piece. 

Jamf shared how it manages AI tools across its own fleet, which it treats as "Customer 0”. Most internal AI use is Claude Desktop and Claude Code. Visibility now extends to the individual device and the commands those tools run, with Protect supplying the telemetry behind it. The clearest theme was a paved road: when the sanctioned way to use a tool is one click, people are less likely to go around it. Examples included providing a dedicated Self Service+ category with one click policies that handle dependencies and sign-in in one step, and using blueprint activation conditions that let teams test a change on a small group before a full rollout. Rollback and version diffs were highlighted as useful for iterating on policies. 

Other themes were data and tooling. Software installed outside management, such as through developer package managers, was identified as a harder problem, and the answer was framed as much about trust and working with security teams as about technology. Local AI management came up as a growing area, with Jamf investigating how customers might deploy and manage local models and asking for feedback. 

What about local AI management? A lot of organisations are moving to local inference instead of cloud, so what's the plan? 

There isn't a plan we can share yet, but Jamf is actively investigating it. If local AI is important to your organisation, feedback is the most useful thing you can give. Submit feature requests and talk to your account team. Jamf team members in Australia are also keen to hear about legitimate local use cases, so get in touch. 

Does AI governance feed into Jamf Protect to help detect bad behaviour as new AI-driven threats emerge, or does it only give analytics you might not have accounted for? 

This wasn't covered in the session, so we'd rather not guess. Please share more detail on the threats or use cases you're thinking about so this can be looked into. 

Has there been much Jamf at Jamf road testing of the Blueprints app installation (ALME) and patching demo shown at JNUC? 

Not covered in the session. Please share what you'd like to test and what you'd want to see from it, so the question can be looked into and answered in the thread. 

How do you handle package management when developers pull packages from many places for coding work? 

The Jamf IT team uses a combination of patch title policies, App Installers, and volume purchase deployments to update apps, with a bias towards policies that can quickly report the version update back to Jamf Pro with an inventory update. Scale is considered when it comes to what deployment mechanism is used for an app. 

Tools installed outside management, such as through Homebrew and NPM, are the harder gap. Jamf IT collaborates regularly with Jamf Information Security teams to understand new and emerging tools in the environment, perform risk assessments, and plan patching cycles.