Binary Authorization for Borg
cloud.google.com
Binary Authorization for Borg
1–10 of 60 posts
Re: Binary Authorization for Borg
#2Has anyone outside of Google implemented something similar in spirit to this for K8s or ECS? What was the threat model you were considering when you built it? Was it worth it?
Re: Binary Authorization for Borg
#3Has anyone outside of Google implemented something similar in spirit to this for K8s or ECS? What was the threat model you were considering when you built it? Was it worth it?
Kritis[0] is a K8s implementation of this that intends to block deployments of images that haven't been properly vetted beforehand, or has critical vulnerabilities, etc.
Whitepaper: https://github.com/grafeas/kritis/blob/master/docs/binary-au...
Re: Binary Authorization for Borg
#4In case anyone else wonders what 'borg' is:
"Our infrastructure is containerized, using a cluster management system called Borg."
I was hoping they had some predictable, indexed build for borg backup[1].
Re: Binary Authorization for Borg
#5I led the portion of this project on Borg itself.
Security team did most of the security infrastructure, and coordination among almost every large infrastructure system team inside TI.
I'll be waiting for them to answer any questions. :)
Re: Binary Authorization for Borg
#6> We want to have confidence that the administrators who run the systems that access user data cannot abuse their powers.
So "Binary Authorization for Borg" is a defense against getting Snowdened.
Re: Binary Authorization for Borg
#7On a related note, we have built an E2E-verified, tamper-evident CI/CD pipeline for the Datadog Agent integrations [1]: the Agent will trust and install only integrations that correspond to source code that have signed by our developers. If there is an attack anywhere between our developers and end-users, it will be caught.
Unlike Binary Authorization for Borg, our security guarantees are publicly verifiable.
[1] https://www.datadoghq.com/blog/engineering/secure-publicatio...
Re: Binary Authorization for Borg
#8Fascinating, the part we may get the most out of is "Adopting similar controls in your organization" - not just Google For Everyone Else.
Re: Binary Authorization for Borg
#9> We want to have confidence that the administrators who run the systems that access user data cannot abuse their powers. So "Binary Authorization for Borg" is a defense against getting Snowdened.
It's more a defense against getting NSA'd (via the specific threat model of an attacker secretly replacing a security service with an implementation that looks very similar but is much easier to crack).
Re: Binary Authorization for Borg
#10I led the portion of this project on Borg itself. Security team did most of the security infrastructure, and coordination among almost every large infrastructure system team inside TI. I'll be waiting for them to answer any questions. :)
I've seen references to gVisor being used 'in production' for google app engine && cloud run and so forth.
Scanning through recent commits && the github repo this is clearly not the case - there are way too many outstanding issues and outright missing support for various things. Is this another project where it was written in a different language or something and then ported out?
Can you clarify?