5 ms·

Yeah that's not "strong technical safeguards". Or good enough.

• lokar 3y ago
  They seemed pretty good at catching people
  • dataflow 3y ago
    I hope you never have control over people's data. Being good at catching people after the fact is not the same as being good about securing the data in the first place. Seriously, if you had important information that was leaked, it's kind of irrelevant whether the person who leaked it got fired. You still face the consequences either way.
    • Terretta 3y ago
      > Being good at catching people after the fact is not the same as being good about securing the data in the first place. True, only one of these is future proof, and maybe not the one you think.
• jeffbee 3y ago
  Yeah that is not even remotely good enough. Processes running under the authority of individual engineers cannot have access to user data. Processes with access to user data can only run reviewed and committed code with verified production builds. There can't be user data just laying around on hosts were unix superuser permissions can be used to access it.
  • lokar 3y ago
    Nothing is laying around. Everything is remote API calls authenticated as the engineer running the code.