3 ms·
This was a relatively recent (last couple yars) change, I’m guessing in part driven by pressure from their new enterprise sales push, due to the more vigilant r
by Terretta 9y ago
This was a relatively recent (last couple yars) change, I’m guessing in part driven by pressure from their new enterprise sales push, due to the more vigilant regulated enterprises in US and enterprises in EU simply unable to purchase services due to Google’s data access and use being so pervasive it violated regulations.
It is not clear to me from papers up through, say, 2016, whether you’ve achieved a guaranteed (compliant by technical architecture rather than by policy) level of access and data separation. Direct conversations had also made it clear it was not yet achieved.
You mentioned GDPR which indeed should require you to have to do the right thing soon, but it allows policy vs. technical controls. Bad actors don’t care about your policy, and good actors make inadvertent errors.
I’d like to know if/how the tech under the hood has changed o support the last couple years’ contract changes and upcoming EU compliance.
If anyone can point me to more recent papers or talks that evidence how it’s now impossible for, say, even a motivated bad actor in support or bad actor in SRE teams to violate data policy, I’d appreciate it.
Even if you can only talk to me off he record, I’d appreciate it.
- eitally 9y agoIf you are under contract & NDA with us, you can get more detailed information. I'm not willing to speak more, even off the record.
- Terretta 9y agoPrior job, we were. You guys were honest, not ready for our level. About right amount of time’s passed, helpful to learn progress? I’m at new job, still interested. At this bank I don’t have paper with you, we’d have to do that. Mail in Profile.