Improvement of OpenSSF Scorecard Score

[harshitasao]

Describe the feature

Is this a bug report or feature request?

• Feature Request

What should the feature do: Hi, I'm Harshita. I’m working with CNCF and the Google Open Source Security Team for the GSoC 2024 term. We are collaborating to enhance security practices across various CNCF projects. The goal is to improve security for all CNCF projects by both using OpenSSF Scorecards and implementing its security improvements.

After the opening of the scorecard action addition PR, I'm here to increase the final score by going over each check. I've listed all of the checks where work needs to be done, in order of its criticality. I plan to submit each PR for each fix. Please let me know what you think and for which ones a PR is welcome that I will submit it ASAP.

Current Score: 7.3

Scorecard report: https://scorecard.dev/viewer/?uri=github.com/knative/serving

Here's a few checks we can work on to improve the project's security posture [ in order of its criticality ]:

• [ ] Token-Permissions: Score = 0

  • The issue here is that many workflows doesn’t have a top-level read-only permissions block like present in the other workflows. Scorecard is quite severe in this check: a single workflow without top-level permissions gets a 0/10 for the check.

• [ ] Vulnerabilities: Score = 7

  • After running the osv scanner locally, a significant amount of vulnerabilities in Go dependencies were found that need to be fixed.
  • May need to add an osv-scanner.toml to mark some of these as not impacting/ignored.
  • Open vulnerabilities are easily exploited by attackers and should be fixed as soon as possible.

• [ ] Signed-Releases: Score = 8

  • SLSA provenance needs to be added, which can be done using this, increasing the overall score to 10.

• [ ] Fuzzing: Score = 0

  • Integrating the project with OSS-Fuzz by following the instructions here. The most difficult one on the list, maintainers help, is highly appreciated. For example, helping in identifying the components where fuzz testing will be added.

• [X] Pinned-Dependencies: Score = 3

  • Github actions and go commands are not pinned by hash, which is resulting in a low score. But pinning go commands would introduce the risk of running outdated versions.
  • Pinning dependencies to a specific hash rather than allowing mutable versions or ranges of versions improves supply chain security.
  • PR: https://github.com/knative/serving/pull/15475

/cc @joycebrum @diogoteles08 @pnacht @nate-double-u

[harshitasao]

cc @davidhadas

[davidhadas]

Welcome @harshitasao

As for Fuzzing - see https://knative.dev/blog/events/fuzzing-audit-2023/ See also https://knative.dev/blog/events/security-audit-2023/

cc @evankanderson