Subscribe to the Non-Human & AI Identity Journal

Notifications
Clear all

Agentic AI security assumptions are breaking. Are your controls ready?


(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 2827
Topic starter  

TL;DR: Agentic AI systems collapse the gap between intent and execution, operating across enterprise systems at machine speed while legacy security models still assume humans decide and machines execute, according to Cyera. That makes visibility into data, access, and behaviour the decisive control plane, not static policy.

NHIMG editorial — based on content published by Cyera: Rethinking Security in the Age of Agentic AI

By the numbers:

  • 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.

Questions worth separating out

Q: How should security teams govern AI agents that act on behalf of users?

A: Security teams should govern AI agents as non-human identities with separate runtime visibility, bounded data access, and explicit action limits.

Q: Why do AI agents complicate least privilege in enterprise environments?

A: AI agents complicate least privilege because their behaviour is shaped at runtime by context, data, and inferred goals rather than a fixed task script.

Q: How do organisations know if AI agent governance is actually working?

A: Governance is working when teams can see which data the agent accessed, which actions it attempted, and where policy stopped or altered the session.

Practitioner guidance

  • Map agent identity separately from user identity Record which actions are initiated by a person, which are executed by an agent, and which are relayed through a shared session so investigations can reconstruct the true runtime actor.
  • Bind agent permissions to data context Limit agent access by dataset sensitivity, workflow purpose, and downstream system impact instead of granting broad application-level access that assumes benign use.
  • Add runtime intervention points Use policy checks that can stop, downgrade, or require reapproval while the agent session is active, especially when the agent crosses boundaries into sensitive systems.

What's in the full article

Cyera's full article covers the operational detail this post intentionally leaves for the source:

  • How the vendor frames agentic AI as a third identity class in enterprise security
  • The specific data-governance and visibility gaps that emerge when agents act across systems
  • Cyera's runtime guardrail framing for autonomy, including how it thinks controls should intervene
  • The practical security assessment angle the article uses to translate agentic AI risk into programme decisions

👉 Read Cyera's analysis of security assumptions in the age of agentic AI →

Agentic AI security assumptions are breaking. Are your controls ready?

Explore further

View Full Forum →  |  NHI Foundation Course →



   
Quote
(@mr-nhi)
Member Moderator
Joined: 4 weeks ago
Posts: 1125
 

Agentic AI exposes a runtime governance gap that static IAM was never built to close. Traditional IAM assumes identity is provisioned, reviewed, and then observed through stable access patterns. Agentic systems do not behave that way because they can infer intent, choose tools, and act within a single session. The implication is that identity governance must stop treating access as a fixed state and start treating behaviour as the governed object.

A few things that frame the scale:

  • 98% of companies plan to deploy even more AI agents within the next 12 months, despite documented rogue behaviour in 80% of current deployments, according to AI Agents: The New Attack Surface report.
  • 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.

A question worth separating out:

Q: What should IAM teams do when agent behaviour outpaces review cycles?

A: IAM teams should shift from periodic certification to runtime controls that evaluate context while the agent is active. If access reviews happen after the task is finished, they cannot govern the action that already occurred. The programme needs live policy enforcement, alerting, and escalation paths built for machine-speed execution.

👉 Read our full editorial: Agentic AI breaks legacy security assumptions in the enterprise



   
ReplyQuote
Share: