1Password: Difference between revisions

Line 38:

1Password, which uses an Okta instance, published a blog post disclosing an internal investigation of the breach.<ref>{{Cite web |last=Canahuati |first=Pedro |date=2023-10-23 |title=Okta Support System incident and 1Password |url=https://blog.1password.com/okta-incident/ |url-status=live |archive-url=https://web.archive.org/web/20250905070945/https://blog.1password.com/okta-incident/ |archive-date=2025-09-05 |access-date=2025-09-05 |work=1Password Blog}}</ref> According to their disclosure, the attackers' actions triggered an email to a member of the IT team who acted swiftly to contain the breach. The company reported that no user data was exfiltrated or decrypted.<ref>{{Cite web |date=2023-10-27 |title=Security incident report |url=https://blog.1password.com/files/okta-incident/okta-incident-report.pdf |archive-url=https://web.archive.org/web/20250920201057if_/https://blog.1password.com/files/okta-incident/okta-incident-report.pdf |archive-date=2025-09-20 |access-date=2026-01-23 |website=1Password Blog}}</ref>

===1Password License Controversy===

Revision as of 13:05, 30 April 2026 edit Languagedivided (talk \| contribs) confirmed 6 edits m This edit adds issues related to 1Password's licencing controversy Tag: Visual edit: Switched ← Older edit		Latest revision as of 13:05, 30 April 2026 edit undo Languagedivided (talk \| contribs) confirmed 6 edits m No change in content. Tag: Visual edit: Switched
Line 38:		Line 38:

	1Password, which uses an Okta instance, published a blog post disclosing an internal investigation of the breach.<ref>{{Cite web \|last=Canahuati \|first=Pedro \|date=2023-10-23 \|title=Okta Support System incident and 1Password \|url=https://blog.1password.com/okta-incident/ \|url-status=live \|archive-url=https://web.archive.org/web/20250905070945/https://blog.1password.com/okta-incident/ \|archive-date=2025-09-05 \|access-date=2025-09-05 \|work=1Password Blog}}</ref> According to their disclosure, the attackers' actions triggered an email to a member of the IT team who acted swiftly to contain the breach. The company reported that no user data was exfiltrated or decrypted.<ref>{{Cite web \|date=2023-10-27 \|title=Security incident report \|url=https://blog.1password.com/files/okta-incident/okta-incident-report.pdf \|archive-url=https://web.archive.org/web/20250920201057if_/https://blog.1password.com/files/okta-incident/okta-incident-report.pdf \|archive-date=2025-09-20 \|access-date=2026-01-23 \|website=1Password Blog}}</ref>		1Password, which uses an Okta instance, published a blog post disclosing an internal investigation of the breach.<ref>{{Cite web \|last=Canahuati \|first=Pedro \|date=2023-10-23 \|title=Okta Support System incident and 1Password \|url=https://blog.1password.com/okta-incident/ \|url-status=live \|archive-url=https://web.archive.org/web/20250905070945/https://blog.1password.com/okta-incident/ \|archive-date=2025-09-05 \|access-date=2025-09-05 \|work=1Password Blog}}</ref> According to their disclosure, the attackers' actions triggered an email to a member of the IT team who acted swiftly to contain the breach. The company reported that no user data was exfiltrated or decrypted.<ref>{{Cite web \|date=2023-10-27 \|title=Security incident report \|url=https://blog.1password.com/files/okta-incident/okta-incident-report.pdf \|archive-url=https://web.archive.org/web/20250920201057if_/https://blog.1password.com/files/okta-incident/okta-incident-report.pdf \|archive-date=2025-09-20 \|access-date=2026-01-23 \|website=1Password Blog}}</ref>


	===1Password License Controversy===		===1Password License Controversy===