Join our Newsletter — 33% off our NHI Course

Did Access Controls for NHIs and AI agents outgrow RBAC?

 

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

TL;DR: Authentication and authorization now have to span humans, devices, APIs, applications, and AI agents, Curity argues, because static role assignment no longer fits requests where context, token scope, and action path decide safety. Access control has to absorb runtime context or heterogeneous identities will keep forcing exceptions across systems.

Editorial analysis by NHI Mgmt Group, based on content published by Curity: “What is Access Control?”.

Key questions

Q: Why do NHIs make access control harder to govern than human users?

A: NHIs are numerous, highly dynamic, and often tied to automation, which means access changes faster than manual review cycles.

Q: What are the signs that role-based access control is becoming too hard to manage?

A: Common signs include role sprawl, frequent role edits, overallocated permissions, and growing visibility gaps across the identity environment.

Q: How should teams design an authorization model for applications that mix human users, APIs, and AI agents?

A: Start by mapping what is protected, who can act, and which conditions change access.

Practitioner guidance

  • Map every requesting party to an identity type Classify users, service accounts, APIs, applications, and AI agents separately so access policy design reflects how each actor actually requests and uses authority.
  • Separate authentication from authorization reviews Check that proof of identity, token issuance, and permission enforcement are independently tested, because a valid token does not guarantee safe access.
  • Move high-risk decisions into policy evaluation Use attribute and context signals such as device state, location, and request path for access decisions where RBAC alone cannot express the risk.

Bottom line: Access control is shifting from a login problem to a governance problem that has to cover humans, NHIs, APIs, applications, and AI agents together.

Glossary terms: Access Controls, Authorization, Attribute-Based Access Control, Policy-Based Access Control

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
 

Access control is becoming an identity governance problem, not just an authentication problem. The article shows that modern systems now have to arbitrate access for users, APIs, applications, and AI agents within one decision model. That broadening matters because the risk is no longer limited to login abuse. It is the mismatch between static entitlement models and runtime decision-making across heterogeneous identities. Practitioners should treat access control as governance over requesting parties, not as a point solution for sign-in.

A few things that frame the scale:

  • 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases, according to the State of Secrets in AppSec.

A question worth separating out:

Q: What should security teams do when a token is valid but the request still feels unsafe?

A: Reject the idea that token validity alone is sufficient. Recheck scopes, claims, issuer, expiration, and the current context at the enforcement point, then decide whether the request still fits the intended policy boundary. A valid token should not override a failed authorisation decision.

👉 Read our full editorial: Access control for AI agents and NHIs is becoming a governance problem



   
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.