[discussion] Add harden-runner (audit mode) to release job, ahead of signing pipeline restoration - #13
Draft
mohitbansal-webflow wants to merge 1 commit into
Draft
Conversation
Allowlist step-security/harden-runner and wire it into publish-source-release as an audit-only first step, ahead of the pending cosign/SBOM/notarization pipeline restoration that will bring real signing credentials into this job. Scoped to this one job only; see .github/action-allowlist.txt for the rationale.
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
1 participant
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.
Per
ACTION_PIN_POLICY.md's "ask first" guidance — requesting an exception to addstep-security/harden-runnerto the allowlist.What: Egress-audit visibility (never blocking) on
publish-source-release, the one job here holding acontents: writetoken behind an environment gate.Why now, not later:
release.yml's header notes the cosign/SBOM/attestation pipeline is pending restoration (blocked on macOS notarization). That pipeline will introduce real secrets — Apple signing/notarization credentials — into this exact job. Wiring in audit-mode monitoring now means it's already in place and has already accumulated baseline data by the time those credentials land, instead of being a rushed addition alongside the signing work itself.Why audit, not block: Block mode requires a maintained egress allowlist; flipping it on before we know the signing pipeline's real network footprint risks breaking a release on a missed domain. Audit-only, at least for now, changes nothing functionally — pure observability.
Why scoped to one job:
harden-runnerruns a privileged eBPF-based agent, not a passive action.lint/test/build/codeql/vuln-scan/scorecardnever hold a secret worth watching — adding it there is attack surface and an external-service dependency for no offsetting benefit.Note: free tier (public repo, GitHub-hosted runners) covers audit mode with no ambiguity. If we ever consider
egress-policy: block, that tier question should be reconfirmed directly with StepSecurity before committing — I found conflicting info on whether block mode is free vs. Enterprise-gated and don't want to assert either way.cc @webflow/infrastructure-security