Topic starter
22/07/2026 4:36 pm
TL;DR: AI agents now behave like trusted insiders with real credentials, machine-speed execution, and volatile tool use, while the old human-insider assumptions no longer hold, according to Pillar Security and its SAIL 2.0 framework. The governing premise that identity, pace, consequence, and behavior stay human-shaped collapses once the actor is an autonomous system with no stable review window.
Editorial analysis by NHI Mgmt Group, based on content published by Pillar Security: “The New Insider: Rethinking Insider Risk for the Agentic Workforce”.
By the numbers:
- Roughly half of employees use unsanctioned AI tools while only 37% of organisations have policies to detect or manage them.
Key questions
Q: What breaks when AI agent harness controls are not governed like production security controls?
A: The agent can still stay within its technical permissions and yet behave unsafely because prompts, tool routing, retrieval, and escalation logic are unconstrained.
Q: Why do autonomous AI agents increase insider risk even when access is technically authorized?
A: Autonomous agents increase insider risk because authorization alone does not explain purpose.
Q: What are the signs that an autonomous agent is operating outside its intended boundary?
A: Look for agents running with approval prompts disabled, outbound connections to unfamiliar destinations, and access to production-classified systems that the workflow does not require.
Practitioner guidance
- Build a complete agent roster Inventory every AI agent across endpoints, pipelines, repositories, SaaS platforms, and no-code builders, and assign each one an owner before expanding access.
- Assign unique identities with human supervision Replace shared and personal accounts with unique agent identities linked to a responsible human supervisor so access and accountability are traceable.
- Classify autonomy and authorise actions separately Define which agents may take which actions against which systems, and place action-level authorisation in front of high-risk tools and data paths.
Bottom line: AI agents behave like insiders with legitimate access, but their machine speed and mutable tool use make human-centric IAM assumptions unreliable.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
22/07/2026 4:41 pm
Human insider risk assumptions collapse when the actor is an AI agent: one identity per person, human-paced action, personal consequences, and stable behaviour are all premises built for people. Once the actor is autonomous, those premises stop describing the identity subject at all. The implication is that insider governance has to be rebuilt around non-human identity properties, not extended from human workforce assumptions.
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.
- 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 question 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. The control set should include inventory, task-bound credentials, audit trails, and revocation paths. If an agent can call tools or touch production systems, it belongs in the same governance model as service accounts and other machine identities.
👉 Read our full editorial: AI agents as insiders expose the limits of human IAM controls