Notifications
Clear all
Topic starter
23/06/2026 9:24 pm
TL;DR: AI adoption at enterprise scale creates visibility, privilege, and lifecycle gaps that traditional identity governance does not cover, and Claude Enterprise access should be governed through the same controls used for human and non-human identities, according to Saviynt. That framing matters because AI access becomes another identity problem, not just a model-security problem.
NHIMG editorial — what this means for NHI practitioners
By the numbers:
- NHIs outnumber human identities by 25x to 50x in modern enterprises.
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them.
Questions worth separating out
Q: How should security teams govern AI platform access in enterprise environments?
A: Treat AI platform access as a governed entitlement, not a special case.
Q: Why do AI platforms create identity governance risk for IAM teams?
A: AI platforms can accumulate broad access to business data, workflows, and sensitive context faster than teams can review them.
Q: What do teams get wrong about least privilege for AI agents?
A: They often treat least privilege as a one-time provisioning rule instead of a continuous control.
Practitioner guidance
- Inventory AI platform entitlements alongside other identities Classify Claude Enterprise access as an entitlement with an owner, purpose, and review cadence.
- Tie AI onboarding and offboarding to lifecycle events Grant access only through controlled joiner, mover, and leaver workflows, then revoke access automatically when the business case ends.
- Require associated-account mapping for every entitlement Document which human or machine identity is accountable for each Claude access path, including delegated or shared accounts.
What's in the full announcement
Saviynt's full blog post covers the operational detail this post intentionally leaves for the source:
- How the Claude Compliance API integration maps AI access into Saviynt governance workflows
- The specific onboarding, offboarding, and certification flows the vendor describes for AI users and AI agents
- How associated accounts are surfaced for each entitlement in the product workflow
- The implementation framing for runtime authorisation, budget validation, and self-service requests
👉 Read Saviynt's analysis of identity security for Claude Enterprise →
Claude Enterprise identity governance: what AI access really changes?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
25/06/2026 2:43 am
AI platform access is now a non-human identity problem, not a sidecar governance issue. Once Claude Enterprise is embedded in workflows, its entitlements behave like any other NHI estate: they accumulate, drift, and outlive their original use case. The governance mistake is treating AI access as exceptional rather than inventoryable. Practitioners should manage the platform as part of the identity fabric, not as an isolated feature.
A few things that frame the scale:
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface, according to Ultimate Guide to NHIs.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them, according to Ultimate Guide to NHIs.
A question worth separating out:
Q: Who should be accountable for AI access decisions in identity programmes?
A: Accountability should sit with the identity or application owner who can justify the entitlement and revoke it when needed. Each AI permission should be linked to an accountable identity so certification, investigation, and audit can trace decisions back to a responsible owner.
👉 Read our full editorial: Identity security for Claude Enterprise exposes AI governance gaps
