Conversation

Notices

1. Quad 🌸 (quad@weeaboo.space)'s status on Thursday, 30-Dec-2021 18:57:22 UTC Quad 🌸
   is it really a breach if there was nothing to breach through though?
   • Santa Claes 🇸🇪🇭🇰🎅 likes this.
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Thursday, 30-Dec-2021 18:57:40 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to
     @quad Apart from the headline it looks like they're open about having messed up
   • Quad 🌸 (quad@weeaboo.space)'s status on Thursday, 30-Dec-2021 18:57:41 UTC Quad 🌸

     in reply to
     We live in a world where "Breach" no longer means they were hacked or social engineered. Instead it's a marketing word to blame hackers because the company doesn't want to admit incompetence
   • Quad 🌸 (quad@weeaboo.space)'s status on Thursday, 30-Dec-2021 18:57:41 UTC Quad 🌸

     in reply to
     I guess it /technically/ is a breach of security. They just conveniently ommit that it's a breach of security caused by their own employees, and hopes everyone will assume it refers to hacker
   • Kumicota :euphohug: (kumicota@weeaboo.space)'s status on Thursday, 30-Dec-2021 19:43:47 UTC Kumicota :euphohug:

     in reply to

     @quad I don’t know a lot about S3 but if they can’t be sure if a third-party had access in the past to the bucket, I would classify as a “potential breach” but not as a breach

     Santa Claes 🇸🇪🇭🇰🎅 likes this.
   • Quad 🌸 (quad@weeaboo.space)'s status on Thursday, 30-Dec-2021 19:43:47 UTC Quad 🌸

     in reply to

     • Santa Claes 🇸🇪🇭🇰🎅
     @clacke I'm fairly certain that's because these findings were published by others. I'm thinking more of the typical press release.
     
     And the abuse of the word "breach" for every situation. I can't remember hearing any other alternative like "Security Fault" or "Security Issue" in quite a while
     Santa Claes 🇸🇪🇭🇰🎅 likes this.