Join our Newsletter — 33% off our NHI Course

Why does AI agent monitoring leave delegated access unchecked?

 

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

TL;DR: AI agent monitoring adds visibility after access is granted, but WorkOS argues that cannot replace the identity controls agents need in production. Identity governance must still bound delegated access before behavioural detection can matter.

Editorial analysis by NHI Mgmt Group, based on content published by WorkOS: “Obsidian Security for AI Agent Security: Features, Pricing, and Alternatives”.

Key questions

Q: Why do AI agents increase risk in SaaS environments?

A: AI agents increase risk because they can operate through existing application permissions and continue using them as tasks change.

Q: How should security teams measure whether AI is helping rather than hiding risk?

A: Security teams should measure AI using outcome metrics that include access scope, session length, revocation speed, and auditability.

Q: What breaks when AI agent monitoring is treated as an authentication control?

A: Access governance breaks because the organisation learns what the agent did, but not whether the agent should have been able to enter in the first place.

Practitioner guidance

  • Define the agent authentication boundary Separate the systems that mint access from the systems that observe usage, and assign ownership for both.
  • Constrain delegated SaaS permissions Review OAuth grants, app scopes, and integration tokens for every AI agent and remove any access that exceeds the minimum task requirement.
  • Add lifecycle controls for machine identities Put AI agents into the same joiner-mover-leaver discipline used for other non-human identities so access is revoked when the workload, workflow, or owner changes.

Bottom line: AI agent monitoring improves SaaS visibility, but it does not replace authentication or authorisation controls that define what the agent can reach.

Glossary terms: Agent observability, Authentication boundary, Delegated Access, Identity Blast Radius

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
 

Authentication and observability are different control planes, and conflating them weakens both. Behavioural monitoring can improve visibility, but it does not issue trust, narrow scope, or govern access lifecycles. For AI agents, the control that matters first is whether the identity boundary was safe enough to permit access at all. Practitioners should treat runtime visibility as supplementary rather than foundational.

A few things that frame the scale:

A question worth separating out:

Q: What is the difference between agent observability and agent authorisation?

A: Agent observability shows what an identity did after access began, while authorisation decides whether that identity should have had access and how much. In production, authorisation is the preventive control and observability is the detective one. They solve related problems, but they are not interchangeable.

👉 Read our full editorial: AI agent monitoring still leaves SaaS identity governance unresolved


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.