Join our Newsletter — 33% off our NHI Course

Why do broad inherited permissions make agentic AI risk scale faster?

 

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

TL;DR: Broader inherited permissions make agentic AI risk scale faster as software can take actions, use credentials and chain tasks without a human closing each step, ClawSecure says. Agent identity needs runtime checks and tighter delegated authority before sensitive access is granted.

Editorial analysis by NHI Mgmt Group, based on content published by ClawSecure: “Agentic AI Security in 2026: The Year Agents Go Mainstream”.

By the numbers:

  • Gartner predicts that 40% of enterprise applications will embed task-specific AI agents by the end of 2026, up from less than 5% in 2025.
  • Palo Alto Networks found that machine identities already outnumber human employees by an 82-to-1 ratio in the enterprise.

Key questions

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: How should security teams evaluate AI agent trust before production use?

A: Security teams should evaluate AI agent trust by combining identity posture, intended access, delegation paths, and governance metadata in one approval decision.

Q: What breaks when AI agents are given broad inherited permissions?

A: Broad inherited permissions break the assumption that access is tied to a narrow business need.

Practitioner guidance

  • Define an agent identity lifecycle Register every agent with an owner, purpose, delegated authority and retirement trigger so the identity record reflects how the agent is actually used.
  • Enforce least agency by default Limit each agent to the minimum decision scope, tool scope and action scope needed for its task, and require explicit approval for higher-risk actions.
  • Add runtime integrity checks Verify that an agent is running unmodified code before it is allowed to access email, files, shells or sensitive APIs, then re-check after updates.

Bottom line: Agentic AI changes the identity problem because software can now take actions, use credentials and chain tasks without a human closing each step.

Glossary terms: Agent Identity, Least Agency, Runtime Verification, Sleeper Agent Risk

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: 20715
 

Agentic AI security is now an identity governance problem, not just an AI safety problem. The article shows that the real risk emerges when agents inherit permissions, act on behalf of users and persist across workflows without a clear lifecycle. That makes identity, delegation and offboarding central controls rather than administrative details. Practitioners should treat agent identity as a first-class governance domain.

A few things that frame the scale:

A question worth separating out:

Q: Should organisations treat AI coding agents as part of IAM and PAM governance?

A: Yes, when those agents can act on code, data, or tools in ways that affect production risk. Their permissions should be scoped, reviewed, and audited like other privileged systems, especially when they interact with sensitive routes, secrets, or regulated data. The governance question is who can let the agent act, and under what policy.

👉 Read our full editorial: Agentic AI security in 2026: identity and control gaps widen


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.