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 two new criteria #35

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

added two new criteria #35

wants to merge 9 commits into from

Conversation

SecurityCRob
Copy link
Contributor

add osps-53 & osps-54 per convo with eknight

added new criteria "Releases are Signed" as OSPS-53

Signed-off-by: CRob <[email protected]>
added new criteria for SAST scanning OSPS-54

Signed-off-by: CRob <[email protected]>
@SecurityCRob SecurityCRob added documentation Improvements or additions to documentation enhancement New feature or request labels Oct 18, 2024
@@ -720,6 +720,55 @@ criteria:
in a separate repository and fetched during
a specific well-documented pipeline step.
control_mappings: # TODO
security_insights_value: # TODO
scorecard_probe: # TODO
- id: OSPS-53

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I disagree with this one as worded fairly strongly.

I would reword it "cryptographically attested" -- We've seen multiple issues with just signing a piece of software.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mlieberman85 If the desire is for more than signing— should we split this into Lv2 signature, and Lv3 for more complete attestation?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's reasonable. I think we should also be clear what just blanket "signing" should be interpreted as. Since people sign a lot of stuff for a lot of reasons, which is why folks have been moving to attestations so it's clear what the intent of the signing is.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the first level should be plain signing with published singer identities. It's way easier to implement plain signing and it gets us initial integrity guarantees.

baseline.yaml Outdated Show resolved Hide resolved
baseline.yaml Outdated Show resolved Hide resolved
baseline.yaml Outdated Show resolved Hide resolved
SecurityCRob and others added 2 commits October 18, 2024 15:33
Co-authored-by: Tom Hennen <[email protected]>
Signed-off-by: CRob <[email protected]>
Co-authored-by: Tom Hennen <[email protected]>
Signed-off-by: CRob <[email protected]>
baseline.yaml Outdated Show resolved Hide resolved
SecurityCRob and others added 2 commits November 7, 2024 16:26
Co-authored-by: Eddie Knight <[email protected]>
Signed-off-by: CRob <[email protected]>
Co-authored-by: Puerco <[email protected]>
Signed-off-by: CRob <[email protected]>
security_insights_value: # TODO
scorecard_probe:
- releasesAreSigned
- id: OSPS-54
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest splitting this out into a separate PR, since it seems less controversial than the other one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants