Trust But Verify: Security and Privacy Considerations for Remote Build Execution (RBE) Platforms
For organizations using Bazel and RBE, your build graph is effectively a fingerprint of your product ecosystem and the engineering hierarchy behind it. Depending on the extent to which Bazel and monorepo usage is established within your organization, your Bazel build graph may be composed of interdependent (configured) targets, actions, and artifacts spanning every single dependency, service and test that exists within your codebase.
Other highly valuable sources of metadata related to your codebase that Bazel can produce are JSON trace profiles, effectively structured recordings of what happened during a build and how long it took.
Combined, and observed in time, those two data sources offer insights into release cadence, acquisition targets, engineering headcount, and products potentially being shipped before you are actually ready to ship them. In other words, they are some of the most sensitive data sources an engineering organization produces, and they are routinely treated as exhaust.
