Notifications
Clear all
Topic starter
09/06/2026 11:13 pm
TL;DR: AI agent discovery remains the most common gap security teams report as organisations build low-code and no-code agents across AWS Bedrock, Azure AI Foundry, Copilot Studio, Vertex AI, and other environments, according to Lasso Security. Without a continuously updated inventory, security teams cannot govern model choice, tool access, or runtime behaviour across separate platforms.
NHIMG editorial — what this means for AI and NHI governance
By the numbers:
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption.
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job.
Questions worth separating out
Q: How should security teams inventory AI agents across multiple cloud platforms?
A: Security teams should treat every cloud platform, low-code builder, repository, and CI/CD pipeline as a discovery source.
Q: Why does AI-BOM visibility matter for agent governance?
A: AI-BOM visibility matters because an agent’s behaviour is defined by its components, not by a single account record.
Q: What breaks when AI agent discovery is incomplete?
A: When discovery is incomplete, security teams cannot reliably assign ownership, scope permissions, or detect cross-environment drift.
Practitioner guidance
- Build a cross-platform agent inventory first Map every low-code, no-code, repository-built, and cloud-native agent across managed AI platforms and cloud accounts.
- Require an AI-BOM for every discovered agent Track the foundation model version, system prompt, connected tools, MCP servers, retrieval sources, guardrails, and dependency set.
- Review delegated permissions in multi-agent graphs Trace sub-agents, APIs, and external services to identify where permissions propagate beyond the parent agent.
What's in the full announcement
Lasso Security's full analysis covers the operational detail this post intentionally leaves for the source:
- Platform-by-platform discovery coverage across AWS Bedrock, Azure AI Foundry, Copilot Studio, Vertex AI, Salesforce Agentforce, and other managed builders.
- The AI-BOM fields and dependency graph outputs used to represent each discovered agent in operational detail.
- How automated red teaming is tied to the discovered posture and how findings feed into runtime policy updates.
- Examples of inline guardrail updates and re-testing after posture findings are generated.
👉 Read Lasso Security's analysis of cross-cloud AI agent discovery and AI-BOM governance →
AI agent discovery across clouds: what IAM teams are missing?
Explore further
10/06/2026 1:30 am
Cross-cloud AI agent discovery is now an identity control, not just an inventory task. Once agents can be created in Bedrock, Azure AI Foundry, Copilot Studio, Vertex AI, or code repositories, the old assumption that security can govern from a single console breaks down. The estate becomes distributed before it becomes visible, which means governance starts from absence rather than control. Practitioners should treat discovery as the first identity boundary for agentic systems.
A few things that frame the scale:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
- A separate finding from the same survey shows that only 44% of organisations have implemented any policies to manage their AI agents, even though 92% agree that governing them is critical to enterprise security.
A question worth separating out:
Q: How should organisations govern model selection for AI agents?
A: Organisations should treat model selection as a governance decision, not a local implementation detail. Approved models, restricted models, and external-facing models should be defined centrally so business teams cannot expand risk simply by choosing a different foundation model.
👉 Read our full editorial: Cross-cloud AI agent discovery is becoming an IAM control point
