Topic starter
14/07/2026 4:24 pm
TL;DR: Login is not enough to govern AI agents once they start choosing tools, calling APIs, and triggering workflows, according to Cato Networks. Runtime behaviour needs action-level policy, or delegated access stays broad and hard to govern.
Editorial analysis by NHI Mgmt Group, based on content published by Cato Networks: “Zero Trust for AI Agents Starts After Login”.
Key questions
Q: Why do agent systems become harder to control as autonomy increases?
A: As autonomy grows, agents create more branching paths, delegate work, and trigger delayed side effects across tools and other agents.
Q: How can security teams know if agent skill controls are actually working?
A: Look for evidence that skills are inventoried, risk rated, scanned before execution, and tied to a policy manifest or approval record.
Q: What breaks when AI agents are governed only with login-based IAM?
A: Login-based IAM breaks because it stops at authentication and never evaluates the thousands of actions an autonomous agent may take after sign-in.
Practitioner guidance
- Define agent autonomy classes Separate observing, advising, acting with approval, and acting autonomously, then attach different approval, logging, and rollback rules to each class.
- Move policy enforcement into the runtime path Validate prompts, retrieved context, tool-call parameters, and target systems before execution, not after the action has already started.
- Inventory all active agent workflows List where agents run, what data they touch, which tools they can invoke, and who owns each workflow so hidden exposure does not sit outside governance.
Bottom line: Login is no longer a sufficient trust boundary for AI agents because the risky decision occurs after authentication, when the agent selects tools and acts on context.
Glossary terms: Agent Autonomy, Runtime Authorisation, Identity Blast Radius, Machine Identity
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 3 days ago by NHI Mgmt Group
14/07/2026 4:32 pm
Login-based Zero Trust is structurally incomplete for AI agents: the security decision does not happen at authentication, it happens when the agent selects a tool and acts on live context. That means the traditional trust boundary is too early in the flow to govern risk. Practitioners need to treat the post-login action as the real control point.
A few things that frame the scale:
- 90% of IT leaders say properly managing NHIs is essential for a successful zero-trust implementation, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What is the difference between access scope and runtime control for AI agents?
A: Access scope defines what an agent is allowed to reach in principle. Runtime control decides whether a particular action should proceed in the current context, with the current instruction, against the current data and system. For AI agents, both matter, but runtime control is what keeps legitimate access from becoming unsafe action.
👉 Read our full editorial: Runtime control, not login, defines AI agent zero trust
This post was modified 3 days ago by NHI Mgmt Group