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

[StepSecurity] Apply security best practices (#230) #231

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

step-security-bot
Copy link

Summary

This pull request is created by Secure Repo at the request of @fperezel. Please merge the Pull Request to incorporate the requested changes. Please tag @fperezel on your message if you have any questions related to the PR. You can also engage with the StepSecurity team by tagging @step-security-bot.

Security Fixes

Pinned Dependencies

GitHub Action tags and Docker tags are mutatble. This poses a security risk. GitHub's Security Hardening guide recommends pinning actions to full length commit.

Keeping your actions up to date with Dependabot

With Dependabot version updates, when Dependabot identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. This is recommended by GitHub as well as The Open Source Security Foundation (OpenSSF).

Feedback

For bug reports, feature requests, and general feedback; please create an issue in step-security/secure-repo. To create such PRs, please visit https://app.stepsecurity.io/securerepo.

Signed-off-by: StepSecurity Bot [email protected]

@@ -112,7 +112,7 @@ jobs:

- name: Check license vetting status (and ask for review if requested)
id: check-license-vetting
uses: eclipse/dash-licenses/.github/actions/maven-license-check-action@master
uses: eclipse/dash-licenses/.github/actions/maven-license-check-action@f12cb1ced8fb5d92acdd9a4ad5930075a94cc675 # master
Copy link

Choose a reason for hiding this comment

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

I would not use a fixed hash for this action.
It is an action hosted within the repo itself. When you change the workflow, you would have to change this workflow as well, referencing the new version of it (cant be done in the same commit btw).

Also when someone is able to manipulate the tags of this repo, this should be our least concern.

Copy link

Choose a reason for hiding this comment

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

Thanks, for the feedback, it sounds reasonable. I am updating and commenting as an exception

@ghost ghost force-pushed the stepsecurity_remediation_1682609380 branch from 859e090 to 5c9f008 Compare April 28, 2023 15:02
@waynebeaton
Copy link
Collaborator

@netomi are you content with the updates? Shall I merge?

@netomi
Copy link

netomi commented May 3, 2023

Looks good to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants