Topic starter
01/08/2026 8:53 pm
TL;DR: AI agents are moving into enterprise workflows with API access, delegated permissions, and tool use, creating risks that traditional controls were not built to govern, according to Salt Security and cited industry research. The security problem is no longer model safety alone; it is identity, privilege, and governance for systems that can act.
Editorial analysis by NHI Mgmt Group, based on content published by Salt: “Top Security Risks of AI Agents”.
By the numbers:
- Gartner projects that 40% of enterprise applications will include task-specific AI agents by the end of 2026, up from less than 5% just a few years earlier.
- A Dark Reading survey found that nearly half of cybersecurity professionals view agentic AI as the leading attack vector heading into 2026.
Key questions
Q: What breaks when AI agents and humans share the same access model?
A: When AI agents and humans share the same access model, organisations lose clean attribution, stronger approval boundaries, and reliable review evidence.
Q: Why do over-privileged AI agents create higher business risk than ordinary users?
A: Over-privileged agents can execute many more actions than the task actually requires, so one bad decision can cascade into wrong approvals, refunds, data movement, or API calls.
Q: What are the signs that AI governance is failing in the enterprise?
A: Common warning signs include rapid growth in AI use without matching policy coverage, sensitive files being copied into personal accounts, and a large share of AI apps carrying high or critical risk.
Practitioner guidance
- Define agent identities explicitly Classify every AI agent, connector, and delegated integration as a governed non-human identity with a named owner and business purpose.
- Scope agent permissions to one task Remove broad inherited access and bind each agent to the smallest feasible tool set, data set, and workflow path.
- Inventory every AI-connected integration Build a complete register of AI-enabled SaaS features, plugins, API links, and MCP-style connectors before authorising production use.
Bottom line: AI agents create an identity governance problem because they can act through delegated permissions, tool use, and cross-system workflows, not just generate text.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
01/08/2026 9:02 pm
AI agent governance is now an identity problem, not just a model-safety problem. The central change is that the system can act through delegated access, tool use, and workflow execution. That places agent behaviour in the same governance family as other non-human identities, but with far less predictable runtime intent. Practitioners should stop treating agent security as an add-on to application security and start governing it as a distinct identity class.
A few things that frame the scale:
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should security teams handle AI agents that need to log into SaaS applications?
A: Use delegated authorization rather than cloned human sessions. Give the agent a separate identity grant with explicit scopes, short-lived tokens, and revocation. That preserves auditability and lets IAM and PAM teams control what the agent can do without inheriting the user’s full browser session or password material.
👉 Read our full editorial: AI agent security risks are outpacing legacy IAM controls