Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TODO: Need mitigation description for "Use a compromised build tool" threat #1184

Open
lehors opened this issue Oct 9, 2024 · 2 comments
Open
Assignees
Labels

Comments

@lehors
Copy link
Member

lehors commented Oct 9, 2024

No description provided.

@lehors lehors added the slsa 1.1 label Oct 9, 2024
@TomHennen
Copy link
Contributor

I think a reasonable mitigation here is something like "Treat build tooling, including OS images, as any other software to be verified prior to use (as described in (G)). This will allow the build platform to detect any modified binaries."

Once the attested build environments track is finalized we can update this mitigation to reference it specifically. CC @marcelamelara

Separately, I'm wondering if this is a reason to move the mitigations from (G) (discussed in #1190, #1191) to (I) since 'usage' is more clearly aligned with this risk than with 'distribution channel'. (Or maybe we can just tweak the mitigation language here to discuss).

@TomHennen TomHennen self-assigned this Oct 15, 2024
@marcelamelara
Copy link
Contributor

@TomHennen Definitely happy to help with this as well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🆕 New
Development

No branches or pull requests

3 participants