> For other services to leak their data, all it takes is for one employee to do something they shouldn't.
This is not true for Google, at least. I know because I work at Google.
So I wonder how accurate your knowledge of Meta, Microsoft etc is.
This is not true for Google, at least. I know because I work at Google.
So I wonder how accurate your knowledge of Meta, Microsoft etc is.
You can also audit that the binaries don’t leak any data in, say, debug logs, which is definitely possible on GCP/Borg. PCC nodes are “cryptographically airtight.”
Airgapped is based on top of Kubernetes, and it's using mostly off the shelf components for networking and compute.
GCP is based on top of Borg, using custom networking and computer hardware (though manufacturers by a partner). As a note, not only is access without a support token alertable (goes to your skip level), there's a distinct level of "I'm not even going to build the tool to enable this". Which makes being in support a b**.
If you want access to something, it's significantly easier to just ask the customer to do it themselves.
Disc: Former TSE for Advanced Support.
But Google does a lot of work to protect against insider threats, because everyone understands that in an organization of this size there will always be bad apples, spies, etc. Google's systems are designed to protect customer data from malicious employees using technical measures; it's much more than just "if we catch you, you're fired" as was asserted upthread.