Who can read my GitLab CI job logs and artifacts?
GitLab's project-based pipeline visibility setting decides who sees job logs and artifacts. Clear it to limit public project logs to Reporters and above.
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.
GitLab's project-based pipeline visibility setting decides who sees job logs and artifacts. Clear it to limit public project logs to Reporters and above.
Use instance runners for similar general jobs and project runners for jobs that hold credentials, such as deploys. How GitLab's three runner scopes differ.
GitLab IaC scanning uses KICS to check Terraform, Kubernetes, CloudFormation and more in CI. See supported formats, setup steps and known limits.
Prefer include:project over include:remote for shared GitLab CI config, point it at a fixed ref you control, and review shared file changes like code.
A map of GitLab's built-in scanners: SAST, secrets, dependency, container, IaC and DAST, with what each looks at and the tier notes we could confirm.
Adding a file to .gitignore only stops future tracking. A secret already committed stays in history until you rotate it and, if needed, rewrite the repo.
Vigilant mode marks every commit and tag under your name with a verification status, so an unsigned commit that claims to be you shows as Unverified.
Default to the built-in GITHUB_TOKEN with minimum permissions. Use a GitHub App for other repositories. Use a PAT only when nothing else works.
Repository secrets suit one repo, organization secrets share across repos, and environment secrets can sit behind required reviewers. Pick by blast radius.
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.