What happened
Replaying the Okta support vendor January 2022 intrusion
- 1
Inside the support vendor
Jan 16 to Jan 21, 2022The attacker has access to Sitel's environment for five days, and a password factor added to a Sitel employee's Okta account stops at the MFA challenge.
- 2
Okta's support tools
Jan 21, 2022; time of day not statedThrough a Sitel workstation already signed in to Okta, the actor opens two customer tenants in SuperUser and views Slack and Jira; no change, reset or impersonation succeeds.
- 3
Screenshots and disclosure
Jan 21 to Apr 19, 2022Screenshots taken on the workstation are posted in March, Okta discloses on March 22, ends its work with Sitel and concludes its investigation in April.
One Sitel support engineer's workstation controlled for 25 consecutive minutes on January 21, 2022, two active customer tenants accessed in Okta's SuperUser support tool and limited information viewed in Slack and Jira; no configuration change, MFA or password reset or support impersonation succeeded. Okta's worst-case scope was 366 customers, approximately 2.5%, and the final impact was significantly less. Okta says the Okta service was not breached, and it does not consider the incident material.
A vendor's support tooling, outside every cloud
This chain lived in a vendor's support tooling: a Sitel workstation already signed in to Okta, Okta's SuperUser support tool and two customer Okta tenants. No AWS, Azure, Google Cloud or Oracle Cloud control sees any of them. What held were Okta's own checks, the MFA challenge and SuperUser's limits, and no change, reset or impersonation succeeded. If your Okta tenant signs your users in to a cloud, that cloud can still bound a hijacked sign-in: an AWS resource control policy on AWS Sign-In, Microsoft Entra Conditional Access that requires a compliant device, or Google Cloud Context-Aware Access that requires a managed device. No source says either customer had such a federation. Okta's own answer sat at the vendor's layer: it now manages third-party support devices directly and limits what a support engineer can view.
Could this have been prevented?
In hindsight, no control would have stopped it. 2 controls would have limited how far it went. 7 steps have no cloud-provider control. The counts below are control assessments, not attack stages: several can address the same step. The same replay with the controls in place before the incident shows where each phase would have been refused or bounded.
- 0
- Prevented
- 2
- Contained
- 7
- Not covered
How it could have been prevented
The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.
Replaying the Okta support vendor January 2022 intrusion
1 · Inside the support vendor
1 Contained2 Not covered2 · Okta's support tools
1 Contained3 Not covered10 on other clouds3 · Screenshots and disclosure
2 Not coveredKey facts
- Okta's final forensic report found that the threat actor actively controlled one Sitel support engineer's workstation for 25 consecutive minutes on January 21, 2022
- In that time the actor accessed two active customer tenants in Okta's SuperUser application and viewed limited information in Slack and Jira; it could not successfully make a configuration change, an MFA or password reset or a support impersonation event
- At 23:18 UTC on January 20, 2022 a password factor was added to a Sitel employee's Okta account from a new location; the MFA challenge was not accepted, and Okta suspended the account at 00:28 UTC on January 21. Whether the suspension came before or after the 25 minutes is not stated
- Okta first scoped the worst case at 366 customers, approximately 2.5%, whose tenants any Sitel support engineer accessed in SuperUser from January 16 to 21; the final impact was significantly less
- Screenshots from the workstation, with a system date of January 21, 2022 per BleepingComputer, were published on March 21, 2022 (US date); Okta had received Sitel's summary report on March 17 without them, and it disclosed on March 22
- LAPSUS$ claimed that Okta stored AWS keys in Slack channels; no source confirms that a key existed or was used, and no Okta source addresses the claim
Sources
Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.
- 1.Updated Okta Statement on LAPSUS$Okta · Mar 22, 2022 · Vendor reportJanuary detection and response, five-day window, support engineer capabilities, 2.5% estimate, customer notification by email, products not affected, no customer action
- 2.Okta's Investigation of the January 2022 CompromiseOkta · Mar 24, 2022 · Vendor reportdetection and containment timeline, Sitel and Sykes relationship, RDP remote access, Sitel-managed device, SuperUser tool and its limits, 366 maximum potential impact, log review, Sitel report dates, notification delay
- 3.Frequently Asked Questions Regarding the January 2022 CompromiseOkta (Okta Support) · Mar 3, 2026 · Vendor reportpassword factor, five-day period, notification delay, vendor identity, SuperUser meaning, 366 method, Sitel remediation, vendor termination, no customer action
- 4.Okta Concludes its Investigation Into the January 2022 CompromiseOkta · Apr 20, 2022 · Vendor reportfinal scope, 25-minute control, two customer tenants, actions not performed, customer notification, corrective actions, end of the vendor relationship
- 5.Form 8-K, Item 8.01 Other EventsOkta (SEC Form 8-K) · Mar 25, 2022 · Vendor reportscreenshot date, vendor remediation advice, five-day window validated by Okta, 366 maximum, materiality, blog post dates
- 6.Form 8-K/A, amendment to Item 8.01Okta (SEC Form 8-K/A) · Apr 19, 2022 · Vendor reportfinal forensic findings, 25-minute control, two customer tenants, actions not performed, materiality
- 7.Auditing Customer Support Actions in the Okta Tenant Using System LogOkta (Okta Support) · Mar 6, 2026 · Vendor reportSystem Log events for support actions, support impersonation grant, log retention, audit queries
- 8.Cloudflare's investigation of the January 2022 Okta compromiseCloudflare · Mar 22, 2022 · Vendor reportscreenshot circulation time, customer detection and response, System Log events searched, Okta confirmation of no events, customer recommendations
- 9.Review of the Attacks Associated with Lapsus$ and Related Threat GroupsCyber Safety Review Board (DHS), hosted by CISA · Jul 24, 2023 · Advisoryofficial characterization, supply chain framing, credential storage examples
- 10.Okta investigating claims of customer data breach from Lapsus$ groupBleepingComputer · Mar 22, 2022 · Newsscreenshot contents and system date, group's first claims, Okta's first public statements
- 11.Okta 'identifying and contacting' customers potentially affected by Lapsus$ breachThe Record (Recorded Future News) · Mar 22, 2022 · Newsgroup's reply and claims, AWS keys in Slack claim, timing of Okta's first response
- 12.Sitel blames Okta breach on 'legacy' network from acquisitionThe Record (Recorded Future News) · Mar 30, 2022 · NewsSitel's statement, legacy Sykes network, Sitel awareness and client notice dates, spreadsheet denial
The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.