Skip to content

[StepSecurity] Apply security best practices#678

Merged
starksm64 merged 2 commits intojakartaee:mainfrom
step-security-bot:stepsecurity_remediation_1686059924
Nov 30, 2023
Merged

[StepSecurity] Apply security best practices#678
starksm64 merged 2 commits intojakartaee:mainfrom
step-security-bot:stepsecurity_remediation_1686059924

Conversation

@step-security-bot
Copy link
Copy Markdown
Contributor

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

resolve: #677

Least Privileged GitHub Actions Token Permissions

The GITHUB_TOKEN is an automatically generated secret to make authenticated calls to the GitHub API. GitHub recommends setting minimum token permissions for the GITHUB_TOKEN.

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 bot@stepsecurity.io

resolve: jakartaee#677

Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
Copy link
Copy Markdown
Member

@Ladicek Ladicek left a comment

Choose a reason for hiding this comment

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

LGTM, though I'm not exactly a fan of pinning actions that come directly from GitHub. The security risk there seems fairly minimal to me. On the other hand, there's a comment with the specific version number, and apparently Dependabot will bump those actions automatically, so it seems fine. Will see if Dependabot will also automatically bump those comments...

@Ladicek
Copy link
Copy Markdown
Member

Ladicek commented Jun 7, 2023

LGTM, but a 2nd review would be nice.

Copy link
Copy Markdown
Contributor

@manovotn manovotn left a comment

Choose a reason for hiding this comment

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

LGTM but as same my other review (jakartaee/cdi-tck#473 (review)), the daily interval might prove irritating

@starksm64 starksm64 merged commit d9e8656 into jakartaee:main Nov 30, 2023
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.

Security Best Practices

5 participants