-
Notifications
You must be signed in to change notification settings - Fork 219
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 Requirements for Automation #478
Comments
SOURCE Requirements for v .1 specification (FIXED) SLSA Source Requirements JSON code (Fixed)
|
High Level SLSA Requirements SLSA High Level requirements JSON file
|
SLSA Build Requirements.(Fixed) SLSA Build Requirements JSON (Fixed)
|
SLSA Provenance Requirements SLSA Mapping - Provenance JSON
|
SLSA Mapping - CONTENTS of Provenance SLSA Mapping - Contents of Provenance.csv SLSA Mapping - Contents of Provenance JSON
|
SLSA Mapping - COMMON Requirements SLSA Mapping - Common Requirements.csv SLSA Mapping - COMMON Requirements JSON
|
Is this what we need to move forward with the OSCAL implementation?? |
Perhaps. I need to read up on the OSCAL spec. The spec itself is a little different. This is useful generally, probably just want to change some of this to true/false or yes, no, optional. Let me take a closer look. |
To clarify, is this about verifying that a system meets the SLSA requirements as per #508? Would this essentially be the "evidence of security claims" from the SLSA v1.0 proposal? |
I think this issue was made obsolete by the build system compliance program. Feel free to reopen. |
Problem: To assist with automation (devops/compliance), need to generate a machine readable format for SLSA Requirements.
Propose:
Additional Info: Discussed during 9/6/22 positioning meeting
The text was updated successfully, but these errors were encountered: