Identity and access management tech firm Okta says it has concluded an investigation into the embarrassing Lapsus$ hacking incident and has severed ties with a third-party company at the center of the breach.
Facing public criticism for communications hiccups after the breach was detected, Okta issued a public statement Wednesday to stress that the impact from the incident was “significantly smaller than we initially scoped.”
A statement from Okta’s Chief Information Security Officer (CISO) David Bradbury said the company initially determined that about 366 customers were affected but a third-party forensic audit showed the damage was contained.
Bradbury described the main conclusions from the audit, which was conducted by an unnamed globally recognized cybersecurity forensic firm:
- The threat actor actively controlled a single workstation, used by a Sykes/Sitel support engineer, with access to Okta resources.
- Control lasted for 25 consecutive minutes on January 21, 2022.
- During that limited window of time, the threat actor accessed two active customer tenants within the SuperUser application (whom we have separately notified), and viewed limited additional information in certain other applications like Slack and Jira that cannot be used to perform actions in Okta customer tenants.
- The threat actor was unable to successfully perform any configuration changes, MFA or password resets, or customer support “impersonation” events.
- The threat actor was unable to authenticate directly to any Okta accounts.
“While the overall impact of the compromise has been determined to be significantly smaller than we initially scoped, we recognize the broad toll this kind of compromise can have on our customers and their trust in Okta,” Bradbury said.
He said Okta had terminated its relationship with Sykes/Sitel and will now “directly manage” all devices of third parties that access its customer support tools.
“We are making further modifications to our customer support tool to restrictively limit what information a technical support engineer can view. These changes also provide greater transparency about when this tool is used in customer admin consoles,” Bradbury added.
Related: The Chaos (and Cost) of the Lapsus$ Hacking Carnage
Related: Microsoft, Okta Confirm Data Breaches Involving Compromised
Related: Credentials of 71,000 NVIDIA Employees Leaked by Lapsus$
Ryan Naraine is Editor-at-Large at SecurityWeek and host of the popular Security Conversations podcast series. He is a security community engagement expert who has built programs at major global brands, including Intel Corp., Bishop Fox and GReAT. Ryan is a founding-director of the Security Tinkerers non-profit, an advisor to early-stage entrepreneurs, and a regular speaker at security conferences around the world.
More from Ryan Naraine
- VMware Confirms Exploit Code Released for Critical vRealize Logging Vulnerabilities
- Gem Security Gets $11 Million Seed Investment for Cloud Incident Response Platform
- Ransomware Leads to Nantucket Public Schools Shutdown
- Sentra Raises $30 Million for DSPM Technology
- Saviynt Raises $205M; Founder Rejoins as CEO
- OpenVEX Spec Adds Clarity to Supply Chain Vulnerability Warnings
- Tenable Launches $25 Million Early-Stage Venture Fund
- VMware Plugs Critical Code Execution Flaws
Latest News
- Fraudulent “CryptoRom” Apps Slip Through Apple and Google App Store Review Process
- US Downs Chinese Balloon Off Carolina Coast
- Microsoft: Iran Unit Behind Charlie Hebdo Hack-and-Leak Op
- Feds Say Cyberattack Caused Suicide Helpline’s Outage
- Big China Spy Balloon Moving East Over US, Pentagon Says
- Former Ubiquiti Employee Who Posed as Hacker Pleads Guilty
- Cyber Insights 2023: Venture Capital
- Atlassian Warns of Critical Jira Service Management Vulnerability
