IDSync Newsletter

Issue 001 — AI agent identity takes center stage

How vendors are scrambling to give non-human identities first-class lifecycle, the SCIM 2.1 draft, and what buyers should ask about agent identity in their next RFP.

Published 5/30/2026 · Updated 5/30/2026

This week IDSync tracked a clear shift: identity vendors are no longer treating AI agents as a sub-case of service accounts. Three platforms shipped agent-specific identity primitives, the SCIM 2.1 draft picked up support for non-human identity attributes, and two large enterprises disclosed agent identity sprawl as a board-level risk. Below, the updates that actually matter for buyers and builders.

AI agent identity

  • Vendors ship agent-specific identity primitives

    Three identity platforms introduced first-class agent identity objects this week, separating them from human users and service accounts. Buyers running agent pilots should ask how lifecycle, scoping, and revocation differ from existing service-account flows.

SCIM/provisioning

  • SCIM 2.1 draft adds non-human identity attributes

    The working draft extends the SCIM schema with attributes specifically for non-human and agent identities. If your IGA or HRIS-driven provisioning relies on SCIM, expect to revisit your mappings in the next 12 months.

IAM implementation lessons

  • Two enterprises name agent identity sprawl a board-level risk

    Both organizations cited an inability to inventory AI agents acting on behalf of employees. Practical takeaway: add an agent inventory column to your access review tooling now, even if your IGA platform does not formally support it yet.