Notifications
Clear all
Topic starter
01/08/2026 10:49 pm
TL;DR: Agentic AI shifts security from monitoring outputs to governing actors, because systems that act across tools, data sources, and workflows can accumulate access, move laterally, and create new abuse paths, according to Anomali. The core issue is that identity, privilege, and accountability assumptions built for humans and service accounts do not hold once AI begins executing independently.
NHIMG editorial — based on content published by Anomali: From Copilots to Digital Employees: How Agentic AI Expands the Attack Surface
Questions worth separating out
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: Why do AI agents increase IAM and PAM risk?
A: AI agents increase IAM and PAM risk because they can execute actions quickly once privilege is available, which shortens the time available to detect misuse.
Q: What breaks when AI agents are treated like standard human users?
A: You lose visibility into effective permissions, expected behaviour, and real blast radius.
Practitioner guidance
- Assign a unique identity to every agent Register each agent as a governed non-human identity with explicit ownership, purpose, and lifecycle state.
- Constrain tool access by workflow boundary Limit each agent to the smallest tool set needed for its assigned process and prohibit cross-domain access unless separately approved.
- Review access growth as a lifecycle event Build recurring reviews for agent entitlements, especially when the agent is extended to new data sources or new operational workflows.
What's in the full article
Anomali's full article covers the operational detail this post intentionally leaves for the source:
- Specific examples of how agentic systems expand access across identity systems, data sources, ticketing, and cloud infrastructure.
- The webinar discussion and speaker framing behind the shift from copilots to digital employees.
- Practical examples of how restrictive-by-default access changes deployment sequencing for AI agents.
- The source article's own narrative on how security teams should rethink defensive logic when agents act inside workflows.
👉 Read Anomali's article on how agentic AI expands the enterprise attack surface →
Agentic AI digital employees: what IAM teams need to govern?
Explore further
01/08/2026 10:57 pm
Digital employees create an identity class that existing IAM programmes only partially cover. Traditional onboarding, least privilege, and offboarding logic can be applied to agents, but the assumption that identity is tied to a stable human operator breaks down. When the actor is software that acts independently across tools, identity governance must treat the agent itself as the accountable subject. Practitioners should stop mapping agents onto human lifecycle models by default.
A few things that frame the scale:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems (39%), inappropriately sharing sensitive data (31%), and revealing access credentials (23%), according to AI Agents: The New Attack Surface report.
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation, according to the same research.
A question worth separating out:
Q: When should organisations restrict AI agent access more aggressively?
A: Restrict access aggressively when an agent can reach production systems, sensitive data, or multiple connected services through broad delegated permissions. Those conditions increase the effective blast radius, so tighter scopes, stronger approvals, and faster review cycles become necessary before adoption scales.
👉 Read our full editorial: Agentic AI expands enterprise attack surface through digital employees
