NHI sprawl and MCP authorization: what identity teams need to know

TL;DR: Enterprise identity now requires two parallel layers: human authentication and machine identity governance, according to WorkOS. Astrix Security focuses on discovery, rotation, monitoring, and AI agent controls for the non-human identity layer, including API keys, service accounts, and OAuth tokens. The practical takeaway is that modern IAM programmes need separate control models for humans, workloads, and autonomous agents.

NHIMG editorial — based on content published by WorkOS: Astrix Security vs. WorkOS: Non-Human Identity Meets Enterprise Authentication

By the numbers:

• For every human employee, there are roughly 100 non-human identities operating across cloud infrastructure, SaaS applications, and AI platforms.
• A 1,000-person company may have 100,000+ machine identities, many of which authenticate thousands of times per hour.
• 80% of identity breaches involved compromised non-human identities such as service accounts and API keys.

Questions worth separating out

Q: How should security teams govern non-human identities alongside human access?

A: Security teams should govern human and non-human access with separate control paths, because the lifecycle, credential type, and review evidence are different.

Q: Why do service accounts and API keys create more risk than many human accounts?

A: Service accounts and API keys often run continuously, carry broad scopes, and are reused across systems without interactive sign-in friction.

Q: What do organisations get wrong about AI agent authorisation?

A: They often treat agent access as a tooling problem instead of an identity problem.

Practitioner guidance

• Inventory every non-human identity class Map service accounts, API keys, OAuth grants, workload identities, and agent credentials across cloud, SaaS, CI/CD, and secrets stores.
• Separate human and machine access reviews Use different review criteria for employee accounts and non-human credentials.
• Replace static secrets with revocable delegated access Where MCP or API integrations require ongoing access, prefer standards-based OAuth flows, short-lived tokens, and scoped client registration instead of long-lived shared keys stored in code or agent memory.

What's in the full article

WorkOS's full article covers the operational detail this post intentionally leaves for the source:

• The full comparison of human authentication controls versus NHI governance patterns for enterprise teams.
• Implementation detail on AuthKit for MCP, including OAuth 2.1 authorisation flow, token handling, and client registration.
• The article's product-side breakdown of how WorkOS positions MCP authorisation alongside SSO, MFA, and directory sync.
• The vendor's own examples of where Astrix fits in the machine identity layer and where WorkOS applies in the human layer.

👉 Read WorkOS's analysis of NHI governance and MCP authorization →

NHI sprawl and MCP authorization: what identity teams need to know?

Explore further

View Full Forum →  |  NHI Foundation Course →