Topic starter
11/06/2026 11:57 pm
TL;DR: As Microsoft reports more than 230,000 organisations, including 90% of the Fortune 500, using Copilot Studio to build custom agents, Zenity’s analysis shows why unauthenticated inputs, tool chaining, and indirect prompt injection can turn workflow automation into data exposure risk. Inline, behavior-driven controls are becoming the governance baseline for AI agents.
Editorial analysis by NHI Mgmt Group, based on content published by Zenity: “Preventing AI Agents from Going Rogue: Zenity Collaborates with Microsoft Copilot Studio to Deliver Inline Protection Against Malicious Behavior”.
Key questions
Q: What breaks when privileged AI agents can read untrusted input directly?
A: Prompt injection risk rises because the agent may treat user content as instruction instead of context.
Q: Why do autonomous agents increase the risk of data leakage from business apps?
A: Because the agent can combine valid tool access with malicious or misleading instructions in the same runtime session.
Q: How do security teams know if agent governance is actually working?
A: It is working only if the team can answer three questions quickly for any agent: what it can reach, what it did recently, and whether that behaviour matches intent.
Practitioner guidance
- Constrain public trigger paths Remove unauthenticated or anonymous entry points for agents that can reach sensitive tools, and require verified identity for every workflow that can initiate external actions.
- Enforce tool-level allowlists Limit each agent to the smallest set of tools, destinations, and data scopes required for its task, with separate controls for read and write operations.
- Inspect tool invocation in real time Insert policy checks at the moment an agent requests a tool action, so risky combinations of input provenance, intent, and destination can be blocked before execution.
Bottom line: AI agents change identity governance because the dangerous event is often not authentication failure but authorised behaviour triggered by untrusted input.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 day ago by NHI Mgmt Group
12/06/2026 8:52 am
Inline agent protection is now a governance requirement, not a nice-to-have control layer. Agents that can accept untrusted input and invoke business tools create a runtime decision problem that post hoc review cannot reliably contain. The field should stop treating agent security as a logging and alerting exercise. The practitioner implication is that authorisation must be enforced at the point of tool use.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: Who should own access decisions for AI agent secrets?
A: Access decisions should be owned by the identity and security function, with approval tied to the task and the actor's scope, not left implicit inside the developer workflow. That gives teams a way to preserve oversight while still supporting automation. If approval is unclear, the secret will drift into places that governance cannot reliably inspect.
👉 Read our full editorial: AI agent governance needs inline protection against rogue behavior
This post was modified 1 day ago by NHI Mgmt Group