Join our Newsletter — 33% off our NHI Course

Did RSAC 2026 show agentic AI needs tighter governance?

 

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

TL;DR: Agentic AI drew the spotlight at RSAC 2026 as security leaders confronted adoption racing ahead of governance, control and isolation capabilities, according to DTEX. Runtime limits, shutdown paths and network separation now matter as much as policy on paper.

Editorial analysis by NHI Mgmt Group, based on content published by DTEX: “Agentic AI: The Star of RSAC 2026”.

By the numbers:

  • 650 vendors had exhibits at RSAC 2026, with almost every one emphasizing agentic AI.
  • 63% of organisations cannot enforce purpose limitations on their AI agents.
  • 60% cannot terminate an agent that’s misbehaving.

Key questions

Q: Why does machine-speed agent behaviour change access governance?

A: Machine-speed behaviour collapses the time available for manual review, exception handling and human approval.

Q: What are the signs that shadow AI is becoming a governance problem rather than a productivity aid?

A: The clearest signs are widespread use outside IT visibility, repeated sharing of corporate data with GenAI tools, and no consistent approval path for new applications.

Q: What breaks when organisations deploy AI agents without lifecycle governance?

A: What breaks is not only access control but the assumption that deployment is a one-time event.

Practitioner guidance

  • Build an agent inventory with ownership and purpose Record every approved agent, its owner, intended task, connected data sources and permitted tools so governance starts with a real inventory rather than assumptions.
  • Enforce task-scoped access decisions Require policy checks at issuance time so agents receive only the minimum access needed for the specific workflow and cannot accumulate standing privilege.
  • Add termination and isolation controls for misbehaving agents Define the kill switch, isolation boundary and escalation path before deployment so a rogue agent can be contained without waiting for manual investigation.

Bottom line: Agentic AI is becoming a governance problem because organisations are granting software the ability to act, not just to assist.

Glossary terms: Agentic AI, Shadow AI, Purpose limitation, Agent Offboarding

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

Agentic AI has become an identity governance problem before it becomes a model governance problem. The article shows that the hard part is not adopting agents, but defining what they are allowed to do, what they can access and how they are retired. That makes registration, delegation and revocation central controls, not optional administration. Practitioners should treat agent identity as a first-class governance object.

A few things that frame the scale:

A question worth separating out:

Q: How should security teams respond when AI agents start touching OT data and workflows?

A: They should treat the agent as a governed identity with tightly bounded access, not as a generic automation layer. The practical test is whether the agent’s data access, decision scope and action rights can be limited, reviewed and revoked before it reaches production control paths.

👉 Read our full editorial: Agentic AI is outpacing governance at RSAC 2026


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.