Notifications
Clear all
Topic starter
07/06/2026 8:29 pm
TL;DR: AI applications that move into enterprise use must add authentication, authorization, multi-tenancy, provisioning, auditability, and real-time protection, according to WorkOS. The real shift is that these products stop behaving like isolated models and start behaving like identity-governed enterprise systems with users, agents, services, and tenants.
NHIMG editorial — based on content published by WorkOS: The enterprise infrastructure layer behind successful AI applications
By the numbers:
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security.
Questions worth separating out
Q: How should security teams govern AI products that use both human and non-human identities?
A: Treat the application as an identity-governed enterprise system.
Q: Why do enterprise AI applications create new authorization risks?
A: Because the application must now decide not only who the user is, but what they can do across tenants, roles, data types, and workflows.
Q: What breaks when AI app provisioning and deprovisioning are manual?
A: Manual lifecycle handling produces stale accounts, delayed revocation, and mismatched group membership as directories and roles change.
Practitioner guidance
- Map every AI-facing identity type Separate human users, AI agents, MCP servers, service accounts, and background jobs into distinct identity classes with distinct trust boundaries and revocation paths.
- Externalise authorization policy Move access logic out of application code and into centrally evaluated policy so tenant boundaries, role changes, and data sensitivity rules can be audited and updated without rewrites.
- Treat SCIM as a reconciliation system Design provisioning and deprovisioning to survive partial failures, provider quirks, and delayed updates.
What's in the full article
WorkOS's full article covers the operational detail this post intentionally leaves for the source:
- Implementation detail on enterprise SSO support across SAML, OAuth, and common identity providers.
- Step-by-step explanation of how the admin portal helps customers manage identity settings without support tickets.
- Operational breakdown of SCIM and directory sync handling across provisioning, role updates, and deprovisioning.
- Detailed descriptions of audit logs, feature flags, and key-management blocks used in production deployments.
👉 Read WorkOS's analysis of the enterprise infrastructure layer AI apps need →
Enterprise AI infrastructure: what IAM teams need to build now?
Explore further
07/06/2026 10:24 pm
AI products are becoming identity-governed enterprise systems, not just model experiences. The article shows that the hard problem is no longer the model, but the surrounding control plane: who can access it, what they can do, and how those decisions are logged. That is the same transition IAM teams have seen before in SaaS, but AI compresses it because humans, services, and agents now share the same product surface. Practitioners should treat AI application onboarding as an identity architecture problem, not a feature checklist.
A few things that frame the scale:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to The 2026 Infrastructure Identity Survey.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to The 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How can teams tell whether an AI product is ready for enterprise security review?
A: Look for evidence that the product can prove identity scope, tenant isolation, access revocation, and auditability without custom engineering for each customer. If those controls are missing, the product is still a prototype from a governance perspective, even if the model itself is production-ready.
👉 Read our full editorial: AI app enterprise infrastructure is now an identity problem
