Join our Newsletter — 33% off our NHI Course

Where does platform control stop and runtime policy begin for Agent Guard?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: Governance breaks most often at the boundary between Kubernetes AI tools, according to Jozu. Packaging, policy and audit trails need to cover the handoff points where provenance, promotion and runtime control meet.

Editorial analysis by NHI Mgmt Group, based on content published by Jozu: “Who Offers a Leading Kubernetes AI Solution for Self-Hosted Enterprise AI?”.

Key questions

Q: Why do runtime policy gateways still leave AI agents exposed?

A: Because they only see a slice of the agent’s behaviour.

Q: How should teams govern AI supply chains for self-hosted deployments?

A: Use package identity, provenance and approval status as the control points for promotion.

Q: What breaks when AI model packaging is not the governed unit?

A: Teams lose the ability to prove which data, code, prompts and configuration actually produced the deployed model.

Practitioner guidance

  • Standardise the AI platform layer Choose one Kubernetes AI foundation for each environment, then keep serving, training and pipelines aligned to that operating model instead of mixing ad hoc deployment paths.
  • Make the packaged artefact the approval unit Require every model, dataset, prompt and configuration bundle to move as one versioned object so approvals, rollback and provenance all refer to the same digest.
  • Separate promotion from rebuilds Promote AI artefacts by digest from development to staging to production and prohibit repackaging steps that would break the evidence chain.

Bottom line: Kubernetes AI governance fails most often at the boundary between tools, not inside any single platform.

Glossary terms: ModelKit, Agent Guard, AI Supply Chain Security, Runtime Policies

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Artifact governance is now the primary control surface for self-hosted AI. In Kubernetes-based AI stacks, the real security unit is no longer the notebook, pipeline or endpoint on its own. It is the packaged artefact that survives movement across all three. That is why provenance, versioning and promotion controls matter more than any single platform choice. Practitioners should stop treating model files as build outputs and start treating them as governed identities in motion.

A few things that frame the scale:

A question worth separating out:

Q: What is the difference between platform control and runtime control for AI agents?

A: Platform control decides where the AI lifecycle runs and how infrastructure is operated. Runtime control decides what an agent may do after it starts, including which tools, data and destinations it can reach. Both are necessary, but they answer different governance questions and fail in different ways.

👉 Read our full editorial: Self-hosted Kubernetes AI needs packaging, policy and audit trails


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.