[StepSecurity] Apply security best practices - #3
Open
stepsecurity-app[bot] wants to merge 1 commit into
Open
Conversation
Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This pull request has been generated by StepSecurity as part of your enterprise subscription to ensure compliance with recommended security best practices. Please review and merge the pull request to apply these security enhancements.
Security Fixes
Harden Runner
Harden-Runner is an open-source security agent for the GitHub-hosted runner to prevent software supply chain attacks. It prevents exfiltration of credentials, detects tampering of source code during build, and enables running jobs without sudo access.
Feedback
For bug reports, feature requests, and general feedback; please create an issue in step-security/secure-repo or contact us via our website.
Note
Low Risk
Workflow-only hardening with no application or build logic changes; CI will fail if the Step Security API secret is missing or misconfigured.
Overview
Adds a Harden the runner step at the start of the CI
testjob usingstep-security/harden-runner(pinned to v2.20.0), before checkout and the existing JDK/sbt steps.The step enables policy store, sets egress-policy to audit, and passes
STEP_SECURITY_API_KEYfrom repository secrets so outbound network activity on the runner can be monitored per StepSecurity guidance.Reviewed by Cursor Bugbot for commit 1e0d1c4. Bugbot is set up for automated code reviews on this repo. Configure here.