[PAN-1885] Spike to evaluate hardened agents #8
Conversation
This file contains 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.
What type of PR is this? (check all applicable)
Description
Enable hardened github actions using Harden Runner.
Related Tickets & Documents
pantos-io/common#16
See policy recommendations at:
https://app.stepsecurity.io/github/pantos-io/common/actions/runs/9065096467?jobid=24904871700&tab=recommendations
QA Instructions
Check the audit information is collected and displayed as shown in https://github.com/step-security/harden-runner. The current egress policy has been defined using a bunch of runs from pantos-io/common#16
[optional] Are there any post deployment tasks we need to perform?
The egress policy for the sonar pipeline has not been set yet. We need a run from the main branch to get a recommendation for the egress policy.