{"id":19461,"date":"2022-03-22T12:09:35","date_gmt":"2022-03-22T16:09:35","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/okta-hack-consequences\/19461\/"},"modified":"2022-03-23T16:12:53","modified_gmt":"2022-03-23T12:12:53","slug":"okta-hack-consequences","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/okta-hack-consequences\/19461\/","title":{"rendered":"What are the possible consequences of Okta hack?"},"content":{"rendered":"<p>Hackers belonging to the LAPSUS$ cybercrime group have published screenshots, allegedly taken from inside Okta\u2019s information systems. If the claims are true, they have access not only to the company\u2019s website, but also to a number of other internal systems, including quite critical ones.<\/p>\n<p>LAPSUS$ claims that they did not steal any data from the company itself, and that their targets were mainly Okta\u2019s customers. Judging by the dates on the screenshots, the attackers had access to the systems as early as January 2022.<\/p>\n<h2>What is Okta and why could the breach be so dangerous?<\/h2>\n<p>Okta develops and maintains identity and access management systems. In particular, they provide a single sign-on solution. A huge number of large companies employ Okta\u2019s solutions.<\/p>\n<p>Kaspersky Lab experts believe that the hacker\u2019s access to Okta\u2019s systems can explain a number of the rather high-profile data leaks from large companies, for which hackers from LAPSUS$ have already claimed responsibility.<\/p>\n<h2>How cybercriminals gain access to Okta\u2019s systems?<\/h2>\n<p>At the moment there is no conclusive evidence that the hackers really gained access. According to an <a href=\"https:\/\/www.okta.com\/blog\/2022\/03\/okta-official-statement-on-lapsus-claims\/\" target=\"_blank\" rel=\"nofollow noopener\">Okta\u2019s official statement<\/a>, its specialists are currently conducting an investigation and the company promises to share details as soon as the investigation is completed. It is possible that the published screenshots are related to the January incident, when an unknown actor tried to compromise the account of a technical support engineer working for a third-party subcontractor.<\/p>\n<p>Updated on March 23, 2022: LAPSUS$ has published their reply to Okta\u2019s official statement in which they accuse the company in attempts to downplay the impact of the breach.<\/p>\n<p><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2022\/03\/23161249\/okta-hack-consequences-lapsuss-reply.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/37\/2022\/03\/23161249\/okta-hack-consequences-lapsuss-reply.png\" alt=\"LAPSUS$ reaction to the official Okta statement.\" width=\"900\" height=\"700\" class=\"aligncenter size-full wp-image-19466\"><\/a><\/p>\n<h2>Who are the LAPSUS$ group and what do we know about them? <\/h2>\n<p>LAPSUS$ gained fame in 2020 when they compromised the Brazilian Ministry of Health\u2019s systems. Presumably, this is a Latin American hacker group that steals information from large companies for ransom. If the victims refuse to pay, the hackers publish the stolen information on the Internet. Unlike many other ransomware groups, LAPSUS$ does not encrypt the data of hacked organizations, but simply threatens to leak the data in case of non-payment of the ransom.<\/p>\n<p>Notable victims of LAPSUS$ include Nvidia, Samsung and Ubisoft. In addition, they recently released 37 GB of code believed to be related to internal Microsoft projects.<\/p>\n<h2>How to stay safe? <\/h2>\n<p>At the moment it is impossible to say with absolute certainty that the incident really happened. The publication of screenshots in itself is a rather strange move that may be aimed at self-promotion of the hackers, an attack on Okta\u2019s reputation, or an attempt to hide the real method by which LAPSUS$ gained access to one of Okta\u2019s clients.<\/p>\n<p>That said, to play it safe our experts recommend Okta\u2019s clients to employ the following protective measures:<\/p>\n<ul>\n<li>Enforce especially stringent monitoring of network activity and in particular of any activity related to authentication in internal systems;<\/li>\n<li>Provide staff with an additional cybersecurity hygiene training and prepare them to be alert and report on any suspicious activity;<\/li>\n<li>Perform a security audit of your organization\u2019s IT infrastructure to reveal gaps and vulnerable systems;<\/li>\n<li>Restrict access to remote management tools from external IP addresses;<\/li>\n<li>Ensure that remote control interfaces can only be accessed from a limited number of endpoints;\n<\/li><li>\n<\/li><li>Follow the principle of offering staff limited privileges and grant high-privileged accounts only to those who need this to fulfil their job;<\/li>\n<li>Use ICS network traffic monitoring, analysis and detection solutions for better protection from attacks potentially threatening technological process and main enterprise assets.<\/li>\n<\/ul>\n<p>Companies that do not have the internal resources to monitor suspicious activity in their IT infrastructure can employ the <a href=\"https:\/\/me-en.kaspersky.com\/enterprise-security\/managed-detection-and-response?icid=me-en_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder_______\" target=\"_blank\" rel=\"noopener\">external experts<\/a>.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"mdr\">\n","protected":false},"excerpt":{"rendered":"<p>Hackers from Lapsus$ group claim they breached Okta, a major provider of access management systems.<\/p>\n","protected":false},"author":2698,"featured_media":19462,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1318,1916,1486],"tags":[359,78,2549,1758],"class_list":{"0":"post-19461","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-enterprise","9":"category-threats","10":"tag-authentication","11":"tag-hackers","12":"tag-okta","13":"tag-supply-chain"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/okta-hack-consequences\/19461\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/okta-hack-consequences\/23978\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/okta-hack-consequences\/9796\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/okta-hack-consequences\/26279\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/okta-hack-consequences\/24238\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/okta-hack-consequences\/24095\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/okta-hack-consequences\/27012\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/okta-hack-consequences\/26551\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/okta-hack-consequences\/32979\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/okta-hack-consequences\/10570\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/okta-hack-consequences\/43971\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/okta-hack-consequences\/18644\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/okta-hack-consequences\/19149\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/okta-hack-consequences\/15866\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/okta-hack-consequences\/28356\/"},{"hreflang":"nl","url":"https:\/\/www.kaspersky.nl\/blog\/okta-hack-consequences\/28165\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/okta-hack-consequences\/24890\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/okta-hack-consequences\/30323\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/okta-hack-consequences\/30095\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/supply-chain\/","name":"supply chain"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/19461","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2698"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=19461"}],"version-history":[{"count":4,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/19461\/revisions"}],"predecessor-version":[{"id":19467,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/19461\/revisions\/19467"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/19462"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=19461"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=19461"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=19461"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}