New Updated Okta Statement on Lapsus$
LAPSUS$ has already responded on Telegram:<p>&#x27;&#x27;&#x27;<p><a href="https:&#x2F;&#x2F;www.okta.com&#x2F;blog&#x2F;2022&#x2F;03&#x2F;updated-okta-statement-on-lapsus&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.okta.com&#x2F;blog&#x2F;2022&#x2F;03&#x2F;updated-okta-statement-on-...</a><p>I do enjoy the lies given by Okta.<p>1. We didn&#x27;t compromise any laptop? It was a thin client.<p>2. &quot;Okta detected an unsuccessful attempt to compromise the account of a customer support engineer working for a third-party provider.&quot; -
I&#x27;m STILL unsure how its a unsuccessful attempt? Logged in to superuser portal with the ability to reset the Password and MFA of ~95% of clients isn&#x27;t successful?<p>4. For a company that supports Zero-Trust. <i>Support Engineers</i> seem to have excessive access to Slack? 8.6k channels? (You may want to search AKIA* on your Slack, rather a bad security practice to store AWS keys in Slack channels )<p>5. Support engineers are also able to facilitate the resetting of passwords and MFA factors for users, but are unable to obtain those passwords. -
Uhm? I hope no-one can read passwords? not just support engineers, LOL. - are you implying passwords are stored in plaintext?<p>6. You claim a laptop was compromised? In that case what <i>suspicious IP addresses</i> do you have available to report?<p>7. The potential impact to Okta customers is NOT limited, I&#x27;m pretty certain resetting passwords and MFA would result in complete compromise of many clients systems.<p>8. If you are committed to transparency how about you hire a firm such as Mandiant and PUBLISH their report? I&#x27;m sure it would be very different to your report :)<p>_________________________________________________________________________________________________________________________________________________________________________________________________________
<a href="https:&#x2F;&#x2F;www.okta.com&#x2F;sites&#x2F;default&#x2F;files&#x2F;2021-12&#x2F;okta-security-privacy-documentation.pdf" rel="nofollow">https:&#x2F;&#x2F;www.okta.com&#x2F;sites&#x2F;default&#x2F;files&#x2F;2021-12&#x2F;okta-securi...</a><p><i>21. Security Breach Management.
a) Notification: In the event of a Security Breach, Okta notifies impacted customers of such Security Breach. Okta
cooperates with an impacted customer’s reasonable request for information regarding such Security Breach, and Okta
provides regular updates on any such Security Breach and the investigative action and corrective action(s) taken.</i> -<p>But customers only found out today? Why wait this long?<p>9. Access Controls. Okta has in place policies, procedures, and logical controls that are designed:<p>b. Controls to ensure that all Okta personnel who are granted access to any Customer Data are based on leastprivilege principles;<p>kkkkkkkkkkkkkkk<p>1. Security Standards. Okta’s ISMP includes adherence to and regular testing of the key controls, systems and procedures of
its ISMP to validate that they are properly implemented and effective in addressing the threats and risks identified. Such
testing includes:
a) Internal risk assessments;
b) ISO 27001, 27002, 27017 and 27018 certifications;
c) NIST guidance; and
d) SOC2 Type II (or successor standard) audits annually performed by accredited third-party auditors (“Audit
Report”).<p>I don&#x27;t think storing AWS keys within Slack would comply to any of these standards?<p>&#x27;&#x27;&#x27;