“Upon investigation, we have concluded that such access was used to copy Okta code repositories,” Okta says in an advisory email. While this is clearly a dangerous breach, it seems the hackers were unable to access the Okta backend or any customer data. “No customer action is required and the Okta service remains fully operational and secure,” the email adds.

Action

Following GitHub’s warning to Okta, the company saw the breach and put in place access restrictions to all GitHub repositories on a temporary basis. This means all GitHub integrations and third-party apps connected to the repository were suspended “We have since reviewed all recent access to Okta software repositories hosted by GitHub to understand the scope of the exposure, reviewed all recent commits to Okta software repositories hosted with GitHub to validate the integrity of our code, and rotated GitHub credentials. We have also notified law enforcement. Additionally, we have taken steps to ensure that this code cannot be used to access company or customer environments. Okta does not anticipate any disruption to our business or our ability to service our customers as a result of this event.” Okta is planning to publish on its blog today to discuss the breach and any follow ups on the situation. At the time of writing, that blog post is not available. Tip of the day: Having problems with pop-ups and unwanted programs in Windows? Try the hidden adware blocker of Windows Defender. We show you how to turn it on in just a few steps.

Okta Confirms Breach of its GitHub Code Repositories - 73Okta Confirms Breach of its GitHub Code Repositories - 98Okta Confirms Breach of its GitHub Code Repositories - 76Okta Confirms Breach of its GitHub Code Repositories - 7Okta Confirms Breach of its GitHub Code Repositories - 83