Hope this isn’t a repeated submission. Funny how they’re trying to deflect blame after they tried to change the EULA post breach.

  • FiveMacs@lemmy.ca
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    5
    ·
    11 months ago

    And it’s your fault you have access to them. Stop doing bad things and keep your information secure.

    • Alien Nathan Edward@lemm.ee
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      5
      ·
      11 months ago

      you clearly have no familiarity with the principles of information security. 23andMe failed to follow a basic principle: defense in depth. The system should be designed such that compromises are limited in scope and cannot be leveraged into a greater scope. Password breaches are going to happen. They happen every day, on every system on the internet. They happen to weak passwords, reused passwords and strong passwords. They’re so common that if you don’t design your system assuming the occasional user account will be compromised then you’re completely ignoring a threat vector, which is on you as a designer. 23andMe didn’t force 2 factor auth (https://techcrunch.com/2023/11/07/23andme-ancestry-myheritage-two-factor-by-default/) and they made it so every account had access to information beyond what that account could control. These are two design decisions that enabled this attack to succeed, and then escalate.