

Get a behind-the-scenes look at how I helped discover the vulnerability that became CVE-2022-41903.

We developed, tested and open sourced a new tool to analyze program dependencies and protect the supply chain.

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.

Our security researcher takes a look at Gitpod and finds some access tokens under the carpet.

We held a public, ask me anything with our Red Team. Here’s what people asked.

How does product security work differ from pen testing and hacking all the things?

Faster releases, more open source code, and developers unlikely to have formal security training = at risk software apps. The solution? A security champions program.
All fields required
Find out which plan works best for your team
Learn about pricingLearn about what GitLab can do for your team
Talk to an expert