Incident
Okta Breach Affected All Customer Support Users
Credentials from an employee's personal Google account provided access to Okta's support system, exposing data across the entire customer base.
Key Finding
Initially reported as affecting a few customers (1Password, Cloudflare, BeyondTrust), Okta later disclosed it affected ALL support system users.
In October 2023, Okta disclosed that an attacker had gained access to their customer support management system. The initial disclosure suggested a limited number of customers were affected. Early reports named 1Password, Cloudflare, and BeyondTrust as victims who detected suspicious activity.
A month later, Okta revised the scope: the breach affected all customer support system users. Every organization that had ever filed a support ticket with Okta had their name and email address exposed.
The entry point was personal credential compromise. An Okta employee had saved their work credentials in their personal Google account. When those personal credentials were compromised, the attacker gained access to Okta's support platform, a system that stores HAR files and session tokens uploaded by customers during troubleshooting.
When your identity provider is the breach target, the blast radius is existential. Okta serves as the identity layer for thousands of organizations worldwide. A compromise of Okta's systems is functionally a supply chain attack on the identity infrastructure of every customer.
This incident underscores why identity architecture must include third-party IdP risk assessment, session monitoring for support tool access, and contractual requirements for identity hygiene at your identity vendors. The security of your identity architecture is only as strong as the identity practices of the organizations you depend on.
Need help with your identity architecture?
Every incident on this page was preventable with the right architecture. Let's talk about yours.
Book a Conversation