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

added criteria for signing and verifying assets #91

Merged
merged 1 commit into from
Dec 5, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
49 changes: 49 additions & 0 deletions baseline.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -334,6 +334,30 @@ criteria:
scorecard_probe:
- # TODO, this might be possible if paired with SI to find the release location

- id: OSPS-BR-08
maturity_level: 2
category: Build & Release
criteria: |
All released software assets MUST be signed
or accounted for in a signed manifest
including each asset's cryptographic hashes.
objective: |
Provide users with a mechanism to verify the
authenticity and integrity of released
software assets, reducing the risk of
tampering or unauthorized modifications.
implementation: |
Sign all released software assets at build
time with a cryptographic signature or
attestations, such as GPG or PGP signature,
Sigstore signatures, SLSA provenance, or SLSA
VSAs. Include the cryptographic hashes of
each asset in a signed manifest or
metadata file.
control_mappings: # TODO
security_insights_value: # TODO
scorecard_probe: # TODO

- id: OSPS-DO-01
maturity_level: 1
category: Documentation
Expand Down Expand Up @@ -600,6 +624,31 @@ criteria:
control_mappings: # TODO
security_insights_value: # TODO

- id: OSPS-DO-12
maturity_level: 2
category: Documentation
criteria: |
The project documentation MUST contain
instructions to verify the integrity
and authenticity of the release assets,
including the expected identity of the person
or process authoring the software release.
objective: |
Enable users to verify the authenticity and
integrity of the project's released software
assets, reducing the risk of using tampered
or unauthorized versions of the software.
implementation: |
Instructions in the project should contain
information about the technology used, the
commands to run, and the expected output. The
expected identity may be in the form of key
IDs used to sign, issuer and identity from a
sigstore certificate, or other similar forms.
control_mappings: # TODO
security_insights_value: # TODO
scorecard_probe: # TODO

- id: OSPS-LE-01
maturity_level: 2
category: Legal
Expand Down
Loading