Topic starter
16/12/2025 5:41 pm
TL;DR: Teleport’s summary of the OWASP Top 10 for Agentic Applications 2026 says AI agents now operate with real permissions across APIs, code, data, and multi-agent workflows, creating risks from goal hijack, tool misuse, privilege abuse, supply chain compromise, and rogue behaviour. Identity review cycles assume access is stable long enough to govern; autonomous action makes control at issuance and runtime the decisive boundary.
Editorial analysis by NHI Mgmt Group, based on content published by Teleport: “OWASP Top 10 for Agentic Applications 2026: Key Takeaways & How to Take Action”.
Key questions
Q: What breaks when AI agents inherit access from users and service accounts?
A: The main failure is that inherited access can be broader than the agent’s actual task, so privilege becomes easier to reuse than to govern.
Q: Should organisations prioritise runtime controls or agent productivity first?
A: Security teams should prioritise runtime controls before broad deployment because uncontrolled agent expansion creates compliance and breach risk faster than most programmes can remediate it.
Q: What are the signs that an agentic workflow is failing governance checks?
A: Look for repeated goal drift, unusual tool chains, unexpected data movement, reused credentials, and agent-to-agent messages that lack strong authentication or schema validation.
Practitioner guidance
- Define unique identities for each agent Assign each agent a separate identity with short-lived credentials, bounded scope, and no shared cached context across tasks.
- Scope every tool before execution Limit each tool to the minimum data, command set, and rate necessary, then require explicit confirmation for destructive operations.
- Inventory runtime dependencies and trust points Track every model, plugin, descriptor, and external service the agent can load, and block any component that cannot be verified or pinned.
Bottom line: Agentic AI changes identity security because the actor can choose, chain, and execute actions in production with real permissions.
What's in the full article
Teleport's full blog post covers the operational detail this post intentionally leaves for the source:
- Teleport’s mapping of each OWASP ASI category to concrete agent guardrails and deployment choices
- Examples of how Teleport applies short-lived credentials, approvals, and audit logging to agent workflows
- The article’s specific implementation guidance for securing AI agents, MCP servers, and human-in-the-loop access
- Related reading links on secretless engineering, MCP security, and AI agent authorisation
👉 Read Teleport’s summary of the OWASP Top 10 for Agentic Applications 2026 →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
07/10/2026 6:13 pm
Agentic systems collapse the assumption that identity is only a static wrapper around a user or workload. Once an AI agent can choose actions at runtime, identity becomes an active control surface rather than a provisioning record. That changes the governance problem from who owns the account to what the account is allowed to decide, do, and delegate. Practitioners need to treat agent identity as a runtime policy boundary, not just an object in the directory.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
- Breaches involving third parties rose to 48% of all breaches, a 60% increase on the previous year, according to Verizon's 2026 Data Breach Investigations Report.
A question worth separating out:
Q: How should security teams govern AI agents and NHIs differently?
A: Security teams should govern NHIs as predictable machine identities and AI agents as runtime actors that can alter behaviour after authentication. That means static entitlements, inventory, and rotation remain central for NHIs, while agents need behaviour monitoring, delegation tracing, and ownership controls that account for tool choice and execution timing.
👉 Read our full editorial: OWASP Top 10 for agentic applications 2026 and NHI risk