FAQ: The RegreSSHion vulnerability and GitLab
Find out what CVE-2024-6387 is, how it impacts GitLab, and what you need to know to mitigate it in your GitLab environment.
The backstory on GitLab's security hardening documentation
GitLab has detailed documentation about how to harden your instance, now as a part of GitLab itself. Here's how it came to be.
How we’re creating a threat model framework that works for GitLab
As usual, we’re creating our own path in how we handle our threat modeling, approaching development both iteratively and collaboratively, and seriously shifting left with our framework and processes.
GitLab instance: security best practices
Default settings on products can be massively helpful. However, when it comes to hardening your GitLab instance, we’ve got some helpful configuration recommendations from our security team.
How we manage open source security software
Open source software presents unique security challenges. Here’s what you need to know.
We answer your most popular questions about our Zero Trust journey
From why we chose Okta to issues around data fluidity, here are answers to your most-asked ZT questions.
Zero Trust at GitLab: Where do we go from here?
We take a look back at how far we've come in our ZTN implementation, and at the progress we still need to make.
Find out which plan works best for your team
Learn about pricingLearn about what GitLab can do for your team
Talk to an expert