is now in public beta!
Browse articles that include the security tag
Recent posts
Company
Support for TLS 1.0 and 1.1 discontinued on GitLab.com and GitLab API on 2018-12-15
TLS 1.2 is now required for all clients that connect to GitLab.com and our GitLab API.
Engineering
GitLab's HackerOne Bug Bounty Program is public today
With 200 reported vulnerabilities and $200,000 awarded already, our bug bounty program is now public and open for your contributions.
Engineering
GitLab Runner update required to use SAST in Auto DevOps
Make sure you upgrade GitLab Runner to 11.5+ to coninue using SAST in Auto DevOps.
Engineering
It's raining repos: The microservices repo explosion, and what we're doing about it
Microservices have spawned an explosion of dependent projects with multiple repos, creating the need for an integrated solution – we're working on it right now.
Company
We're on target to discontinue support for TLS 1.0 and TLS 1.1 by end of 2018
Find out how to test for potential operational disruptions to your integrations and browsers.
Company
GitLab to deprecate support for TLS 1.0 and TLS 1.1 by end of 2018
Support for TLS 1.0 and 1.1 will be disabled on December 15th, 2018
Company
This is what happens if you lose access to your 2FA GitLab.com account
Support Engineering Manager Lyle Kozloff explains why we no longer accept government ID for two-factor authentication removal.
Find out which plan works best for your team
Learn about pricingLearn about what GitLab can do for your team
Talk to an expert