- Security - GitLab
At GitLab, we know how much security, privacy and accessibility matters to our customers and stakeholders Learn more about GitLab security compliance controls
- GitLab Hardening Recommendations | GitLab Docs
CI CD is a core component of GitLab, and while application of security principles are based upon needs, there are several things you can do to make your CI CD more secure
- GitLab Trust Center | Powered by SafeBase
At GitLab, we're committed to Information Security It is GitLab’s mission to make it so that everyone can contribute, and it's our Security Division's mission to enable everyone to innovate and succeed on a safe, secure, and trusted DevSecOps platform
- Security dashboards | GitLab Docs
Use security dashboards to assess the security posture of your applications GitLab provides you with a collection of metrics, ratings, and charts for the vulnerabilities detected by the security scanners run on your project
- Secure GitLab | GitLab Docs
GitLab Self-Managed customers and administrators are responsible for the security of their underlying hosts, and for keeping GitLab itself up to date It is important to regularly patch GitLab, patch your operating system and its software, and harden your hosts in accordance with vendor guidance
- GitLab introduces new CIS Benchmark for improved security
GitLab and the Center for Internet Security® (CIS®) created the just-published CIS GitLab Benchmark, which includes more than 125 recommended secure configuration guidelines for hardening GitLab installations
- Security - Hardening Your GitLab Instance
We designed this Hardening page to serve as a starting point for those interested in hardening a GitLab instance to help improve security
|