• Features
• Requirements
• Supported languages and frameworks
• Advanced vulnerability tracking
• Automatic vulnerability resolution
• Supported distributions
  • FIPS-enabled images
• Vulnerability details
• Download a SAST report
• View SAST results
  • Merge request widget
  • Merge request changes view
• Contribute your scanner
• Configuration
  • Configure SAST in your CI/CD YAML
  • Stable vs latest SAST templates
  • Configure SAST by using the UI
    • Configure SAST with customizations
    • Configure SAST with default settings only
  • Overriding SAST jobs
  • Pinning to minor image version
  • Using CI/CD variables to pass credentials for private repositories
    • Using a CI/CD variable to pass username and password to a private Maven repository
  • Enabling Kubesec analyzer
  • Scanning Rust applications
  • Pre-compilation
  • Running jobs in merge request pipelines
  • Available CI/CD variables
    • Custom Certificate Authority
    • Docker images
    • Vulnerability filters
    • Analyzer settings
    • Security scanner configuration
    • Custom CI/CD variables
  • Exclude code from analysis
• Running SAST in an offline environment
  • Requirements for offline SAST
  • Make GitLab SAST analyzer images available inside your Docker registry
    • If support for Custom Certificate Authorities are needed
  • Set SAST CI/CD variables to use local SAST analyzers
  • Configure certificate checking of packages
• Running SAST in SELinux

Static Application Security Testing (SAST)

If you’re using GitLab CI/CD, you can use Static Application Security Testing (SAST) to check your source code for known vulnerabilities. You can run SAST analyzers in any GitLab tier. The analyzers output JSON-formatted reports as job artifacts.

With GitLab Ultimate, SAST results are also processed so you can:

• Use them in approval workflows.
• Review them in the security dashboard.

For more information, see Features.

Features

The following table lists the GitLab tiers in which each feature is available.

Requirements

Before you run a SAST analyzer in your instance, make sure you have the following:

• Linux-based GitLab Runner with the docker or kubernetes executor. If you’re using hosted runners for GitLab.com, this is enabled by default.
  • Windows Runners are not supported.
  • CPU architectures other than amd64 are not supported.
• GitLab CI/CD configuration (.gitlab-ci.yml) must include the test stage, which is included by default. If you redefine the stages in the .gitlab-ci.yml file, the test stage is required.

Supported languages and frameworks

GitLab SAST uses different scanning technologies depending on which programming languages are found in your project’s source code. Most languages are covered by GitLab Advanced SAST or by Semgrep-based scanning with GitLab-managed rules.

After you enable SAST, the right set of analyzers runs automatically even if your project uses more than one language.

For nearly all languages, GitLab SAST scans your source code directly, rather than requiring you to modify your build configuration or compile it to a binary first. Only the SpotBugs-based analyzer, which is used to scan Groovy code, requires compilation.

For more information about our plans for language support in SAST, see the category direction page.

1. The SpotBugs-based analyzer supports Gradle, Maven, and SBT. It can also be used with variants like the Gradle wrapper, Grails, and the Maven wrapper. However, SpotBugs has limitations when used against Ant-based projects. You should use the Advanced SAST or Semgrep-based analyzer for Ant-based Java or Scala projects.
2. Requires a custom ruleset and an override to the semgrep-sast CI job. See Scanning Rust applications for an example.

To learn more about SAST analyzers that are no longer supported, see Analyzers that have reached End of Support.

Advanced vulnerability tracking

Source code is volatile; as developers make changes, source code may move within files or between files. Security analyzers may have already reported vulnerabilities that are being tracked in the Vulnerability Report. These vulnerabilities are linked to specific problematic code fragments so that they can be found and fixed. If the code fragments are not tracked reliably as they move, vulnerability management is harder because the same vulnerability could be reported again.

GitLab SAST uses an advanced vulnerability tracking algorithm to more accurately identify when the same vulnerability has moved within a file due to refactoring or unrelated changes.

Advanced vulnerability tracking is available in a subset of the supported languages and analyzers:

• C, in the Semgrep-based only
• C++, in the Semgrep-based only
• C#, in the Advanced SAST and Semgrep-based analyzers
• Go, in the Advanced SAST and Semgrep-based analyzers
• Java, in the Advanced SAST and Semgrep-based analyzers
• JavaScript, in the Advanced SAST and Semgrep-based analyzers
• PHP, in the Semgrep-based analyzer only
• Python, in the Advanced SAST and Semgrep-based analyzers
• Ruby, in the Semgrep-based analyzer only

Support for more languages and analyzers is tracked in this epic.

For more information, see the confidential project https://gitlab.com/gitlab-org/security-products/post-analyzers/tracking-calculator. The content of this project is available only to GitLab team members.

Automatic vulnerability resolution

To help you focus on the vulnerabilities that are still relevant, GitLab SAST automatically resolves vulnerabilities when:

• You disable a predefined rule.
• We remove a rule from the default ruleset.

Automatic resolution is available only for findings from the Semgrep-based analyzer. The Vulnerability Management system leaves a comment on automatically-resolved vulnerabilities so you still have a historical record of the vulnerability.

If you re-enable the rule later, the findings are reopened for triage.

Supported distributions

The default scanner images are built on a base Alpine image for size and maintainability.

FIPS-enabled images

GitLab offers an image version, based on the Red Hat UBI base image, that uses a FIPS 140-validated cryptographic module. To use the FIPS-enabled image, you can either:

• Set the SAST_IMAGE_SUFFIX to -fips.
• Add the -fips extension to the default image name.

For example:

variables:
  SAST_IMAGE_SUFFIX: '-fips'

include:
  - template: Jobs/SAST.gitlab-ci.yml

A FIPS-compliant image is only available for the Advanced SAST and Semgrep-based analyzer.

Vulnerability details

SAST vulnerabilities are named according to the primary Common Weakness Enumeration (CWE) identifier for the discovered vulnerability. Read the description of each vulnerability finding to learn more about the specific issue that the scanner has detected.

For more information on SAST coverage, see SAST rules.

Download a SAST report

Each SAST analyzer outputs a JSON report as a job artifact. The file contains details of all detected vulnerabilities. You can download the file for processing outside GitLab.

For more information, see:

• SAST report file schema
• Example SAST report file

View SAST results

In Ultimate, the SAST report file is processed by GitLab and the details are shown in the UI:

• Merge request widget
• Merge request changes view
• Vulnerability report
• Pipeline security report

A pipeline consists of multiple jobs, including SAST and DAST scanning. If any job fails to finish for any reason, the security dashboard does not show SAST scanner output. For example, if the SAST job finishes but the DAST job fails, the security dashboard does not show SAST results. On failure, the analyzer outputs an exit code.

Merge request widget

SAST results display in the merge request widget area if a report from the target branch is available for comparison. The merge request widget shows:

• new SAST findings that are introduced by the MR.
• existing findings that are resolved by the MR.

The results are compared using Advanced Vulnerability Tracking whenever it is available.

Merge request changes view

SAST results display in the merge request Changes view. Lines containing SAST issues are marked by a symbol beside the gutter. Select the symbol to see the list of issues, then select an issue to see its details.

Contribute your scanner

The Security Scanner Integration documentation explains how to integrate other security scanners into GitLab.

Configuration

SAST scanning runs in your CI/CD pipeline. When you add the GitLab-managed CI/CD template to your pipeline, the right SAST analyzers automatically scan your code and save results as SAST report artifacts.

To configure SAST for a project you can:

• Use Auto SAST, provided by Auto DevOps.
• Configure SAST in your CI/CD YAML.
• Configure SAST by using the UI.

You can enable SAST across many projects by enforcing scan execution.

To configure Advanced SAST (available in GitLab Ultimate only), follow these instructions.

You can change configuration variables or customize detection rules if needed, but GitLab SAST is designed to be used in its default configuration.

Configure SAST in your CI/CD YAML

To enable SAST, you include the SAST.gitlab-ci.yml template. The template is provided as a part of your GitLab installation.

Copy and paste the following to the bottom of the .gitlab-ci.yml file. If an include line already exists, add only the template line below it.

include:
  - template: Jobs/SAST.gitlab-ci.yml

The included template creates SAST jobs in your CI/CD pipeline and scans your project’s source code for possible vulnerabilities.

The results are saved as a SAST report artifact that you can later download and analyze. When downloading, you always receive the most recent SAST artifact available.

Stable vs latest SAST templates

SAST provides two templates for incorporating security testing into your CI/CD pipelines:

• SAST.gitlab-ci.yml (recommended)

  The stable template offers a reliable and consistent SAST experience. You should use the stable template for most users and projects that require stability and predictable behavior in their CI/CD pipelines.

• SAST.latest.gitlab-ci.yml

  This template is for those who want to access and test cutting-edge features. It is not considered stable and may include breaking changes that are planned for the next major release. This template allows you to try new features and updates before they become part of the stable release, making it ideal for those comfortable with potential instability and eager to provide feedback on new functionality.

Configure SAST by using the UI

You can enable and configure SAST by using the UI, either with the default settings or with customizations. The method you can use depends on your GitLab license tier.

Configure SAST with customizations

To enable and configure SAST with customizations:

1. On the left sidebar, select Search or go to and find your project.
2. Select Secure > Security configuration.
3. If the latest pipeline for the default branch of the project has completed and produced valid SAST artifacts, select Configure SAST, otherwise select Enable SAST in the Static Application Security Testing (SAST) row.

4. Enter the custom SAST values.

   Custom values are stored in the .gitlab-ci.yml file. For CI/CD variables not in the SAST Configuration page, their values are inherited from the GitLab SAST template.

5. Select Create Merge Request.
6. Review and merge the merge request.

Pipelines now include a SAST job.

Configure SAST with default settings only

To enable and configure SAST with default settings:

1. On the left sidebar, select Search or go to and find your project.
2. Select Secure > Security configuration.
3. In the SAST section, select Configure with a merge request.
4. Review and merge the merge request to enable SAST.

Pipelines now include a SAST job.

Overriding SAST jobs

To override a job definition, (for example, change properties like variables, dependencies, or rules), declare a job with the same name as the SAST job to override. Place this new job after the template inclusion and specify any additional keys under it. For example, this enables FAIL_NEVER for the spotbugs analyzer:

include:
  - template: Jobs/SAST.gitlab-ci.yml

spotbugs-sast:
  variables:
    FAIL_NEVER: 1

Pinning to minor image version

The GitLab-managed CI/CD template specifies a major version and automatically pulls the latest analyzer release within that major version.

In some cases, you may need to use a specific version. For example, you might need to avoid a regression in a later release.

To override the automatic update behavior, set the SAST_ANALYZER_IMAGE_TAG CI/CD variable in your CI/CD configuration file after you include the SAST.gitlab-ci.yml template.

Only set this variable within a specific job. If you set it at the top level, the version you set is used for other SAST analyzers.

You can set the tag to:

• A major version, like 3. Your pipelines use any minor or patch updates that are released within this major version.
• A minor version, like 3.7. Your pipelines use any patch updates that are released within this minor version.
• A patch version, like 3.7.0. Your pipelines don’t receive any updates.

This example uses a specific minor version of the semgrep analyzer and a specific patch version of the brakeman analyzer:

include:
  - template: Jobs/SAST.gitlab-ci.yml

semgrep-sast:
  variables:
    SAST_ANALYZER_IMAGE_TAG: "3.7"

brakeman-sast:
  variables:
    SAST_ANALYZER_IMAGE_TAG: "3.1.1"

Using CI/CD variables to pass credentials for private repositories

Some analyzers require downloading the project’s dependencies to perform the analysis. In turn, such dependencies may live in private Git repositories and thus require credentials like username and password to download them. Depending on the analyzer, such credentials can be provided to it via custom CI/CD variables.

Using a CI/CD variable to pass username and password to a private Maven repository

If your private Maven repository requires login credentials, you can use the MAVEN_CLI_OPTS CI/CD variable.

For more information, see how to use private Maven repositories.

Enabling Kubesec analyzer

You need to set SCAN_KUBERNETES_MANIFESTS to "true" to enable the Kubesec analyzer. In .gitlab-ci.yml, define:

include:
  - template: Jobs/SAST.gitlab-ci.yml

variables:
  SCAN_KUBERNETES_MANIFESTS: "true"

Scanning Rust applications

To scan Rust applications, you must:

1. Provide a custom ruleset for Rust. Create a file named sast-ruleset.toml in a .gitlab/ directory at the root of your repository. Add the following contents:

   [semgrep]
     description = "Rust ruleset for Semgrep"
     targetdir = "/sgrules"
     timeout = 60
   
     [[semgrep.passthrough]]
       type  = "url"
       value = "https://semgrep.dev/c/p/rust"
       target = "rust.yml"
   

   This configuration uses the open-source Semgrep ruleset. Read more on customizing rulesets.

2. Override the semgrep-sast job to add a rule that detects Rust (.rs) files. Define the following in the .gitlab-ci.yml file:

   include:
     - template: Jobs/SAST.gitlab-ci.yml
   
   semgrep-sast:
     rules:
       - if: $CI_COMMIT_BRANCH
         exists:
           - '**/*.rs'
           # include any other file extensions you need to scan from the semgrep-sast template: Jobs/SAST.gitlab-ci.yml
   

Pre-compilation

Most GitLab SAST analyzers directly scan your source code without compiling it first. However, for technical reasons, the SpotBugs-based analyzer scans compiled bytecode.

By default, the SpotBugs-based analyzer automatically attempts to fetch dependencies and compile your code so it can be scanned. Automatic compilation can fail if:

• your project requires custom build configurations.
• you use language versions that aren’t built into the analyzer.

To resolve these issues, you can skip the analyzer’s compilation step and directly provide artifacts from an earlier stage in your pipeline instead. This strategy is called pre-compilation.

To use pre-compilation:

1. Output your project’s dependencies to a directory in the project’s working directory, then save that directory as an artifact by setting the artifacts: paths configuration.
2. Provide the COMPILE: "false" CI/CD variable to the analyzer job to disable automatic compilation.
3. Add your compilation stage as a dependency for the analyzer job.

To allow the analyzer to recognize the compiled artifacts, you must explicitly specify the path to the vendored directory. This configuration can vary depending on how the project is set up. For Maven projects, you can use MAVEN_REPO_PATH. See Analyzer settings for the complete list of available options.

The following example pre-compiles a Maven project and provides it to the SpotBugs-based SAST analyzer:

stages:
  - build
  - test

include:
  - template: Jobs/SAST.gitlab-ci.yml

build:
  image: maven:3.6-jdk-8-slim
  stage: build
  script:
    - mvn package -Dmaven.repo.local=./.m2/repository
  artifacts:
    paths:
      - .m2/
      - target/

spotbugs-sast:
  dependencies:
    - build
  variables:
    MAVEN_REPO_PATH: $CI_PROJECT_DIR/.m2/repository
    COMPILE: "false"
  artifacts:
    reports:
      sast: gl-sast-report.json

Running jobs in merge request pipelines

See Use security scanning tools with merge request pipelines.

Available CI/CD variables

SAST can be configured using the variables parameter in .gitlab-ci.yml.

The following example includes the SAST template to override the SEARCH_MAX_DEPTH variable to 10 in all jobs. The template is evaluated before the pipeline configuration, so the last mention of the variable takes precedence.

include:
  - template: Jobs/SAST.gitlab-ci.yml

variables:
  SEARCH_MAX_DEPTH: 10

Custom Certificate Authority

To trust a custom Certificate Authority, set the ADDITIONAL_CA_CERT_BUNDLE variable to the bundle of CA certs that you want to trust in the SAST environment. The ADDITIONAL_CA_CERT_BUNDLE value should contain the text representation of the X.509 PEM public-key certificate. For example, to configure this value in the .gitlab-ci.yml file, use the following:

variables:
  ADDITIONAL_CA_CERT_BUNDLE: |
      -----BEGIN CERTIFICATE-----
      MIIGqTCCBJGgAwIBAgIQI7AVxxVwg2kch4d56XNdDjANBgkqhkiG9w0BAQsFADCB
      ...
      jWgmPqF3vUbZE0EyScetPJquRFRKIesyJuBFMAs=
      -----END CERTIFICATE-----

The ADDITIONAL_CA_CERT_BUNDLE value can also be configured as a custom variable in the UI, either as a file, which requires the path to the certificate, or as a variable, which requires the text representation of the certificate.

Docker images

The following are Docker image-related CI/CD variables.

Vulnerability filters

Footnotes:

1. You might need to exclude temporary directories used by your build tool as these can generate false positives. To exclude paths, copy and paste the default excluded paths, then add your own paths to be excluded. If you don’t specify the default excluded paths, the defaults are overridden and only the paths you specify are excluded from SAST scans.

2. For these analyzers, SAST_EXCLUDED_PATHS is implemented as a pre-filter, which is applied before the scan is executed.

   The analyzer skips any files or directories whose path matches one of the comma-separated patterns.

   For example, if SAST_EXCLUDED_PATHS is set to *.py,tests:

   • *.py ignores the following:
     • foo.py
     • src/foo.py
     • foo.py/bar.sh
   • tests ignores:
     • tests/foo.py
     • a/b/tests/c/foo.py

   Each pattern is a glob-style pattern that uses the same syntax as gitignore.

3. For these analyzers, SAST_EXCLUDED_PATHS is implemented as a post-filter, which is applied after the scan is executed.

   Patterns can be globs (see doublestar.Match for supported patterns), or file or folder paths (for example, doc,spec). Parent directories also match patterns.

   The post-filter implementation of SAST_EXCLUDED_PATHS is available for all SAST analyzers. Some SAST analyzers such as those with superscript 2 implement SAST_EXCLUDED_PATHS as both a pre-filter and post-filter. A pre-filter is more efficient because it reduces the number of files to be scanned.

   For analyzers that support SAST_EXCLUDED_PATHS as both a pre-filter and post-filter, the pre-filter is applied first, then the post-filter is applied to any vulnerabilities that remain.

4. For this variable, Path patterns can be globs (see doublestar.Match for supported patterns). Directories are excluded from the build process if the path pattern matches a supported build file:

   • build.sbt
   • grailsw
   • gradlew
   • build.gradle
   • mvnw
   • pom.xml
   • build.xml

   For example, to exclude building and scanning a maven project containing a build file with the path project/subdir/pom.xml, pass a glob pattern that explicitly matches the build file, such as project/*/*.xml or **/*.xml, or an exact match such as project/subdir/pom.xml.

   Passing a parent directory for the pattern, such as project or project/subdir, does not exclude the directory from being built, because in this case, the build file is not explicitly matched by the pattern.

5. The SAST CI/CD template searches the repository to detect the programming languages used, and selects the matching analyzers. Then, each analyzer searches the codebase to find the specific files or directories it should scan. Set the value of SEARCH_MAX_DEPTH to specify how many directory levels the analyzer’s search phase should span.

Analyzer settings

Some analyzers can be customized with CI/CD variables.

Security scanner configuration

SAST analyzers internally use OSS security scanners to perform the analysis. We set the recommended configuration for the security scanner so that you need not to worry about tuning them. However, there can be some rare cases where our default scanner configuration does not suit your requirements.

To allow some customization of scanner behavior, you can add a limited set of flags to the underlying scanner. Specify the flags in the SAST_SCANNER_ALLOWED_CLI_OPTS CI/CD variable. These flags are added to the scanner’s CLI options.

Custom CI/CD variables

In addition to the aforementioned SAST configuration CI/CD variables, all custom variables are propagated to the underlying SAST analyzer images if the SAST vendored template is used.

Exclude code from analysis

You can mark individual lines, or blocks, of code to be excluded from being analyzed for vulnerabilities. You should manage all vulnerabilities through Vulnerability Management, or adjust the scanned file paths using SAST_EXCLUDED_PATHS before using this method of finding-by-finding comment annotation.

When using the Semgrep-based analyzer, the following options are also available:

• Ignore a line of code - add // nosemgrep: comment to the end of the line (the prefix is according to the development language).

  Java example:

  vuln_func(); // nosemgrep
  

  Python example:

  vuln_func(); # nosemgrep
  

• Ignore a line of code for specific rule - add // nosemgrep: RULE_ID comment at the end of the line (the prefix is according to the development language).

• Ignore a file or directory - create a .semgrepignore file in your repository’s root directory or your project’s working directory and add patterns for files and folders there.

For more details see Semgrep documentation.

Running SAST in an offline environment

For self-managed GitLab instances in an environment with limited, restricted, or intermittent access to external resources through the internet, some adjustments are required for the SAST job to run successfully. For more information, see Offline environments.

Requirements for offline SAST

To use SAST in an offline environment, you need:

• GitLab Runner with the docker or kubernetes executor.
• A Docker container registry with locally available copies of SAST analyzer images.
• Configure certificate checking of packages (optional).

GitLab Runner has a default pull_policy of always, meaning the runner tries to pull Docker images from the GitLab container registry even if a local copy is available. The GitLab Runner pull_policy can be set to if-not-present in an offline environment if you prefer using only locally available Docker images. However, we recommend keeping the pull policy setting to always if not in an offline environment, as this enables the use of updated scanners in your CI/CD pipelines.

Make GitLab SAST analyzer images available inside your Docker registry

For SAST with all supported languages and frameworks, import the following default SAST analyzer images from registry.gitlab.com into your local Docker container registry:

registry.gitlab.com/security-products/gitlab-advanced-sast:1
registry.gitlab.com/security-products/kubesec:5
registry.gitlab.com/security-products/pmd-apex:5
registry.gitlab.com/security-products/semgrep:5
registry.gitlab.com/security-products/sobelow:5
registry.gitlab.com/security-products/spotbugs:5

The process for importing Docker images into a local offline Docker registry depends on your network security policy. Consult your IT staff to find an accepted and approved process by which external resources can be imported or temporarily accessed. These scanners are periodically updated with new definitions, and you may be able to make occasional updates on your own.

For details on saving and transporting Docker images as a file, see the Docker documentation on docker save, docker load, docker export, and docker import.

If support for Custom Certificate Authorities are needed

Support for custom certificate authorities was introduced in the following versions.

Set SAST CI/CD variables to use local SAST analyzers

Add the following configuration to your .gitlab-ci.yml file. You must replace SECURE_ANALYZERS_PREFIX to refer to your local Docker container registry:

include:
  - template: Jobs/SAST.gitlab-ci.yml

variables:
  SECURE_ANALYZERS_PREFIX: "localhost:5000/analyzers"

The SAST job should now use local copies of the SAST analyzers to scan your code and generate security reports without requiring internet access.

Configure certificate checking of packages

If a SAST job invokes a package manager, you must configure its certificate verification. In an offline environment, certificate verification with an external source is not possible. Either use a self-signed certificate or disable certificate verification. Refer to the package manager’s documentation for instructions.

Running SAST in SELinux

By default SAST analyzers are supported in GitLab instances hosted on SELinux. Adding a before_script in an overridden SAST job may not work as runners hosted on SELinux have restricted permissions.