Gitlab hero border pattern left svg Gitlab hero border pattern right svg
Gitlab logo svg

DevSecOps with GitLab

With GitLab, Security is built into the CI pipeline, out of the box. Every code commit is automatically scanned for security vulnerabilities in your code and its dependencies. Actionable results are delivered to the developer in their native workflow for rapid remediation.

Try all features free for 30 days

Empower developers to create secure code

Application Security is hard when security is separated from your DevOps workflow. Security has traditionally been the final hurdle in the development life cycle. Iterative development workflows can make security a release bottleneck. Instead of waiting for security at the end of the development process, you can include it seamlessly within your developer's workflow.

How GitLab enables DevSecOps

  • Every piece of code is tested upon commit for security threats, without incremental cost.
  • The developer can remediate now, while they are still working in that code, or create an issue with one click.
  • The security pro can see and manage unresolved vulnerabilities captured as a by-product of software development.
  • Single source of truth can focus collaboration on remediation, eliminating translation and finger pointing.
  • A single tool reduces cost to buy, integrate and maintain point solutions throughout the DevOps pipeline.
CI/CD Overview

What Are The GitLab Advantages?

  • Contextual. GitLab provides vulnerability findings to developers in their native workflow. Because we scan at code commit, before the code is merged, the developer sees clear cause and effect of their own specific code changes - and only their code changes, thereby eliminating noise. They can address the flaws they just created potentially without involvement from anyone else.
  • Congruent with DevOps processes. GitLab Secure¬†capabilities provide immediate remediation information to the developers as they are still iterating on their code. They need not wait for a merge nor for lengthy scans. Results¬†are interactive and actionable. Automation ensures policies are followed and exceptions documented. Security teams and engineers alike view the same vulnerability information so nothing is lost in translation and silos are eliminated.
  • Integrated with DevOps tools. When triaging vulnerabilities, users can confirm (by creating an issue to solve the problem) or dismiss them (in case they are false positives or there are compensating controls). When using GitLab for SCM and CI, no additional integration is needed between application security and DevOps. That said, if you have a favorite security scanner, integration is straightforward and, you can even use GitLab Secure alongside Jenkins CI
  • Efficient and automated. Set your policies for merging when vulnerabilities are found and for allowing/denying licenses, eliminating mundane work and ensuring consistency. Auto remediation applies patches to vulnerable dependencies and even re-runs the pipeline to evaluate the viability of the patch.

Why integrated security matters

Continuous security testing capabilities

included within GitLab Ultimate

Static Application Security Testing (SAST)

  • Scan the application to spot potential vulnerabilities before code is merged.
  • Vulnerabilities are shown in-line with every merge request
  • All scan results are collected and presented as a single report.
  • Evaluate vulnerabilities from the GitLab pipeline and dismiss or create an issue with one click.

Dynamic Application Security Testing (DAST)

  • Dynamic scanning earlier in the SDLC than ever possible, by leveraging the review app CI/CD capability of GitLab.
  • Test running web applications for known runtime vulnerabilities.
  • Users can provide HTTP credentials to test private areas.
  • Vulnerabilities are shown in-line with every merge request.

Dependency Scanning

  • Analyze external dependencies (e.g. libraries like Ruby gems) for known vulnerabilities on each code commit with GitLab CI/CD.
  • Identify vulnerable dependencies needing updating.
  • Vulnerabilities are shown in-line with every merge request.

Container Scanning

  • Check Docker images for known vulnerabilities in the application environment.
  • Avoid redistribution of vulnerabilities via container images.
  • Vulnerabilities are shown in-line with every merge request.

License Compliance

  • Automatically search project dependencies for approved and unapproved licenses defined by your policies.
  • Custom license policies per project.
  • License analysis results are shown in-line for every merge request for immediate resolution.

Additional Capabilities

  • Auto Remediation: Auto remediation aims to automated vulnerability solution flow, and automatically create a fix. The fix is then tested, and if it passes all the tests already defined for the application, it is deployed to production.
  • Secret Detection: Prevent secrets from accidentally leaking into your Git history. Each commit is scanned for secrets within SAST.
  • Fuzz Testing: Fuzz testing acquisitions are integrating alongside other scanners in the merge request pipeline. See the visions for Fuzzing

Exciting new capabilities!
We welcome your feedback and contribution to our vision and roadmap
Vulnerability Management
Evaluate vulnerabilities based upon risk and scanning vendor used.
Risk-based Triage Filter by scanner vendor
Fuzz testing
Integrating Fuzz Testing acquisitions to apply this powerful technology to automatically test for unknown security flaws.
Coverage-guided Fuzz Testing API Fuzz Testing
Container Security
Protect cloud-native production applications.
Container Network Policies Container Host Security

Deep Dive into a Security demo
See how we compare against other Security tools

Try all GitLab features - free for 30 days

GitLab is more than just source code management or CI/CD. It is a full software development lifecycle & DevOps tool in a single application.

Try GitLab Free
Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license