- vendor
- Ping Identity
- whatItIs
- PingOne Privilege capability that discovers personal AI agents (including shadow AI), ties each agent session to the user and device behind it, and governs what each agent can access and do at the moment of action, without static stored credentials.
- hosting
- managed-only
- pricingModel
- not publicly listed
- modelProviders
- agnostic (governs agents in supported environments, including Claude desktop assistants and Claude Code)
- stateModel
- runtime sessions tied to the user and device; includes MCP server interactions
- toolModel
- discovery + secretless privileged access + runtime policy enforcement, including MCP server connections
- includesBrowser
- false
- includesMemory
- false
- observability
- record of what the agent did, when, and which user session it was tied to
- maturity
- ga
- launched
- 2026-09-01
- notes
- Announced 2026-09-01, 5 days before this run's nominal window start (2026-09-06); included here on the same baseline-gap logic used for the other identity/guardrails candidates in this batch (JumpCloud Agentic IAM, Temporal), since the topic has no other agent-identity governance entry besides the already-tracked Okta Agent SSO. Distinct from Okta Agent SSO (Cross App Access/XAA token issuance via Universal Directory): Ping's product is framed around discovering and controlling *personal* agents already in use (e.g. Claude, Claude Code) rather than issuing SSO tokens for registered agent identities. Delivered through PingOne Privilege; already piloted with enterprise customers at launch.