Dev to main - Harden GitHub Actions workflows: AppSec Findings - #176
Closed
sankettangade wants to merge 1 commit into
Closed
Dev to main - Harden GitHub Actions workflows: AppSec Findings#176sankettangade wants to merge 1 commit into
sankettangade wants to merge 1 commit into
Conversation
- Move untrusted ${{ }} into env vars to prevent script injection
- Pin all actions to commit SHAs (no version bumps)
- Set top-level permissions: {} with minimal job-level grants
- Add concurrency groups and job names
- Pin semgrep container image by digest
sankettangade
added
the
Release Not Needed
sankettangade
changed the title
GarrettBeatty
approved these changes
Jul 2, 2026
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
2 participants
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
Hardening our GitHub Actions workflows with zizmor — same change already merged to
dev, brought tomainvia a clean cherry-pick (the rest ofdevisn't ready formainyet). Same approach as aws-sdk-net-staging#1375.Changes
${{ }}values intoenv:vars to prevent script injectionpermissions: {}with minimal per-job grantsNotes
Workflow files only — no behavior changes. The release/sync checkouts intentionally keep persisted credentials (they push afterwards). Verified clean with zizmor; only expected
artipackedfindings remain on those push steps.