/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

1Password detected suspicious activity on its Okta instance for managing employee-facing apps but “found no compromise of user data or other sensitive systems”

1Password CTO says investigation found no compromise of user data or sensitive systems.

Ars Technica Dan Goodin

Discussion

  • @AnnemarieBridy@mastodon … Annemarie Bridy on mastodon
    FFS, it hasn't even been six months since I ditched LastPass to move to 1Password.  —  1Password detects “suspicious activity” in its internal Okta account |  Ars Technica https://arstechnica.com/...
  • @insiderphd Katie Paxton-Fear on x
    i can't believe i pay $5 a month for a password manager and they can't shell out the same for malware bytes
  • @c7five Nick Percoco on x
    Product placements in incident reports help reduce the cost of the investigation...
  • @jfslowik Joe Słowik on x
    OK, the quoted post appears to be picking up steam.... gentle reminder that yeah this is a “WTF???” observation but I bet the org is hardly alone in having to “wing it” in certain situations due to failures to account for certain scenarios in IR events.
  • @attrc Andrew Case on x
    The malwarebytes scan is enough to make everyone run from @1Password and never look back
  • @jfslowik Joe Słowik on x
    I'm sorry, what??? [image]
  • @syndrowm @syndrowm on x
    Good stuff from the @1Password incident response. Every incident is an opportunity to improve. https://blog.1password.com/... [image]
  • @xillwillx @xillwillx on x
    https://blog.1password.com/... [image]
  • @dagrz Daniel Grzelak on x
    The @1Password incident report resulting from the Okta breach is really good. The level of transparency is something to aspire to, espcially about the things not known. Usually we get “no evidence to suggest” instead. https://blog.1password.com/...
  • @dcuthbert Daniel Cuthbert on x
    “and was scanned with the free version of Malwarebytes, which reported no findings” hmmm.... https://blog.1password.com/... [image]
  • @citcsmobile James Clark on x
    Holy shit... https://1password.com/'s security response is “We ran the free version of malwarebytes” I don't even know what to say... https://blog.1password.com/... [image]
  • @ejcx_ Evan J on x
    This Okta breach is notable because BeyondTrust, Cloudflare, and 1Password all detected this before Okta did. How though? It looks like the threat actor may have been triggering Okta emails that tipped off the victims. Maybe we'll hear from more? https://blog.1password.com/... [i…
  • @r0wdy_ Ham Elliot on x
    If you use okta, you need to be monitoring for idp addition/modification events. Also most actions in okta are given a risk score based on criteria like device, ip, and location compared against previous actions. Flag high risk tagged events, like admin dashboard access, idp, etc
  • @kn0wmadic Ryan on x
    I don't think people really understand how single threaded this entire ecosystem is. Okta -> 1Password is a murderous pivot if successful.
  • @mattjay Matt Johansen on x
    Well shit. 1Password disclosed breach tied to Okta incident. https://blog.1password.com/...
  • @1password @1password on x
    We detected suspicious activity on our Okta instance but confirmed no user data was accessed. Pedro Canahuati, our CTO, provides more information in this blog post https://blog.1password.com/..., which includes our internal Okta Incident Report for additional details.
  • r/1Password r on reddit
    1Password detects “suspicious activity” in its internal Okta account