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

Define "trusted control plane" #367

Closed
bobcatfish opened this issue Apr 15, 2022 · 3 comments
Closed

Define "trusted control plane" #367

bobcatfish opened this issue Apr 15, 2022 · 3 comments
Assignees
Labels
clarification Clarification of the spec, without changing meaning slsa 3 Applies to a SLSA 3 requirement

Comments

@bobcatfish
Copy link

Another phrase which occurs a few times in the SLSA requirements but is not clearly defined (or I haven't found the definition!) is trusted control plane.

It would be very useful to have this clearly defined in the SLSA terminology, especially how it could apply to different systems, for example this phrase would likely mean something different for GitHub Actions which is hosted and has complete control over the control plane vs. for something like Tekton where the trusted control plane depends on how Tekton is configured and also may include components such as Tasks

(More context available in SLSA + Tekton: Case Study - particularly the section around what trusted control plane could mean for Tekton - the doc is visible to anyone in mailing list [email protected] ).

@marcelamelara
Copy link
Contributor

+1 to resolving this for v1.0.

@kpk47
Copy link
Contributor

kpk47 commented Jan 19, 2023

This may have been addressed by #568.

@kpk47 kpk47 closed this as completed Mar 20, 2023
@MarkLodato MarkLodato reopened this Mar 20, 2023
@MarkLodato
Copy link
Member

This can be further clarified because requirements.md says "trusted control plane" without linking to a definition. Simple solution is to link to the corresponding page in verifying build systems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Clarification of the spec, without changing meaning slsa 3 Applies to a SLSA 3 requirement
Projects
Status: Done
Development

No branches or pull requests

4 participants