Agent identity and permissionsAdditional if: Governed agents have delegated authority · The governed environment includes action-taking agents with delegated authority.Machine and workload identityAdditional if: Governed AI uses machine credentials · Governed AI systems use service accounts, API keys, machine identities, or other machine credentials.AI asset and configuration securityDirectly addresses · Discover approved, unmanaged, and action-taking AI systems along with model and software artifacts that require governance.AI governance, risk, and complianceDirectly addresses · Manage ownership, policies, risk reviews, approvals, exceptions, obligations, and audit evidence.
Vendor research
Okta for AI Agents
Review what this vendor says publicly, the security topics those statements may support, what remains unverified, and factual company context. This is not an assessment of product effectiveness or fit.
Use-case context
How this vendor relates to the selected use case
Related research availableBack to use case →
These links show approaches associated with this vendor. The relationship label describes how the approach maps to the use case—not product effectiveness, complete requirement coverage, or fit.
Company scale
Established?
EstablishedA provider with at least $1B in annual revenue, at least 1,000 employees, or backing from an established owner.This is a company-maturity signal, not a product-quality rating.
?
EstablishedA provider with at least $1B in annual revenue, at least 1,000 employees, or backing from an established owner.This is a company-maturity signal, not a product-quality rating.A descriptive band derived from retained public revenue, workforce, ownership, or funding signals.
Company scale is separate from product features, effectiveness, and suitability.
- $2.9B annual revenue (2026-01-31)
- $75M known funding
- 1000+ employees
Company context
Public company (Nasdaq: OKTA)
Okta positions itself as an independent identity platform for human, machine, and AI-agent identities
Research coverageCounts describe available public research, not product quality.View details
- Vendor statements
- 19 records
- Source-checked records
- 14
- Evaluation requirements
- 19 in this research model
- Unresolved requirements
- 5
Company intelligence
Who is behind the product
Company facts provide evaluation context. Each signal is kept separate because tenure, workforce, funding, and hiring answer different questions.
Founded2009
HeadquartersSan Francisco, California
OwnershipPublic company (Nasdaq: OKTA)
Employees1000+
Capital and scalePlatform provider
Okta
- Known funding
- $75M
- Operating scale
- Okta positions itself as an independent identity platform for human, machine, and AI-agent identities
- Backing context
- Public-company investment in Okta Workforce Identity, Customer Identity, Auth0, and Okta for AI Agents
SERIES_C_PLUS · $75M · 2015-09-01
Founders and leadership1 person listed
- Todd McKinnonCurrent role listed
CEO
Operating signalsRead each signal separately
There is no combined company rating. The company-scale label uses stated size thresholds; product features and effectiveness require separate evidence.
- Company tenure
- 2009
- Workforce scale
- 1000+
- Hiring activity
- Not displayed
A current count requires a retained, clickable source URL.
Open research questions
- A current hiring source is not available, so the count is not shown.
Company sources and research limits5 linked public sources
Only company facts supported by retained public sources are shown. Missing values remain unknown, and company scale does not establish product effectiveness.
Company sourceOkta for AI Agents pageOkta describes generally available discovery, onboarding, protection, credentialing, governance, audit, and lifecycle controls for AI agents.Company sourceOkta AI Agents Core announcementOkta's regulated-environment announcement describes the public-company identity platform and general availability of Okta for AI Agents Core.Company information sourcecompany_intelSupports the company facts shown in this profile.Company information sourceStored company websiteSupports the company facts shown in this profile.Regulatory filing10-K annual filingOkta, Inc. (OKTA) · period ended 2026-01-31
Solution areas
These areas describe how the vendor approaches enterprise AI security. They do not establish product quality or fit.
Buyer context
- Treat Okta for AI Agents as an identity, authorization, credentialing, and lifecycle control plane for agents rather than an AI content-security or red-teaming platform.
- Okta states that its core agent capabilities are generally available and include known and unknown agent discovery, registration, human ownership, short-lived credentials, least privilege, governance, audit, and deactivation.
- Public pages reviewed did not establish AI red teaming, browser content controls, software as a service (SaaS) embedded-AI feature inventory, FinOps, or a public licensing unit for the agent product.
Related frameworks
Where public vendor statements relate to framework requirements
11 related frameworks · expand when needed
Related frameworks
Where public vendor statements relate to framework requirements
These links show related requirements for further review. They do not establish framework compliance or control implementation. Open the full framework crosswalk →
Current referenceCIS Critical Security Controls
- Requirements with public support
- 13
- Related requirements
- 11
- References
- 58
- Requirements with public support
- 13
- Related requirements
- 14
- References
- 71
- Requirements with public support
- 13
- Related requirements
- 12
- References
- 35
- Requirements with public support
- 13
- Related requirements
- 12
- References
- 71
- Requirements with public support
- 13
- Related requirements
- 13
- References
- 39
- Requirements with public support
- 13
- Related requirements
- 12
- References
- 39
- Requirements with public support
- 13
- Related requirements
- 12
- References
- 31
- Requirements with public support
- 13
- Related requirements
- 11
- References
- 27
- Requirements with public support
- 13
- Related requirements
- 13
- References
- 31
- Requirements with public support
- 13
- Related requirements
- 13
- References
- 25
- Requirements with public support
- 3
- Related requirements
- 3
- References
- 3
Evaluation questions
What to verify beyond public claims
These questions come from security requirements with some public support. Use them as starting points for demonstrations, documentation review, customer references, or a buyer-observed pilot.
- 01Unapproved AI use discovery
An unmanaged AI app used by a test user appears in discovery inventory with user, app or domain, and timestamp.
- 02Unapproved AI use discovery
The test user's AI usage activity can be filtered or exported with AI-specific context.
- 03Approved AI usage monitoring
Approved AI workspace activity appears with user, workspace or tenant, model or provider, and timestamp.
- 04Approved AI usage monitoring
Prompt, model, or admin activity can be exported or correlated for the selected approved AI platform.
- 05Controls for unapproved AI use
A policy blocks, coaches, redirects, or contains a test interaction with an unapproved AI destination.
- 06Controls for unapproved AI use
The control event records policy reason, user, destination, action, and timestamp.
- 07Sensitive-data protection for generative AI
Sensitive prompt, response, or file test data is detected and classified during an AI interaction.
- 08Sensitive-data protection for generative AI
A policy redacts, blocks, coaches, or records the sensitive data event before it leaves the approved path.
Detailed security-requirement research18 evaluation items · supporting evidence and open research are shown separatelyExpand
Security requirementPublic supportRelated frameworksWhat to verify
Unapproved AI use discovery
Strong public supportDiscover and monitor workforce AI tools, accounts, prompts, domains, models, users, and usage outside approved controls.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
An unmanaged AI app used by a test user appears in discovery inventory with user, app or domain, and timestamp.
AI-feature discovery in business applications
No supporting claim foundInventory software as a service (SaaS) applications that embed AI features, expose enterprise data to AI capabilities, or create AI-driven data movement.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A software as a service (SaaS) app with an embedded AI feature appears in the software as a service (SaaS) AI inventory with app, provider, and feature context.
Approved AI usage monitoring
Strong public supportMonitor approved AI workspaces, tenants, gateways, and model platforms such as ChatGPT Enterprise, Claude Enterprise, Gemini, Microsoft Copilot, Vertex AI, Elvex, or internal AI gateways.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
Approved AI workspace activity appears with user, workspace or tenant, model or provider, and timestamp.
Controls for unapproved AI use
Limited public supportBlock, coach, redirect, or contain non-approved AI use and policy-violating AI interactions.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A policy blocks, coaches, redirects, or contains a test interaction with an unapproved AI destination.
Sensitive-data protection for generative AI
Limited public supportDetect, classify, redact, or block sensitive data in prompts, responses, files, retrieval, memory, and AI-connected workflows.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
Sensitive prompt, response, or file test data is detected and classified during an AI interaction.
Browser and business-application controls
No supporting claim foundApply session-level controls in browser and software as a service (SaaS) workflows, including uploads, downloads, copy/paste, sharing, and identity-aware access decisions.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A session-level policy controls upload, download, copy, paste, sharing, or form submission in a browser or software as a service (SaaS) workflow.
Generative AI application security
Limited public supportProtect enterprise-built large language model (LLM) applications, retrieval-augmented generation (RAG) systems, prompts, application programming interfaces (APIs), model calls, tools, and production runtime behavior.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test large language model (LLM) application event records prompt, application programming interface (API), model, retrieval, or tool interaction context.
AI governance, risk, and compliance
Strong public supportInventory AI systems and owners, translate policy and regulatory obligations into governed workflows, assess risk, manage approvals and exceptions, and retain audit evidence across the AI lifecycle.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test AI system is registered with owner, intended use, risk tier, lifecycle state, and applicable obligations.
AI assurance and adversarial testing
No supporting claim foundTest models, applications, retrieval-augmented generation (RAG) systems, and agents before release and continuously thereafter using adversarial probes, evaluation suites, attack simulation, and security release gates.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A controlled test campaign exercises an AI model, application, or agent against named AI attack classes.
AI model and supply-chain security
Limited public supportDiscover, inventory, scan, validate, and monitor models, datasets, model artifacts, registries, dependencies, and AI development assets for tampering, unsafe serialization, provenance gaps, or malicious content.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test model or AI artifact appears in inventory with origin, version, hash or provenance, and deployment context.
AI gateway, tool-connection, and runtime controls
Limited public supportMediate model, agent, tool, application programming interface (API), connector, and Model Context Protocol (MCP) traffic through an enforcement point that applies identity-aware policy, content controls, routing, rate limits, and auditable allow or deny decisions.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A model, agent, tool, or Model Context Protocol (MCP) request passes through a named policy enforcement point.
Action-taking agent monitoring
Strong public supportObserve and govern agent plans, memory, tool calls, delegated tasks, autonomy, runtime decisions, and outcomes.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test agent run captures plan, steps, tool calls, outcome, and timestamps.
Agent-to-agent communication security
Strong public supportAuthorize, log, and control agent-to-agent, agent-to-tool, Model Context Protocol (MCP), connector, and tool-chain handoffs.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
An agent, tool, connector, or Model Context Protocol (MCP) handoff logs source identity, destination, and authorization decision.
Non-human identity and service-account security
Strong public supportInventory, least privilege, credential hygiene, monitoring, and lifecycle management for non-human identities, workloads, service accounts, application programming interface (API) keys, and machine credentials.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test service account, agent identity, or non-human identity appears in inventory with owner and privileges.
AI agent identity and permissions
Strong public supportRegister AI agents as accountable identities, bind them to owners and delegating users, authorize task- and tool-level access, issue short-lived credentials, review access, and revoke or suspend agent authority.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test agent is registered with a unique identity, accountable owner, purpose, and permitted resources.
AI coding-agent and workstation security
Limited public supportDiscover and govern AI coding agents, integrated development environment (IDE) assistants, command-line agents, skills, hooks, extensions, Model Context Protocol (MCP) tools, filesystem access, commands, network activity, secrets, and software-supply-chain actions on developer workstations and build environments.
NIST AI RMF PlaybookNIST Cybersecurity Framework 2.0CIS Critical Security ControlsISO/IEC 42001OWASP GenAI Security Solutions Landscape
A test coding agent and its skills, hooks, extensions, or Model Context Protocol (MCP) tools appear in an attributable inventory.
AI cost and usage controls
No supporting claim foundVisibility, attribution, budgeting, rate limiting, anomaly detection, and optimization for AI usage and spend across models, agents, workflows, and owners.
Commercial MetadataNIST AI RMF PlaybookNIST Cybersecurity Framework 2.0ISO/IEC 42001OWASP Agentic AI Security Solutions Landscape
A controlled AI usage event is attributed to user, team, model, workflow, or owner with cost or token metrics.
Licensing model
No supporting claim foundPublicly discoverable commercial model such as per user, per seat, per app, per token, per integration, or enterprise platform license.
The vendor can map the sourced commercial model to per-user, per-seat, per-app, per-token, per-integration, or platform packaging.
Public sources
Vendor statements and quoted evidence
Showing the first 6 of 19 source records. Open additional records only when needed.
Okta claims continuous discovery of unknown AI agents and detection of OAuth consent grants for agents outside standard review.
Continuously discover unknown agents
Okta materials reviewed did not provide a public claim for tenant-level inventory of embedded AI features across enterprise software as a service (SaaS) applications.
No quoted source text is recorded for this claim.
Okta claims registration of agents and Model Context Protocol (MCP) servers in a centralized directory with assigned human owners.
Register your agents and MCP servers
Okta claims a kill switch that deactivates rogue agents and prevents new token requests.
Deactivate the agent with a kill switch
Okta claims least-privilege policies that constrain agent access to critical systems and data.
Enforce least-privilege policies to protect critical systems and data.
Okta materials reviewed did not provide a public claim for browser session controls over AI upload, download, copy, paste, sharing, or form submission.
No quoted source text is recorded for this claim.
Show 13 additional evidence records
Okta claims context-aware authorization policies that limit compromised agents after prompt injection.
context-aware authorization policies
Okta claims automated agent governance workflows, lifecycle access reviews, revocation, and full audit trails.
automated governance workflows
Okta materials reviewed did not provide a public claim for adversarial AI testing, red teaming, model evaluation, or release-gate regression testing.
No quoted source text is recorded for this claim.
Okta claims access management for tools, code repositories, and model registries to reduce unauthorized access and tampering.
tools, code repositories, and model registries
Okta claims centralized access policies over agent connections to Model Context Protocol (MCP) servers, application programming interfaces (APIs), and other agents.
from MCP servers to APIs and even other agents
Okta claims visibility into known and unknown agents, their owners, permissions, accessible resources, and lifecycle state.
see what they can access
Okta claims centralized access policies for connections between agents as well as Model Context Protocol (MCP) servers and application programming interfaces (APIs).
and even other agents
Okta claims secret and application programming interface (API)-key vaulting and rotation for AI-agent credential lifecycle.
Vault and rotate secrets and API keys
Okta claims unique agent registration, human ownership, short-lived credentials, runtime policies, governance, audit, and retirement.
temporary, short-lived credentials
Okta claims access management for code repositories and model registries used by developers.
managing access to the tools, code repositories, and model registries
Okta materials reviewed did not provide a public claim for AI spend attribution, budgets, chargeback, rate limits, or token-cost anomaly detection.
No quoted source text is recorded for this claim.
Okta materials reviewed did not provide a public licensing unit or price for Okta for AI Agents.
No quoted source text is recorded for this claim.
Okta claims a vendor-neutral identity control plane using standards across agents, identity providers, platforms, application programming interfaces (APIs), software as a service (SaaS), and cloud services.
Vendor-neutral