Topic starter
18/08/2026 2:37 pm
TL;DR: Enterprise AI is repeating the cloud-native identity lesson in a new form: agents need controlled access, transaction context, and interoperability, not vertically integrated lock-in, according to Stacklok. The practical break point is not model quality but whether identity, tool access, and data egress can be governed across the full agent path.
Editorial analysis by NHI Mgmt Group, based on content published by Stacklok: “Navigating the AI Infrastructure Landscape: Lessons from Kubernetes Creators”.
Key questions
Q: How should security teams govern AI workflows that use multiple tools and data sources?
A: Security teams should govern AI workflows by placing explicit authorization at each decision point, not by relying on the permissions attached to the surrounding application or service account.
Q: Why do AI agents increase access risk compared with traditional application integrations?
A: AI agents can make runtime decisions, chain tool calls, and reach multiple systems faster than a human operator.
Q: What breaks when transaction context is lost in an agent workflow?
A: When transaction context is lost, downstream systems can no longer tell whether the request is still specific, valid, and constrained.
Practitioner guidance
- Define the agent identity boundary Map exactly where an agent is authenticated, where it is authorised, and where transaction context must persist across tool calls and downstream systems.
- Constrain tool access by workflow Limit each agent to the smallest practical tool set for the task, then separate read-only access from any action that can modify data or trigger side effects.
- Preserve data egress controls across the path Apply policy at the gateway, the agent runtime, and the destination system so that sensitive data cannot leave the approved workflow through a weaker hop.
Bottom line: AI infrastructure introduces a governance problem that looks like IAM, but behaves more like transaction control across non-human actors.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
18/08/2026 3:22 pm
AI infrastructure is now an identity architecture problem, not just an application design problem. The article shows that enterprises are no longer experimenting with isolated copilots. They are putting agents into real workflows that cross internal systems, gateways, and data stores. That means the question is no longer whether AI works, but whether the identity model can preserve control as the workflow moves.
A few things that frame the scale:
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.
- Kubernetes production adoption has surged from 66% in CNCF's 2023 survey to 82% in 2025.
A question worth separating out:
Q: What should teams do when AI infrastructure starts to look too vertically integrated?
A: Teams should check whether the stack is locking identity, policy, and data paths to one vendor’s model or gateway choices. If portability disappears, governance becomes harder to maintain during migrations, and the organisation loses leverage over access boundaries. The practical test is whether controls survive a platform swap without redesign.
👉 Read our full editorial: AI infrastructure needs identity controls that preserve interoperability