Topic starter
22/08/2026 12:00 pm
TL;DR: Google’s inaugural Gemini Startup Forum grouped 33 startups across six focus areas, with AI agent security standing on its own as a full segment rather than a subset of application security, according to Onyx. That separation reinforces that autonomous agents need dedicated discovery, posture, and runtime governance, not retrofitted controls from legacy IAM or appsec.
Editorial analysis by NHI Mgmt Group, based on content published by Onyx: “Onyx joins Google's Gemini Startup Forum for AI agent security”.
Key questions
Q: What breaks when autonomous agents are governed like human users?
A: Session-based IAM breaks first, because autonomous agents can make and execute decisions between review points.
Q: Why do autonomous agents complicate data security controls?
A: Autonomous agents complicate data security because they can combine discovery, retrieval, and action in one workflow.
Q: What are the signs that agent security controls are lagging?
A: Common signs include agents appearing in production without clear ownership, unclear visibility into tool calls, and no reliable way to reconstruct what a session changed.
Practitioner guidance
- Inventory autonomous agent surfaces Identify where agents are already embedded in AI platforms, workflow tools, and developer environments, then classify each by ownership, tool access, and runtime authority.
- Separate agent governance from appsec Map which agent risks are about runtime behaviour, tool chaining, and scope drift rather than code flaws, then assign those risks to an agent-specific control model.
- Define approval boundaries for tool use Require explicit policy for which tools an agent may call, which actions need human review, and which sessions must be constrained to read-only behaviour.
Bottom line: Google’s forum grouping shows that AI agent security is being treated as a distinct discipline, not a minor extension of application security.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
22/08/2026 12:02 pm
AI agent security has crossed the threshold from feature concern to control discipline. Google’s decision to group AI agent security as a full segment, rather than bury it inside application security or identity, reflects a structural shift in how the market now interprets autonomous systems. That matters because the governance problem is no longer only whether an agent can authenticate, but whether it can act, select tools, and expand scope at runtime. Practitioners should read this as a category-definition moment, not a branding exercise.
A few things that frame the scale:
- Gartner predicts that more than 50% of successful cyberattacks against AI agents through 2029 will exploit access control weaknesses.
A question worth separating out:
Q: How should enterprises compare agent security to identity or application security?
A: Agent security overlaps with both, but it is not the same thing. Identity controls answer who or what may authenticate, while application security traditionally protects the software surface. Autonomous agents need both, plus runtime governance over tool use and scope drift, which is why the category is emerging separately.
👉 Read our full editorial: Google’s Gemini forum signals AI agent security is a distinct discipline