Credential leaks often start with developers improvising secret storage, leading to vulnerabilities. GitLab Secrets Manager, now in public beta, aims to solve this by providing a secure and integrated solution. This manager keeps secrets within the GitLab platform, accessible to jobs needing them. Developers can define secrets in .gitlab-ci.yml, using the secrets: keyword. The access control uses the established group and project structure. This approach eliminates the need for separate systems, simplifying access management. The secret's scope can be defined using job attributes, minimizing the impact of a breach. Audit logs within GitLab track secret usage, enabling efficient investigation. This feature is in public beta for Premium and Ultimate users on GitLab.com and self-managed deployments. It's designed to streamline secret management and reduce the risk associated with compromised credentials. The Secrets Manager will be a paid feature post-beta. Feedback is encouraged to help shape its final form.