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

SLSA 3 compliance #1164

Open
4 tasks
nyrahul opened this issue Mar 15, 2023 · 0 comments
Open
4 tasks

SLSA 3 compliance #1164

nyrahul opened this issue Mar 15, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@nyrahul
Copy link
Contributor

nyrahul commented Mar 15, 2023

Feature Request

Proposed by Google, SLSA (Supply Chain Levels for Software Artifacts) is a security framework and a check-list of standards and controls to prevent tampering, improve software supply chain integrity, and secure software packages and infrastructure in projects, businesses or enterprises. It is not a single tool, but a step-by-step outline to prevent artifacts from being tampered with and tampered artifacts from being used, and at the higher levels, to strengthen the platforms that make up a supply chain. Manufacturers follow the SLSA guidelines to safeguard their software, and users make decisions based on the security status of software packages.

KubeArmor is a security engine, thus it is imperative that it follows all the best practices of the supply chain methods. KubeArmor has already begun the journey by ensuring that the generated container images are signed and can be verified using cosign.

Tasks Involved

  • Understand SLSA 3 requirements
  • Fulfill the checklist for SLSA 3 requirement. Identify the gaps
  • Create issues to handle the gaps
  • Track to closure the gaps and update the checklist.

Reference
Check how KubeEdge got the SLSA 3 compliance handled and follow a similar strategy.

@nyrahul nyrahul added the enhancement New feature or request label Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

1 participant