GitLab Secrets Manager: Govern secrets like your code
Oct 15, 2026Mark Settle

Summary
This post announces the general availability of GitLab Secrets Manager, built on OpenBao. It details how the manager scopes build-time secrets to individual jobs using project, branch, and environment context, exposing secrets via temporary files and masking them in logs. It highlights the ability to revoke and trace exposed credentials, the integration with GitLab's permission model for governing access, and its support for runtime tools like Kubernetes (via ESO), Terraform, and Vault CLIs. The post also explains how Secrets Manager fits into GitLab's supply chain controls and provides guidance on getting started, including trial options and installation for self-managed instances.
More from the GitLab Secrets Manager trail
- GitLab Secrets Manager adds ESO, Terraform, API support
- Manage CI/CD credentials with GitLab Secrets Manager
- A leaked personal access token shouldn't expose every project its owner can reach. Fine-grained PATs scope each token’s permissions to the job.
- Solving complex challenges with GitLab Duo Workflow
- How to scan a full commit history to detect sensitive secrets