try using harden-runner in doc as code#502
Closed
srinivasugithub wants to merge 1 commit into
Closed
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //src:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
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.
Description
Add security hardening step to GitHub workflows
This PR adds the step-security/harden-runner@v2.18.0 action to 6 GitHub workflows to improve the security posture of the Eclipse SCORE project. The hardening runner monitors and audits egress (outbound) network traffic from CI/CD jobs, helping to detect and prevent unauthorized or suspicious network activity.
Modified workflows:
consumer_test.yml
link_check.yml
lint.yml
renovate.yml
test.yml
test_links.yml
Key implementation details:
Conditional execution: Only runs when github.repository_owner == 'eclipse-score' (does not affect forks)
Egress policy set to audit (non-blocking, monitoring mode)
Positioned as the first step in each job for maximum effectiveness
Impact Analysis
This change does not violate any tool requirements and is covered by existing tool requirements
This change does not violate any design decisions
Otherwise I have created a ticket for new tool qualification
Rationale: This is a security enhancement that adds monitoring without modifying workflow behavior. No new tools or dependencies are introduced that would violate existing requirements.
✅ Checklist
Added/updated documentation for new or changed features
(Documentation: Changes are self-contained in workflow definitions with descriptive step name)
Added/updated tests to cover the changes
(Not applicable: Workflow changes; no unit tests needed)
Followed project coding standards and guidelines
(Consistent YAML formatting and follows GitHub Actions best practices)