Static application security testing (SAST)

Static application security testing (SAST) discovers vulnerabilities in your source code before theyreach production. Integrated directly into your CI/CD pipeline, SAST identifies security issuesduring development when they’re easiest and most cost-effective to fix.

Security vulnerabilities found late in development create costly delays and potential breaches. SASTscans happen automatically with each commit, giving you immediate feedback without disruptingyour workflow.

Features

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

Getting started

If you are new to SAST, the following steps show how to enable SAST for your project.

Prerequisites:

• Linux-based GitLab Runner with either the Docker or Kubernetes executor. If you’re using hostedrunners 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 thetest stage, which is included bydefault. If you redefine the stages in the.gitlab-ci.yml file, thetest stage is required.

To enable SAST:

1. On the left sidebar, selectSearch or go to and find your project. If you’veturned on the new navigation, this field is on the top bar.
2. If your project does not already have one, create a.gitlab-ci.yml file in the root directory.
3. At the top of the.gitlab-ci.yml file, add one of the following lines:

Using a template:

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

Or using a CI component:

include:-component:gitlab.com/components/sast/sast@main

At this point, SAST is enabled in your pipeline.If supported source code is present, the appropriate analyzers and default rules automatically scan for vulnerabilities when a pipeline runs.The corresponding jobs will appear under thetest stage in your pipeline.

After completing these steps, you can:

• Learn more about how tounderstand the results.
• Reviewoptimization tips.
• Plan arollout to more projects.

For details on other configuration methods, seeConfiguration.

Understanding the results

You can review vulnerabilities in a pipeline:

1. On the left sidebar, selectSearch or go to and find your project. If you’veturned on the new navigation, this field is on the top bar.
2. On the left sidebar, selectBuild >Pipelines.
3. Select the pipeline.
4. Select theSecurity tab.
5. Either download results, or select a vulnerability to view its details (Ultimate only), including:
   • Description: Explains the cause of the vulnerability, its potential impact, and recommended remediation steps.
   • Status: Indicates whether the vulnerability has been triaged or resolved.
   • Severity: Categorized into six levels based on impact.Learn more about severity levels.
   • Location: Shows the filename and line number where the issue was found.Selecting the file path opens the corresponding line in the code view.
   • Scanner: Identifies which analyzer detected the vulnerability.
   • Identifiers: A list of references used to classify the vulnerability, such as CWE identifiers and the IDs of the rules that detected it.

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, seeSAST rules.

In Ultimate, you can also download the security scan results:

• In the pipeline’sSecurity tab, selectDownload results.

For more details, seePipeline security report.

Additional ways to see SAST results:

• Merge request widget: Shows newly introduced or resolved findings.
• Merge request changes view: Shows inline annotations for changed lines.
• Vulnerability report: Shows confirmed vulnerabilities on the default branch.

A pipeline consists of multiple jobs, including SAST and DAST scanning. If any job fails to finishfor any reason, the security dashboard does not show SAST scanner output. For example, if the SASTjob 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 requestChanges view. Lines containing SASTissues 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.

Optimization

To optimize SAST according to your requirements you can:

• Disable a rule.
• Exclude files or paths from being scanned.

Disable a rule

To disable a rule, for example because it generates too many false positives:

1. On the left sidebar, selectSearch or go to and find your project. If you’veturned on the new navigation, this field is on the top bar.

2. Create a.gitlab/sast-ruleset.toml file at the root of your project if one does not already exist.

3. In the vulnerability’s details, locate the ID of the rule that triggered the finding.

4. Use the rule ID to disable the rule. For example, to disablegosec.G107-1, add the following in.gitlab/sast-ruleset.toml:

   [semgrep][[semgrep.ruleset]]disable=true[semgrep.ruleset.identifier]type="semgrep_id"value="gosec.G107-1"

For more details on customizing rulesets, seeCustomize rulesets.

Exclude files or paths from being scanned

To exclude files or paths from being scanned, for example test or temporary code, set theSAST_EXCLUDED_PATHS variable.For example, to skiprule-template-injection.go, add the following to your.gitlab-ci.yml:

variables:SAST_EXCLUDED_PATHS:"rule-template-injection.go"

For more information about configuration options, seeAvailable CI/CD variables.

Roll out

After you are confident in the SAST results for a single project, you can extend its implementation to additional projects:

• Useenforced scan execution to apply SAST settings across groups.
• Share and reuse a central ruleset byspecifying a remote configuration file.
• If you have unique requirements, SAST can be run in an offline environment or under SELinux constraints.

Supported languages and frameworks

GitLab SAST supports scanning the following languages and frameworks.

The available scanning options depend on the GitLab tier:

• In Ultimate, GitLab Advanced SAST provides more accurate results. You should use it for the languages it supports.
• In all tiers, you can use GitLab-provided analyzers, based on open-source scanners, to scan your code.

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

Languages with full support

These languages are supported by both GitLab Advanced SAST (Ultimate) and standard analyzers (all tiers):

Footnotes:

1. GitLab Advanced SAST - Ultimate tier only.
2. All tiers. UsesSemgrep analyzer withGitLab-managed rules unless otherwise specified.
3. Including Java Server Pages (JSP) and Android.
4. Including Node.js and React.
5. Including Ruby on Rails.
6. YAML support is restricted to the following file patterns:
   • application*.yml
   • application*.yaml
   • bootstrap*.yml
   • bootstrap*.yaml

Languages with standard analyzer support only

These languages are supported by standard analyzers (all tiers) but not by GitLab Advanced SAST:

Footnotes:

1. All tiers. UsesSemgrepanalyzer withGitLab-managed rules unless otherwise specified.
2. The referenced epic proposes GitLab Advanced SAST support for these languages.
3. SpotBugs with the find-sec-bugs plugin. Supports Gradle, Maven, and SBT. It can also be used with variantslike the Gradle wrapper, Grails, and the Maven wrapper. However, SpotBugs haslimitations when used against Ant-basedprojects. You should use the GitLab Advanced SAST or Semgrep-based analyzer for Ant-based Java orScala projects.
4. Including Android.

The SAST CI/CD template also includes an analyzer job that can scan Kubernetes manifests and Helm charts; this job is off by default.SeeEnabling Kubesec analyzer or considerIaC scanning, which supports additional platforms, instead.

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

Advanced vulnerability tracking

Source code is volatile; as developers make changes, source code may move in the same file orbetween files. Security analyzers may have already reported vulnerabilities that are being trackedin the vulnerability report. These vulnerabilities are linked to specific problematic code fragmentsso 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 thesame vulnerability has moved in the same file due to refactoring or unrelated changes.

Support for advanced vulnerability tracking is dependent on the language and analyzers used.

Support for more languages and analyzers is tracked inepic 5144.

For more information, see the confidential projecthttps://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 automaticallyresolves vulnerabilities when:

• Youdisable a predefined rule.
• We remove a rule from the default ruleset.

Automatic resolution is available only for findings from theSemgrep-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 theRed Hat UBI base image,that uses a FIPS 140-validated cryptographic module. To use the FIPS-enabled image, you can either:

• Set theSAST_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 GitLab Advanced SAST and Semgrep-based analyzer.

Download a SAST report

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

For more information, see:

• SAST report file schema
• Example SAST report file

Configuration

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

To configure SAST for a project you can:

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

You can enable SAST across many projects byenforcing scan execution.

To configure GitLab Advanced SAST (available in GitLab Ultimate only), seeGitLab Advanced SAST.

You canchange configuration variables orcustomize 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, youincludetheSAST.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 aninclude linealready exists, add only thetemplate line below it.

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

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

The results are saved as aSAST report artifactthat 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, selectSearch or go to and find your project. If you’veturned on the new navigation, this field is on the top bar.

2. SelectSecure >Security configuration.

3. If the latest pipeline for the default branch of the project has completedand produced validSAST artifacts, selectConfigure SAST, otherwiseselectEnable 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 SASTConfiguration page, their values are inherited from the GitLab SAST template.

5. SelectCreate 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, selectSearch or go to and find your project. If you’veturned on the new navigation, this field is on the top bar.
2. SelectSecure >Security configuration.
3. In the SAST section, selectConfigure 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 likevariables,dependencies, orrules),declare a job with the same name as the SAST job to override. Place this new job after the templateinclusion and specify any additional keys under it. For example, this enablesFAIL_NEVER for thespotbugs analyzer:

include:-template:Jobs/SAST.gitlab-ci.ymlspotbugs-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 theSAST_ANALYZER_IMAGE_TAG CI/CD variablein your CI/CD configuration file after you include theSAST.gitlab-ci.yml template.

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

You can set the tag to:

• A major version, like3. Your pipelines use any minor or patch updates that are released within this major version.
• A minor version, like3.7. Your pipelines use any patch updates that are released within this minor version.
• A patch version, like3.7.0. Your pipelines don’t receive any updates.

This example uses a specific minor version of thesemgrep analyzer and a specific patch version of thebrakeman analyzer:

include:-template:Jobs/SAST.gitlab-ci.ymlsemgrep-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 toperform the analysis. In turn, such dependencies may live in private Gitrepositories and thus require credentials like username and password to download them.Depending on the analyzer, such credentials can be provided toit viacustom 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 theMAVEN_CLI_OPTS CI/CD variable.

For more information, seehow to use private Maven repositories.

Enabling Kubesec analyzer

You need to setSCAN_KUBERNETES_MANIFESTS to"true" to enable theKubesec analyzer. In.gitlab-ci.yml, define:

include:-template:Jobs/SAST.gitlab-ci.ymlvariables:SCAN_KUBERNETES_MANIFESTS:"true"

Scan other languages with the Semgrep-based analyzer

You can customize the Semgrep-based SAST analyzer to scan languages that are not supported by aGitLab-managed ruleset. However, because GitLab does not provide rulesets for these other languages,you mustreplace or add to the predefined rulesto cover them. You must also modify therules of thesemgrep-sast CI/CD job so that the job runswhen the relevant files are modified.

Scan a Rust application

For example, to scan a Rust application, you must:

1. Provide a custom ruleset for Rust. Create a file namedsast-ruleset.toml in a.gitlab/ directory at the root of your repository. The following example uses the Semgrep registry’s default ruleset for Rust:

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

   For more details, seeReplace or add to the predefined rules.

2. Override thesemgrep-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.ymlsemgrep-sast:rules:-if:$CI_COMMIT_BRANCHexists:-'**/*.rs'# include any other file extensions you need to scan from the semgrep-sast template: Jobs/SAST.gitlab-ci.yml

JDK21 support for SpotBugs analyzer

Version6 of the SpotBugs analyzer adds support for JDK21 and removes JDK11. The default version remains at5 as discussed inissue 517169.To use version6, manually pin the version by following the instructionsPinning to minor image version.

spotbugs-sast:variables:SAST_ANALYZER_IMAGE_TAG:"6"

Using pre-compilation with SpotBugs analyzer

The SpotBugs-based analyzer scans compiled bytecode for Groovy projects. By default, itautomatically attempts to fetch dependencies and compile your code so it can be scanned.

Automatic compilation can fail if either:

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

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

Sharing pre-compiled artifacts

1. Use a compilation job (typically namedbuild) to compile your project and store the compiledoutput as ajob artifact by using the CI/CDartifacts: paths variable.

   • For Maven projects, the output folder is usually thetarget directory.
   • For Gradle projects, it’s typically thebuild directory.
   • If your project uses a custom output location, set the artifacts path accordingly.

2. Disable automatic compilation by setting theCOMPILE: "false" CI/CD variable in thespotbugs-sast job.

3. Ensure thespotbugs-sast job depends on the compilation job by setting thedependencies keyword. This allows thespotbugs-sast job to download and use the artifacts created in the compilation job.

The following example pre-compiles a Gradle project and provides the compiled bytecode to the analyzer:

stages:-build-testinclude:-template:Jobs/SAST.gitlab-ci.ymlbuild:image:gradle:7.6-jdk8stage:buildscript:-gradle buildartifacts:paths:-build/spotbugs-sast:dependencies:-buildvariables:COMPILE:"false"SECURE_LOG_LEVEL:debug

Specifying dependencies (Maven only)

If your project requires external dependencies to be recognized by the analyzer and you’re using Maven, you can specify the location of the local repository by using theMAVEN_REPO_PATH variable.

Specifying dependencies is only supported for Maven-based projects. Other build tools (for example, Gradle) do not have an equivalent mechanism for specifying dependencies. In that case, ensure that your compiled artifacts include all necessary dependencies.

The following example pre-compiles a Maven project and provides the compiled bytecode along with the dependencies to the analyzer:

stages:-build-testinclude:-template:Jobs/SAST.gitlab-ci.ymlbuild:image:maven:3.6-jdk-8-slimstage:buildscript:-mvn package -Dmaven.repo.local=./.m2/repositoryartifacts:paths:-.m2/-target/spotbugs-sast:dependencies:-buildvariables:MAVEN_REPO_PATH:$CI_PROJECT_DIR/.m2/repositoryCOMPILE:"false"SECURE_LOG_LEVEL:debug

Running jobs in merge request pipelines

SeeUse security scanning tools with merge request pipelines.

Available CI/CD variables

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

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

include:-template:Jobs/SAST.gitlab-ci.ymlvariables:SEARCH_MAX_DEPTH:10

Custom Certificate Authority

To trust a custom Certificate Authority, set theADDITIONAL_CA_CERT_BUNDLE variable to the bundleof CA certs that you want to trust in the SAST environment. TheADDITIONAL_CA_CERT_BUNDLE value should contain thetext 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-----

TheADDITIONAL_CA_CERT_BUNDLE value can also be configured as acustom variable in the UI, either as afile, 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 asthese can generate false positives. To exclude paths, copy and paste the default excluded paths, thenadd yourown paths to be excluded. If you don’t specify the default excluded paths, the defaults are overridden and only thepaths you specify are excluded from SAST scans.

2. For these analyzers,SAST_EXCLUDED_PATHS is implemented as apre-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, ifSAST_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 asgitignore.

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

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

   The post-filter implementation ofSAST_EXCLUDED_PATHS is available for all SAST analyzers. SomeSAST analyzers such as those withsuperscript2 implementSAST_EXCLUDED_PATHSas both a pre-filter and post-filter. A pre-filter is more efficient because it reduces the number of filesto be scanned.

   For analyzers that supportSAST_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(seedoublestar.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 amaven project containing a build file with the pathproject/subdir/pom.xml, pass a glob pattern that explicitly matches the build file, such asproject/*/*.xml or**/*.xml, or an exact match such asproject/subdir/pom.xml.

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

5. TheSAST CI/CD templatesearches the repository to detect the programming languagesused, and selects the matching analyzers. Then, each analyzer searches the codebase to find the specific files or directoriesit should scan. Set the value ofSEARCH_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 recommendedconfiguration 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 yourrequirements.

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

Custom CI/CD variables

When the GitLab SAST template is used, all standard SAST configuration CI/CD variablesandcustom variables arepropagated to the underlying SAST analyzer images.

Exclude code from analysis

You can mark individual lines, or blocks, of code to be excluded from being analyzed forvulnerabilities. You should manage all vulnerabilities through Vulnerability Management, or adjust the scanned file pathsusingSAST_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. GitLab Semgrep analyzer automatically merges your custom.semgrepignore file withGitLab built-in ignore patterns.

For more details seeSemgrep documentation.

Running SAST in an offline environment

For instances in an environment with limited, restricted, or intermittent accessto external resources through the internet, some adjustments are required for the SAST job torun successfully. For more information, seeOffline environments.

Requirements for offline SAST

To use SAST in an offline environment, you need:

• GitLab Runner with thedocker orkubernetes executor. Seeprerequisites for details.
• A Docker container registry with locally available copies of SASTanalyzer images.
• Configure certificate checking of packages (optional).

GitLab Runner has adefaultpull_policy ofalways,meaning the runner tries to pull Docker images from the GitLab container registry even if a localcopy is available. The GitLab Runnerpull_policy can be set toif-not-presentin an offline environment if you prefer using only locally available Docker images. However, werecommend keeping the pull policy setting toalways if not in an offline environment, as thisenables 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 analyzerimages fromregistry.gitlab.com into yourlocal Docker container registry:

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

The process for importing Docker images into a local offline Docker registry depends onyour network security policy. Consult your IT staff to find an accepted and approvedprocess by which external resources can be imported or temporarily accessed. These scanners areperiodically updatedwith 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
• 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 replaceSECURE_ANALYZERS_PREFIX to refer to your local Docker container registry:

include:-template:Jobs/SAST.gitlab-ci.ymlvariables:SECURE_ANALYZERS_PREFIX:"localhost:5000/analyzers"

The SAST job should now use local copies of the SAST analyzers to scan your code and generatesecurity 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 anoffline environment, certificate verification with an external source is not possible. Either use aself-signed certificate or disable certificate verification. Refer to the package manager’sdocumentation for instructions.

Running SAST in SELinux

By default SAST analyzers are supported in GitLab instances hosted on SELinux. Adding abefore_script in anoverridden SAST job may not work as runners hosted on SELinux have restricted permissions.