TL;DR: Enterprise buyers are moving from broad AI agent demos to sharper questions about discovery, intent-based access, agent-native detection and governance, according to Aizome, because vendors built for cloud or endpoint security miss co-working agents and mandate drift. The shortlist now depends on whether a platform can see, explain and govern what agents actually do.
Editorial analysis by NHI Mgmt Group, based on content published by Aizome: “Your AI Security Vendor Cannot Answer These Questions - And That Is the Problem”.
Key questions
Q: How should security teams discover shadow AI agents in the enterprise?
A: Use endpoint artefacts first.
Q: What is the difference between agent permissions and agent intent?
A: Agent permissions are the actual technical rights granted to an agent, such as API scopes, service account roles, or tool-specific access.
A: AI agents can compress investigations and improve coverage, but they also shift decision-making into systems that may act quickly and with incomplete context.
Practitioner guidance
- Build a complete AI agent inventory Track agents created by business users, not just engineering teams, and include where they run, who owns them and which credentials they use.
- Separate approved agents from shadow agents Require a governance record for every agent that touches production systems, including purpose, owner, data scope and retirement date.
- Review runtime behaviour against declared intent Compare what each agent is permitted to do with the systems, records and workflows it actually touches during execution.
Bottom line: AI agent security now turns on whether organisations can find every agent, including those built outside IT and connected through human credentials.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Discovery is now the first governance test for AI agents. Enterprises are past the stage where the main question is whether agents exist at all. The harder problem is whether the security team can see co-working agents that were created outside central IT and still operate under human credentials. That is not just an inventory issue. It is a control-plane failure that leaves governance blind to shadow deployments and unmanaged access paths. Practitioners should treat undiscovered agent populations as a standing governance gap, not an edge case.
A few things that frame the scale:
- Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.
A question worth separating out:
Q: When should security teams prioritise agent-native detection over endpoint controls?
A: Security teams should prioritise agent-native detection when the main risk comes from the agent’s tool calls, workflow chaining, delegated credentials, or prompt-driven actions that may look normal on the endpoint. Endpoint controls still matter for host compromise, but they do not show intent, tool selection, or cross-system sequences. Agent-native telemetry from the agent runtime, orchestration layer, and audit logs is the control surface for spotting misuse.
👉 Read our full editorial: AI agent vendor evaluations are shifting to discovery, intent and governance