Topic starter
23/03/2026 2:17 pm
TL;DR: Agentic AI systems follow intent, move at machine speed, and can shift sensitive data across environments in milliseconds, creating control gaps where visibility, enforcement, and attribution are missing, according to Cyera. Legacy network and identity silos were built for deterministic systems, but agentic workflows require data-layer governance before autonomous action becomes operational risk.
Editorial analysis by NHI Mgmt Group, based on content published by Cyera: “The Toxic Combinations of Agentic AI Risk”.
Key questions
Q: What breaks when agentic AI is governed like a normal application account?
A: Security controls break down because agentic systems do not behave like fixed-function applications.
Q: Why do AI systems create more data exposure risk than human users with the same access?
A: AI systems can process and combine information at machine speed without the judgment humans use to ignore irrelevant or sensitive material.
Q: What signs show that legacy identity controls are failing with AI agents?
A: The clearest signs are poor traceability, unclear ownership of actions, and data leaving its original boundary without a matching approval or enforcement record.
Practitioner guidance
- Map agent workflows to control assumptions Identify where current identity, network, and endpoint controls assume deterministic behaviour, then document the exact points where an agent can act faster than review or enforcement.
- Shift policy enforcement to the data layer Define controls that follow sensitive data as it is copied, summarised, shared, or written into new workspaces, because the risky event is often the movement itself.
- Separate external communication from write authority Review which agents can both reach outside sources and commit changes internally, then constrain any workflow that combines external ingestion with autonomous write actions.
Bottom line: Agentic AI exposes a mismatch between static identity models and actors that can make runtime decisions across tools, data, and environments.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
08/10/2026 5:29 pm
Legacy identity controls were designed for deterministic actors, and that assumption fails when the actor is agentic. Cyera’s analysis makes the central point plainly: access models built around predictable request-response behaviour do not hold when an agent selects actions at runtime. The governance implication is not simply more control, but a different control premise. Practitioners should stop treating agent identity as a special case of human or workload access.
A few things that frame the scale:
- 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to the 2026 Infrastructure Identity Survey.
- 54% of organisations are actively deploying AI agents across workflows, yet only 21% report a mature governance model for agentic AI.
A question worth separating out:
Q: How should security teams govern autonomous systems that create their own access?
A: Security teams should govern autonomous access as a runtime identity problem, not a ticketing problem. The key is to inventory machine and agent identities at creation, assign ownership, define expiry conditions, and classify access events as they happen. If access exists only inside execution, governance must operate inside execution too.
👉 Read our full editorial: Agentic AI risk exposes the limits of legacy identity controls