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. To learn more, visit the security section of our handbook.
GitLab's AI Transparency Center can be found here.
GitLab has published its FY25 Penetration Test Executive Summary report. The report covers both GitLab.com and GitLab Dedicated. Please download the report from the trust center at your convenience.
GitLab has updated the following documents for both GitLab.com and GitLab Dedicated with Japanese, German, and French translations:
- Securing Customer Data Report
- GitLab Technical Paper - Securing GitLab's Supply Chain
- CAIQ
- ISO Certificate
- ISO 27001 Summary Letter
GitLab is aware of a recently reported data breach at Sisense. GitLab does not currently use Sisense for GitLab.com, GitLab Dedicated, or GitLab self-hosted deployments.
GitLab is a former customer of Sisense and at the termination of our contract in March 2024, GitLab rotated secrets as part of our routine security operations. Out of an abundance of caution following the reported data breach, GitLab followed Sisense's recommended remediation measures on 2024-04-11.
We have taken additional measures to identify any unauthorized usage of Sisense related keys, tokens or credentials within GitLab and have not uncovered any suspicious activity to date.
Please reach out if you have any further questions.
The GitLab.com and GitLab Dedicated CAIQs have been updated to the latest version, 4.0.3. Please use the STAR Registry link on GitLab's Trust Center to view and download the latest version of the questionnaire.
GitLab has updated the ESG card for both GItLab.com and GitLab Dedicated! To learn more about how GitLab addresses Environmental, Social, and Governance concerns, please visit our trust center.
If you think you may have discovered a vulnerability, please send us a note.