Okta Corporate Blog
Blog
Accelerate a world where everyone can safely use any technology. We bring simple and secure access to people and organizations everywhere. Source
Actions
Media Outlet details
| Scope | International |
|---|---|
| Language | English, Japanese |
| Country | United States of America |
|
Similarweb UVM |
Request pricing |
|
Comscore UVM |
Request pricing |
Recent Articles
Search ArticlesMuck Rack - Sign In
Sign in with your account to access Google Javascript is disabled on your browser. Please enable Javascript and refresh this page. Refresh Your OneDrive version is not supported Upgrade now by installing the OneDrive for Business Next Generation Sync Client to login to Okta Learn how to upgrade Cookies are disabled on your browser. Please enable Cookies and refresh this page. Refresh The page has timed out If this page does not reload automatically, please refresh your browser.
The anatomy of modern identity attacks: Defending public sector missions in an AI-driven threat landscape
Across federal, state, and local government agencies, mission delivery has fundamentally shifted. From delivering digital citizen services and modernizing legacy infrastructure to enabling hybrid public workforces, the era of static network perimeters and traditional castle-and-moat security models is over.
How Okta Workflows scales enterprise IT and security operations
Discover how Vimeo and Foursquare secure and scale with Okta Workflows Okta Workflows is a no-code identity automation platform that eliminates manual IT tasks like user onboarding, offboarding, and license provisioning. By replacing custom scripts with event-driven, drag-and-drop logical flows, enterprises like Vimeo and Foursquare save more than 1,000 hours annually and achieve a 100% success rate on complex device migrations. Add it up: More than 1,000 hours and $45,000 saved a year at Vimeo.
What it takes to own AI agent identity as agents spread
As AI agents scale, there’s a hidden cost to maintaining a custom-built agent access layer. Investing in a centralized governance solution keeps your engineers focused on the work that impacts your business. Managing enterprise AI agent identity internally quickly scales into a continuous governance and compliance burden. It requires centralizing authentication, authorization, token lifecycle management, and audit logging across all internal, third-party, and shadow agents.
Modernizing DoW/IL5 Office 365 identity lifecycle management
Okta's native Office 365 integration and Okta Workflows Office 365 connector for DoW IL5 deliver policy-driven, no-code identity lifecycle automation for DoW and federal GCC High cloud environments. The solution replaces custom PowerShell scripts and static service accounts with OAuth 2.0 client credentials, providing automated SSO, user provisioning, and Zero Trust access controls within sovereign cloud boundaries.
Governing AI agents: Four questions every government agency needs to answer
BLUF Legacy constraints: 68% of surveyed government employees report intense pressure to deploy agentic AI, yet legacy access controls can’t secure non-human identities at mission speed. Zero Trust modernization: Implementing Zero Trust governance allows federal agencies to meet modernization directives while eliminating the visibility gaps that lead to compliance failures and security incidents.
Build a Secure TypeScript MCP Client with Cross App Access (XAA)
Enterprise apps rarely work alone. Imagine this scenario: HR wants to ensure that a new employee completes their new hire onboarding, and they want this verification in the company’s HR app so it’s tied to the employee’s personnel file. But the onboarding tasks come from a task-tracking tool with requirements defined by each department, from a different vendor and on a different domain than the HR app. It’s on IT to bridge the two.
Securing AI agents at runtime with Okta's Agent Gateway
Agent Gateway is a runtime identity enforcement layer within Okta for AI Agents. It validates every agent-to-tool request against identity policies using RFC 8693 token exchange. Unlike traditional gateways that rely on shared service keys, Agent Gateway requires credentials naming both the acting AI agent and the human user, preventing confused deputy attacks and unauthorized permission inheritance.
The agent is not the user: Using Amazon Bedrock AgentCore with Okta to secure AI agent identity
Rather than impersonating the user, the agent uses a two-step delegation process: The ID-JAG step: The agent presents the user's authentication token as the subject token and authenticates itself using its own credentials. Okta binds the user's identity to the agent's workload context, scoped to the target resource authorization server's audience. This produces a short-lived, one-time-use ID-JAG token.
Resource Access Certifications for AI Agents: Reduce the agent attack surface. Close the audit gap.
Two AI agent governance challenges: security and compliance Agents pose new security and compliance challenges, and most organizations are unprepared to address them. More than 60% of survey respondents in Okta’s AI at Work 2025 report cited security as their primary AI concern, and 69% mentioned governing the non-human identity (NHI) lifecycle, including account creation and deactivation, as a key concern.