Join our Newsletter — 33% off our NHI Course

Are traditional IAM controls enough for the agentic workforce?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Broad adoption of autonomous agents is already putting the Agentic Workforce into production, with 72% of organizations using them and 40% running multiple agents, according to Pillar Security. Static IAM cannot safely govern this shift because review after execution arrives too late for machine-speed decisions.

Editorial analysis by NHI Mgmt Group, based on content published by Pillar Security: “Securing the Agentic Workforce”.

By the numbers:

  • 40% are running multiple agents in production workflows.

Key questions

Q: Why do AI agents need action-level authorisation instead of resource-level access?

A: Resource-level access tells you what an agent can reach, but not whether its runtime actions match its authorised purpose.

Q: How should security teams discover shadow AI agents in the enterprise?

A: Use endpoint artefacts first.

Q: What breaks when autonomous agents are governed like human users?

A: Session-based IAM breaks first, because autonomous agents can make and execute decisions between review points.

Practitioner guidance

  • Inventory every production agent Map where agents exist, who created them, what systems they can reach, and whether they are sanctioned or shadow deployments.
  • Separate authentication from action approval Treat login or token issuance as only the start of governance, then require runtime checks before each meaningful tool call or downstream write.
  • Attach ownership to every agent identity Record a human owner, a business purpose, and an expiry path so agent identities can be reviewed, revoked, and retired without ambiguity.

Bottom line: Autonomous agents invalidate the assumption that identity activity can be reviewed after execution, because the work may be finished before a human sees it.

Glossary terms: Agentic Workforce, Action Control, Shadow Agent, Scope drift

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Autonomous identity governance is collapsing because access review assumes access remains stable long enough to be reviewed. That assumption was designed for human-paced and service-account-paced control loops. It fails when an autonomous agent can acquire context, combine tools, and complete harmful action chains within a single session. The implication is that existing review cadences no longer describe the actual risk state, so practitioners must rethink what governance is trying to observe.

A few things that frame the scale:

  • Independent surveys put adoption above 72% of organizations either using or testing AI agents, with 40% running multiple agents in production workflows, 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.

A question worth separating out:

Q: What should organisations do before scaling agentic workflows?

A: Before scaling agentic workflows, organisations should define who owns each agent, what it is allowed to do, and where intervention will happen if behaviour drifts. They should also test whether tools can be chained into unsafe outcomes even when individual permissions look reasonable. That is the real governance test for autonomous systems.

👉 Read our full editorial: Securing the agentic workforce: why existing IAM controls fail



   
ReplyQuote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Action control is now the decisive governance layer for autonomous agents. The article is right to move the focus away from static access policy. Once an actor can chain tools, change direction, and complete work at machine speed, session-level IAM no longer defines the real security boundary. Practitioners should treat action authorization as the primary control plane for agentic systems.

A few things that frame the scale:

A question worth separating out:

Q: What should organisations do when an AI agent starts chaining tools beyond its intended task?

A: Contain the agent before the workflow completes, because chained tool use can turn an ordinary task into data movement, unwanted writes, or business process manipulation. The right response is to stop the execution path, preserve the trace, and review the permission scope that allowed the chain to form.

👉 Read our full editorial: Agentic workforce governance needs runtime action control


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.