What happened?
Okta, a leading identity tools provider, experienced a security breach that compromised its customer support unit. While Okta claims the breach affected only a “very small number” of customers, the hackers had access to Okta’s support platform for about two weeks.
Details of the Breach:
Attackers exploited a stolen credential to gain access to Okta’s support case management system, viewing files that customers had uploaded for recent support cases.
Okta often requests HTTP Archive (HAR) files from customers during troubleshooting, which contain sensitive data like cookies and session tokens. Attackers can use these to impersonate valid users.
Okta took protective measures, including the revocation of embedded session tokens and advised customers to sanitize HAR files before sharing.
BeyondTrust’s Involvement:
Security firm BeyondTrust alerted Okta about suspicious activities over two weeks before Okta acknowledged the breach.
BeyondTrust detected unauthorized activities using an Okta account belonging to one of its engineers. They traced the activity back to a HAR file sent to Okta, which was exploited 30 minutes later by the attacker.
BeyondTrust contacted Okta multiple times, asserting their suspicion of a breach at Okta.
Okta’s Response:
Initially, Okta didn’t think BeyondTrust’s alert indicated a system breach. By Oct. 17, however, Okta had identified and contained the incident, disabling the compromised account and invalidating associated Okta access tokens.
Okta’s Deputy Chief Information Security Officer, Charlotte Wylie, stated that the breach affected a “very, very small subset” of its 18,000+ customers.
Past Incidents:
Recently, Caesar’s Entertainment and MGM Resorts were hacked via social engineering attacks targeting Okta administrator accounts.
In March 2022, Okta disclosed another breach involving the hacking group LAPSUS$. This group socially-engineered a support engineer from Sitel, which had access to Okta resources.
Who was behind this?
While specific details about the attacker were not revealed, Okta believes it was a known threat actor that has previously targeted them and their customers.