4 ms·
This document has been a long-time coming, and finally lets us talk about the encryption we perform on your behalf when transiting outside our physical boundari
by boulos 9y ago
This document has been a long-time coming, and finally lets us talk about the encryption we perform on your behalf when transiting outside our physical boundaries. There are lots of paths, but I think the diagram [1] captures it well.
Edit: Of particular note is that if you have a VM in say us-central1 talking to another of your VMs in us-east1, we encrypt that traffic across regions (even though it's riding our backbone).
Disclosure: I work on Google Cloud (and even sort of contributed to this).
[1] https://cloud.google.com/images/security/whitepaper-transit-01.svg https://cloud.google.com/images/security/whitepaper-transit-...
- foobarbazetc 9y agoAny chance you guys will support dual RSA+ECC custom certs on the HTTPS load balancer at some point? :)
- boulos 9y agoI've pinged the PM to ask. Send me an email or check back here :).
- foobarbazetc 9y agoHoly moly, it’s actually possible right now! It wasn’t there before, but you can assign multiple certs to a front end now, and it works as you expect (tested with SSLLabs.com). Great, thanks! :)
- CPAhem 9y agoWhen are you going to support end-to-end encryption for consumer apps? We use Syncdocs https://syncdocs.com https://syncdocs.com to encrypt Google Drive, but it would be better to use an entirely Google soultion.
- rakoo 9y agoI believe this diagram (http://www.theblaze.com/wp-content/uploads/2014/06/NSA-brief-slide.png http://www.theblaze.com/wp-content/uploads/2014/06/NSA-brief...) is even more simple to understand