GitLab CI_JOB_TOKEN allowlist: control cross-project access
CI_JOB_TOKEN works only while a job runs and reaches only its own project by default. How the allowlist works and which settings to leave on.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
CI_JOB_TOKEN works only while a job runs and reaches only its own project by default. How the allowlist works and which settings to leave on.
Why the default GITHUB_TOKEN should be read-only, how to grant write access per job with the permissions key, and what to check in older workflows.
Push protection blocks secrets before they land, but anyone with write access can bypass it by default. How to set bypass reasons and delegated review.
Maintainers can enable private vulnerability reporting in a few clicks so researchers have a private channel. Steps and the custom form option.
How environment protection rules gate production deploys in GitHub Actions: reviewers, self-review block, wait timers, branch limits and plan caveats.
Branch protection allows one rule per branch. Rulesets layer, toggle without deleting, and are visible to readers. A short guide to choosing between them.
How script injection works in GitHub Actions run steps and the fix GitHub recommends: pass untrusted values through an environment variable, not inline.
How OIDC lets a GitHub Actions job get a short-lived cloud token instead of a stored key, what the subject claim does, and how to scope the trust.
Use OpenID Connect so GitHub Actions gets short-lived AWS credentials. See the setup, the permissions needed and the trust policy condition to include.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.