{"id":2130630,"date":"2022-03-23T16:21:00","date_gmt":"2022-03-23T14:21:00","guid":{"rendered":"http:\/\/nhub.news\/?p=2130630"},"modified":"2022-03-23T18:03:16","modified_gmt":"2022-03-23T16:03:16","slug":"okta-says-hack-from-lapsus-group-may-have-ensnared-366-brands","status":"publish","type":"post","link":"http:\/\/nhub.news\/ru\/2022\/03\/okta-says-hack-from-lapsus-group-may-have-ensnared-366-brands\/","title":{"rendered":"Okta Says Hack From LAPSUS$ Group May Have Ensnared 366 Brands"},"content":{"rendered":"<p style=\"text-align: justify;\"><b>However, the company maintains the compromised laptop only had restricted access to Okta accounts belonging to corporate customers.<\/b><br \/>\nOkta says the LAPSUS$ gang hack may have affected 2.5% of its corporate customers, or 366. In a more detailed report released on Tuesday, Okta said the hack involved LAPSUS$ remotely compromising a computer belonging to a customer support engineer contracted out from a third-party outsourcing firm called Sitel. Access was achieved through Microsoft\u2019s Remote Desktop Protocol; the computer itself was owned by Sitel. \u201cThe scenario here is analogous to walking away from your computer at a coffee shop, whereby a stranger has (virtually in this case) sat down at your machine and is using the mouse and keyboard,&#187; said Okta Chief Security Officer David Bradbury. Not So SuperUser It&#8217;s not clear how the LAPSUS$ group gained remote access. But despite the hack, Okta said the customer support engineer\u2019s computer contained only limited access to customer accounts. \u201cThe majority of support engineering tasks are performed using an internally built application called SuperUser or SU for short, which is used to perform basic management functions of Okta customer tenants. This does not provide \u2018god-like access\u2019 to all its users,\u201d Bradbury said. A post from LAPSUS$ claiming the group had &#8216;SuperUser&#8217; access to Okta&#8217;s systems. However, Okta says the SuperUser access is actually quite limited. \u201cThis is an application built with least privilege in mind to ensure that support engineers are granted only the specific access they require to perform their roles,\u201d he added. \u201cThey are unable to create or delete users. They cannot download customer databases. They cannot access our source code repositories.\u201d It\u2019s also why Okta believes the hack failed to breach the company itself or customer accounts. Nevertheless, the LAPSUS$ gang did have a five-day window, between Jan.16-21, to access the compromised computer. During this time, the hackers also had access to systems at Sitel, which offers services to over 700 brands across the globe. \u201cIn trying to scope the blast radius for this incident, our team assumed the worst case scenario and examined all of the access performed by all Sitel employees to the SuperUser application for the five-day period in question,\u201d Bradbury said. As a result, over the past 24 hours the company has examined more than 125,000 log entries to determine what actions were performed on the compromised computer. \u201cWe have determined that the maximum potential impact is 366 (approximately 2.5% of) customers whose Okta tenant was accessed by Sitel,\u201d Bradbury said. \u201cBecause of the access that the support engineers had, the information and the actions were constrained. While it is not a necessary step for customers, we fully expect they may want to complete their own analysis,\u201d he added. \u201cFor transparency, these customers will receive a report that shows the actions performed on their Okta tenant by Sitel during that period of time. We think this is the best way to let customers assess the situation for themselves.\u201d &#8216;We Should Have Moved More Swiftly&#8217; Okta first learned of the hack on Jan.20, when the company\u2019s security team detected an attempt to add a new multi-factor authentication login over the customer support engineer\u2019s Okta account. In response, the company reset the Okta account a day later, and notified Sitel to hire a \u201cleading forensic firm\u201d to perform an investigation. The problem is that Sitel\u2019s forensic investigation wasn\u2019t conducted until Feb.28. The resulting forensic report on the incident also wasn\u2019t sent to Okta until March 17, mere days before LAPSUS$ would announce it had allegedly breached Okta. In addition, Okta said it only received the \u201ccomplete investigation report\u201d on the attempted hack on Tuesday. Hence, the company never alerted customers about the potential breach. \u201cI am greatly disappointed by the long period of time that transpired between our notification to Sitel and the issuance of the complete investigation report,\u201d Bradbury said. \u201cUpon reflection, once we received the Sitel summary report we should have moved more swiftly to understand its implications.\u201d In a statement, Sitel told PCMag: &#171;Following completion of the initial investigation, working in partnership with the worldwide cybersecurity leader, we continue to investigate and assess potential security risks to both our infrastructure and to the brands we support around the globe. As a result of the investigation, along with our ongoing assessment of external threats, we are confident there is no longer a security risk.&#187; Okta published more details about the breach after offering a vague and confusing assessment of the incident hours earlier on Tuesday. It\u2019s unclear which Okta customers were affected, but the company serves major brands including Grubhub, Jetblue, T-Mobile, Sonos, and Peloton, by providing authentication and login management systems. The LAPSUS$ gang so far hasn\u2019t commented on Okta\u2019s latest statement. But on Tuesday, the group rebutted Okta\u2019s assertion that the January hack had a limited impact. \u201cI&#8217;m STILL unsure how it\u2019s a unsuccessful attempt?\u201d the group wrote in a public chat. \u201cLogged in to superuser portal with the ability to reset the Password and MFA of ~95% of clients isn&#8217;t successful?\u201d Crossing a Redline Microsoft, which was also recently hacked by LAPSUS$, has published a report on the cybergang\u2019s activities. The report concludes LAPSUS$ is likely breaking into organizations by circulating the Redline password stealer malware, buying stolen logins from other cybercriminals, and paying employees at targeted organizations for access to company systems. &#171;In other observed activity, DEV-0537 (LAPSUS$) actors performed a SIM-swapping attack to access a user\u2019s phone number before signing into the corporate network. This method allows the actors to handle phone-based authentication prompts they need to gain access to a target,&#187; Microsoft said.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>However, the company maintains the compromised laptop only had restricted access to Okta accounts belonging to corporate customers. Okta says the LAPSUS$ gang hack may have affected 2.5% of its corporate customers, or 366. In a more detailed report released on Tuesday, Okta said the hack involved LAPSUS$ remotely compromising a computer belonging to a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2130629,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[93],"tags":[],"_links":{"self":[{"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/posts\/2130630"}],"collection":[{"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/comments?post=2130630"}],"version-history":[{"count":0,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/posts\/2130630\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/media\/2130629"}],"wp:attachment":[{"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/media?parent=2130630"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/categories?post=2130630"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/tags?post=2130630"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}