search

bazel-contrib / SIG-rules-authors

Governance and admin for the rules authors Special Interest Group
https://bazel-contrib.github.io/SIG-rules-authors/
Apache License 2.0
30 stars 12 forks source link

Support supply-chain security (slsa) #13

Closed alexeagle closed 1 year ago

alexeagle commented 3 years ago

Someone would need to gather requirements on what data a tool like salsa needs for establishing provenance of binaries.

In theory an aspect could visit the build graph to collect these.

It also needs to interact with every package manager to know the origin of third-party library code/binaries.

This is a superset of the rules_license problem, to track metadata transitively through the graph.

If we had a recommendation for what rules authors ought to do, we could document that, provide verification tooling for this feature. We could supply "BCID level numbering". Maybe there's a test rule that can verify a binary has the following provenance.

jsharpe commented 3 years ago

For context: https://security.googleblog.com/2021/06/introducing-slsa-end-to-end-framework.html

aiuto commented 2 years ago

cc: @aiuto

alexeagle commented 2 years ago

My understanding is that Google is funding the slsa project, so we'd hope they can contribute resources to making the Bazel ecosystem support it.

alexeagle commented 1 year ago

I think we should just close this issue, since Tony is working on this problem in rules_license and there's nothing the rules authors SIG can act on right now, as far as I know.