url stringlengths 24 122 | repo_url stringlengths 60 156 | date_extracted stringdate 2025-08-13 00:00:00 2025-08-13 00:00:00 | root stringlengths 3 85 | breadcrumbs listlengths 1 6 | filename stringlengths 6 60 | stage stringclasses 33
values | group stringclasses 81
values | info stringclasses 22
values | title stringlengths 3 110 ⌀ | description stringlengths 11 359 ⌀ | clean_text stringlengths 47 3.32M | rich_text stringlengths 321 3.32M |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
https://docs.gitlab.com/user/application_security/dast/browser/configuration | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/_index.md | 2025-08-13 | doc/user/application_security/dast/browser/configuration | [
"doc",
"user",
"application_security",
"dast",
"browser",
"configuration"
] | _index.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Configuration | null |
- [Requirements](../_index.md)
- [Enabling the analyzer](enabling_the_analyzer.md)
- [Customize analyzer settings](customize_settings.md)
- [Overriding analyzer jobs](overriding_analyzer_jobs.md)
- [Available CI/CD variables](variables.md)
- [Authentication configuration](authentication.md)
- [Offline configuration](... | ---
type: reference, howto
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Configuration
breadcrumbs:
- doc
- user
- appl... |
https://docs.gitlab.com/user/application_security/dast/browser/variables | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dast/browser/variables.md | 2025-08-13 | doc/user/application_security/dast/browser/configuration | [
"doc",
"user",
"application_security",
"dast",
"browser",
"configuration"
] | variables.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Available CI/CD variables | null |
<!--
This documentation is auto generated by a script.
Please do not edit this file directly.
To edit the introductory text, modify `tooling/dast_variables/docs/templates/default.md.haml`.
To edit information about the variables, modify `lib/gitlab/security/dast_variables.rb`.
Run `bundle exec rake gitlab... | ---
type: reference, howto
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Available CI/CD variables
breadcrumbs:
- doc
-... |
https://docs.gitlab.com/user/application_security/triage | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/triage | [
"doc",
"user",
"application_security",
"triage"
] | _index.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Triage | Vulnerability separation by status. |
Triage is the second phase of the vulnerability management lifecycle: detect, triage, analyze,
remediate.
Triage is an ongoing process of evaluating each vulnerability to decide which need attention now and
which are not as critical. High-risk vulnerabilities are separated from medium or low risk threats.
It may not... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Triage
description: Vulnerability separation by status.
breadcrumbs:
-... |
https://docs.gitlab.com/user/application_security/vulnerability_management_policy_schema | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/vulnerability_management_policy_schema.md | 2025-08-13 | doc/user/application_security/policies | [
"doc",
"user",
"application_security",
"policies"
] | vulnerability_management_policy_schema.md | Security Risk Management | Security Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Vulnerability management policy schema | null |
The YAML file with vulnerability management policies consists of an array of objects matching
the vulnerability management policy schema nested under the `vulnerability_management_policy` key.
When you save a vulnerability management policy, its content is validated against the vulnerability
management policy schema... | ---
stage: Security Risk Management
group: Security Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Vulnerability management policy schema
breadcrumbs:
- doc
- user
- appli... |
https://docs.gitlab.com/user/application_security/scheduled_pipeline_execution_policies | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/scheduled_pipeline_execution_policies.md | 2025-08-13 | doc/user/application_security/policies | [
"doc",
"user",
"application_security",
"policies"
] | scheduled_pipeline_execution_policies.md | Security Risk Management | Security Policies | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Scheduled pipeline execution policies | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
- Status: Experiment
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/14147) as an experiment in GitLab 18.0 with a flag named `scheduled_pipeline_execution_policy_type` defin... | ---
stage: Security Risk Management
group: Security Policies
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Scheduled pipeline execution policies
breadcrumbs:
- doc
- user
- applic... |
https://docs.gitlab.com/user/application_security/centralized_security_policy_management | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/centralized_security_policy_management.md | 2025-08-13 | doc/user/application_security/policies | [
"doc",
"user",
"application_security",
"policies"
] | centralized_security_policy_management.md | null | null | null | null | null |
<!-- markdownlint-disable -->
This document was moved to [another location](enforcement/compliance_and_security_policy_groups.md).
<!-- This redirect file can be deleted after 2025-10-23. -->
<!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects that point to docs in... | ---
redirect_to: enforcement/compliance_and_security_policy_groups.md
remove_date: '2025-07-23'
breadcrumbs:
- doc
- user
- application_security
- policies
---
<!-- markdownlint-disable -->
This document was moved to [another location](enforcement/compliance_and_security_policy_groups.md).
<!-- This redirect file c... |
https://docs.gitlab.com/user/application_security/pipeline_execution_policies | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/pipeline_execution_policies.md | 2025-08-13 | doc/user/application_security/policies | [
"doc",
"user",
"application_security",
"policies"
] | pipeline_execution_policies.md | Security Risk Management | Security Policies | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Pipeline execution policies | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/13266) in GitLab 17.2 [with a flag](../../../administration/feature_flags/_index.md) named `pipeline_execution_policy_type`. E... | ---
stage: Security Risk Management
group: Security Policies
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Pipeline execution policies
breadcrumbs:
- doc
- user
- application_secu... |
https://docs.gitlab.com/user/application_security/security_policy_projects | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/security_policy_projects.md | 2025-08-13 | doc/user/application_security/policies | [
"doc",
"user",
"application_security",
"policies"
] | security_policy_projects.md | null | null | null | null | null |
<!-- markdownlint-disable -->
This document was moved to [another location](enforcement/security_policy_projects.md).
<!-- This redirect file can be deleted after 2025-10-23. -->
<!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects that point to docs in a different ... | ---
redirect_to: enforcement/security_policy_projects.md
remove_date: '2025-07-23'
breadcrumbs:
- doc
- user
- application_security
- policies
---
<!-- markdownlint-disable -->
This document was moved to [another location](enforcement/security_policy_projects.md).
<!-- This redirect file can be deleted after 2025-1... |
https://docs.gitlab.com/user/application_security/scan_execution_policies | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/scan_execution_policies.md | 2025-08-13 | doc/user/application_security/policies | [
"doc",
"user",
"application_security",
"policies"
] | scan_execution_policies.md | Security Risk Management | Security Policies | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Scan execution policies | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- Support for custom CI/CD variables in the scan execution policies editor [introduced](https://gitlab.com/groups/gitlab-org/-/epics/9566) in GitLab 16.2.
- Enforcement of scan execution... | ---
stage: Security Risk Management
group: Security Policies
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Scan execution policies
breadcrumbs:
- doc
- user
- application_security... |
https://docs.gitlab.com/user/application_security/policies | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/policies | [
"doc",
"user",
"application_security",
"policies"
] | _index.md | Security Risk Management | Security Policies | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Policies | Security policies, enforcement, compliance, approvals, and scans. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
Policies provide security and compliance teams with a way to enforce controls globally in
their organization.
Security teams can ensure:
- Security scanners are enforced in development team pipelines w... | ---
stage: Security Risk Management
group: Security Policies
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Policies
description: Security policies, enforcement, compliance, approv... |
https://docs.gitlab.com/user/application_security/vulnerability_management_policy | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/vulnerability_management_policy.md | 2025-08-13 | doc/user/application_security/policies | [
"doc",
"user",
"application_security",
"policies"
] | vulnerability_management_policy.md | Security Risk Management | Security Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Vulnerability management policy | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/5708) support for enforcing policies on projects in GitLab 17.7 [with a flag](../../../administration/feature_flags/_index.md)... | ---
stage: Security Risk Management
group: Security Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Vulnerability management policy
breadcrumbs:
- doc
- user
- application_... |
https://docs.gitlab.com/user/application_security/merge_request_approval_policies | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/merge_request_approval_policies.md | 2025-08-13 | doc/user/application_security/policies | [
"doc",
"user",
"application_security",
"policies"
] | merge_request_approval_policies.md | Security Risk Management | Security Policies | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Merge request approval policies | Learn how to enforce security rules in GitLab using merge request approval policies to automate scans, approvals, and compliance across your projects. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- Group-level scan result policies [introduced](https://gitlab.com/groups/gitlab-org/-/epics/7622) in GitLab 15.6.
- Scan result policies feature was renamed to merge request approval po... | ---
stage: Security Risk Management
group: Security Policies
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Learn how to enforce security rules in GitLab using merge request ... |
https://docs.gitlab.com/user/application_security/policies/enforcement | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/policies/_index.md | 2025-08-13 | doc/user/application_security/policies/enforcement | [
"doc",
"user",
"application_security",
"policies",
"enforcement"
] | _index.md | Security Risk Management | Security Policies | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Policy enforcement | Learn how to apply security policies across multiple groups and projects from a single, centralized location. |
You can create a new security policy for each project or group, but duplicating the same policy settings across multiple top-level groups can be time-consuming and present compliance challenges. Before you create a policy, you should know whether the policy should be:
- Enforced on a specific project or group.
- Enf... | ---
stage: Security Risk Management
group: Security Policies
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Learn how to apply security policies across multiple groups and pr... |
https://docs.gitlab.com/user/application_security/policies/security_policy_projects | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/policies/security_policy_projects.md | 2025-08-13 | doc/user/application_security/policies/enforcement | [
"doc",
"user",
"application_security",
"policies",
"enforcement"
] | security_policy_projects.md | Security Risk Management | Security Policies | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Security policy projects | Learn how to enforce security rules in GitLab using merge request approval policies to automate scans, approvals, and compliance across your projects. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
Security policy projects enforce policies across multiple projects. A security policy project is a
special type of project used only to contain policies. To enforce the policies contained in a
security p... | ---
stage: Security Risk Management
group: Security Policies
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Learn how to enforce security rules in GitLab using merge request ... |
https://docs.gitlab.com/user/application_security/policies/compliance_and_security_policy_groups | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/policies/compliance_and_security_policy_groups.md | 2025-08-13 | doc/user/application_security/policies/enforcement | [
"doc",
"user",
"application_security",
"policies",
"enforcement"
] | compliance_and_security_policy_groups.md | Security Risk Management | Security Policies | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Compliance and security policy groups | Learn how to apply security policies across multiple groups and projects from a single, centralized location. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab Self-Managed
- Status: Beta
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/7622) in GitLab 18.2 [with a feature flag](../../../../administration/feature_flags/_index.md) named `security_policies_csp`. Disabled by defa... | ---
stage: Security Risk Management
group: Security Policies
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Learn how to apply security policies across multiple groups and pr... |
https://docs.gitlab.com/user/application_security/configuration | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/configuration | [
"doc",
"user",
"application_security",
"configuration"
] | _index.md | null | null | null | null | null |
<!-- markdownlint-disable -->
This document was moved to [another location](../detect/security_configuration.md).
<!-- This redirect file can be deleted after <2025-08-13>. -->
<!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects that point to docs in a different pr... | ---
redirect_to: ../detect/security_configuration.md
remove_date: '2025-08-13'
breadcrumbs:
- doc
- user
- application_security
- configuration
---
<!-- markdownlint-disable -->
This document was moved to [another location](../detect/security_configuration.md).
<!-- This redirect file can be deleted after <2025-08-... |
https://docs.gitlab.com/user/application_security/security_report_validation | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/security_report_validation.md | 2025-08-13 | doc/user/application_security/detect | [
"doc",
"user",
"application_security",
"detect"
] | security_report_validation.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Security report validation | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
Security reports are validated before their content is added to the database. This prevents
ingestion of broken vulnerability data into the database. Reports that fail validation are liste... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Security report validation
breadcrumbs:
- doc
- user
- application_sec... |
https://docs.gitlab.com/user/application_security/vulnerability_scanner_maintenance | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/vulnerability_scanner_maintenance.md | 2025-08-13 | doc/user/application_security/detect | [
"doc",
"user",
"application_security",
"detect"
] | vulnerability_scanner_maintenance.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Vulnerability scanner maintenance | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
The following vulnerability scanners and their databases are regularly updated:
| Secure scanning tool | Vulnerabilities database updat... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Vulnerability scanner maintenance
breadcrumbs:
- doc
- user
- applicat... |
https://docs.gitlab.com/user/application_security/roll_out_security_scanning | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/roll_out_security_scanning.md | 2025-08-13 | doc/user/application_security/detect | [
"doc",
"user",
"application_security",
"detect"
] | roll_out_security_scanning.md | Secure | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Roll out application security testing | null |
Plan your application security testing implementation in phases to ensure a smooth transition to a
more secure development practice.
This guide helps you implement GitLab application security testing across your organization in
phases. By starting with a pilot group and gradually expanding coverage, you can minimize... | ---
stage: Secure
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Roll out application security testing
breadcrumbs:
- doc
- user
- application_security
- det... |
https://docs.gitlab.com/user/application_security/vulnerability_deduplication | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/vulnerability_deduplication.md | 2025-08-13 | doc/user/application_security/detect | [
"doc",
"user",
"application_security",
"detect"
] | vulnerability_deduplication.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Vulnerability deduplication process | Deduplication of security scanning results |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
When a pipeline contains jobs that produce multiple security reports of the same type, it is
possible that the same vulnerability finding is present in multiple reports. This duplication i... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Vulnerability deduplication process
description: Deduplication of secu... |
https://docs.gitlab.com/user/application_security/security_configuration | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/security_configuration.md | 2025-08-13 | doc/user/application_security/detect | [
"doc",
"user",
"application_security",
"detect"
] | security_configuration.md | Security Risk Management | Security Platform Management | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Security configuration | Configuration, testing, compliance, scanning, and enablement. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
You can configure security scanners for projects individually or create a scanner configuration
shared by multiple projects. Configuring each project manually gives you maximum flexibility... | ---
stage: Security Risk Management
group: Security Platform Management
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Security configuration
description: Configuration, testing, c... |
https://docs.gitlab.com/user/application_security/security_scan_results | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/security_scan_results.md | 2025-08-13 | doc/user/application_security/detect | [
"doc",
"user",
"application_security",
"detect"
] | security_scan_results.md | null | null | null | null | null |
<!-- markdownlint-disable -->
This document was moved to [another location](security_scanning_results.md).
<!-- This redirect file can be deleted after <2025-09-11>. -->
<!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects that point to docs in a different project o... | ---
redirect_to: security_scanning_results.md
remove_date: '2025-09-11'
breadcrumbs:
- doc
- user
- application_security
- detect
---
<!-- markdownlint-disable -->
This document was moved to [another location](security_scanning_results.md).
<!-- This redirect file can be deleted after <2025-09-11>. -->
<!-- Redirec... |
https://docs.gitlab.com/user/application_security/security_scanning_results | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/security_scanning_results.md | 2025-08-13 | doc/user/application_security/detect | [
"doc",
"user",
"application_security",
"detect"
] | security_scanning_results.md | Security Risk Management | Security Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Security scanning results | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/490334) in GitLab 17.9 [with a flag](../../../administration/feature_flags/_index.md) named `dependency_scanni... | ---
stage: Security Risk Management
group: Security Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Security scanning results
breadcrumbs:
- doc
- user
- application_securi... |
https://docs.gitlab.com/user/application_security/detect | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/detect | [
"doc",
"user",
"application_security",
"detect"
] | _index.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Detect | Vulnerability detection and result evaluation. |
Detect vulnerabilities in your project's repository and application's behavior throughout the
software development lifecycle.
To help you manage the risk of vulnerabilities during development:
- Security scanners run when you push code changes to a branch.
- You can view details of vulnerabilities detected in the b... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Detect
description: Vulnerability detection and result evaluation.
bre... |
https://docs.gitlab.com/user/application_security/detect/security_report_validation | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/detect/security_report_validation.md | 2025-08-13 | doc/user/application_security/detect/pipeline_secret_scanning | [
"doc",
"user",
"application_security",
"detect",
"pipeline_secret_scanning"
] | security_report_validation.md | null | null | null | null | null |
<!-- markdownlint-disable -->
This document was moved to [another location](../security_report_validation.md).
<!-- This redirect file can be deleted after <2025-09-11>. -->
<!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects that point to docs in a different proje... | ---
redirect_to: ../security_report_validation.md
remove_date: '2025-09-11'
breadcrumbs:
- doc
- user
- application_security
- detect
- pipeline_secret_scanning
---
<!-- markdownlint-disable -->
This document was moved to [another location](../security_report_validation.md).
<!-- This redirect file can be deleted a... |
https://docs.gitlab.com/user/application_security/coverage_fuzzing | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/coverage_fuzzing | [
"doc",
"user",
"application_security",
"coverage_fuzzing"
] | _index.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Coverage-guided fuzz testing (deprecated) | Coverage-guided fuzzing, random inputs, and unexpected behavior. |
<!--- start_remove The following content will be removed on remove_date: '2026-08-15' -->
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< alert type="warning" >}}
This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/517841... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Coverage-guided fuzz testing (deprecated)
description: Coverage-guide... |
https://docs.gitlab.com/user/application_security/troubleshooting | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/troubleshooting.md | 2025-08-13 | doc/user/application_security/api_fuzzing | [
"doc",
"user",
"application_security",
"api_fuzzing"
] | troubleshooting.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting API Fuzzing jobs | null |
## API Fuzzing job times out after N hours
For larger repositories, the API Fuzzing job could time out on the [small hosted runner on Linux](../../../ci/runners/hosted_runners/linux.md#machine-types-available-for-linux---x86-64), which is set per default. If this happens in your jobs, you should scale up to a [large... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting API Fuzzing jobs
breadcrumbs:
- doc
- user
- applicat... |
https://docs.gitlab.com/user/application_security/api_fuzzing | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/api_fuzzing | [
"doc",
"user",
"application_security",
"api_fuzzing"
] | _index.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Web API Fuzz Testing | Testing, security, vulnerabilities, automation, and errors. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
Web API fuzz testing passes unexpected values to API operation parameters to cause unexpected behavior
and errors in the backend. Use fuzz testing to discover bugs and potential vulnerabilities that othe... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Web API Fuzz Testing
description: Testing, security, vulnerabilities,... |
https://docs.gitlab.com/user/application_security/performance | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/performance.md | 2025-08-13 | doc/user/application_security/api_fuzzing | [
"doc",
"user",
"application_security",
"api_fuzzing"
] | performance.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Performance tuning and testing speed | null |
Security tools that perform API fuzz testing, such as API Fuzzing, perform testing by sending requests to an instance of your running application. The requests are mutated by our fuzzing engine to trigger unexpected behavior that might exist in your application. The speed of an API fuzzing test depends on the followi... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Performance tuning and testing speed
breadcrumbs:
- doc
- user
- appl... |
https://docs.gitlab.com/user/application_security/create_har_files | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/create_har_files.md | 2025-08-13 | doc/user/application_security/api_fuzzing | [
"doc",
"user",
"application_security",
"api_fuzzing"
] | create_har_files.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Create HAR Files | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
HTTP Archive (HAR) format files are an industry standard for exchanging information about HTTP
requests and HTTP responses. A HAR file's content is JSON formatted, containing browser interactions
with a ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Create HAR Files
breadcrumbs:
- doc
- user
- application_security
- a... |
https://docs.gitlab.com/user/application_security/api_fuzzing/overriding_analyzer_jobs | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_fuzzing/overriding_analyzer_jobs.md | 2025-08-13 | doc/user/application_security/api_fuzzing/configuration | [
"doc",
"user",
"application_security",
"api_fuzzing",
"configuration"
] | overriding_analyzer_jobs.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Overriding API Fuzzing jobs | null |
To override a job definition, (for example, change properties like `variables`, `dependencies`, or [`rules`](../../../../ci/yaml/_index.md#rules)),
declare a job with the same name as the DAST job to override. Place this new job after the template
inclusion and specify any additional keys under it. For example, this ... | ---
type: reference, howto
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Overriding API Fuzzing jobs
breadcrumbs:
- doc... |
https://docs.gitlab.com/user/application_security/api_fuzzing/variables | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_fuzzing/variables.md | 2025-08-13 | doc/user/application_security/api_fuzzing/configuration | [
"doc",
"user",
"application_security",
"api_fuzzing",
"configuration"
] | variables.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Available CI/CD variables | null |
| CI/CD variable | Description |
|-------------------------------------------------------------|-------------|
| `SECURE_ANALYZERS_PREFIX` | Specify the Docker registry base address from which to download the analyzer. |
| `FUZZAPI_VERSION... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Available CI/CD variables
breadcrumbs:
- doc
- user
- application_sec... |
https://docs.gitlab.com/user/application_security/api_fuzzing/configuration | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_fuzzing/_index.md | 2025-08-13 | doc/user/application_security/api_fuzzing/configuration | [
"doc",
"user",
"application_security",
"api_fuzzing",
"configuration"
] | _index.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Configuration | null |
- [Requirements](../_index.md)
- [Enabling the analyzer](enabling_the_analyzer.md)
- [Customize analyzer settings](customizing_analyzer_settings.md)
- [Overriding analyzer jobs](overriding_analyzer_jobs.md)
- [Available CI/CD variables](variables.md)
- [Offline configuration](offline_configuration.md)
| ---
type: reference, howto
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Configuration
breadcrumbs:
- doc
- user
- appl... |
https://docs.gitlab.com/user/application_security/api_fuzzing/enabling_the_analyzer | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_fuzzing/enabling_the_analyzer.md | 2025-08-13 | doc/user/application_security/api_fuzzing/configuration | [
"doc",
"user",
"application_security",
"api_fuzzing",
"configuration"
] | enabling_the_analyzer.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Enabling the analyzer | null |
Prerequisites:
- One of the following web API types:
- REST API
- SOAP
- GraphQL
- Form bodies, JSON, or XML
- One of the following assets to provide APIs to test:
- OpenAPI v2 or v3 API definition
- HTTP Archive (HAR) of API requests to test
- Postman Collection v2.0 or v2.1
{{< alert type="warning... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Enabling the analyzer
breadcrumbs:
- doc
- user
- application_securit... |
https://docs.gitlab.com/user/application_security/api_fuzzing/customizing_analyzer_settings | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_fuzzing/customizing_analyzer_settings.md | 2025-08-13 | doc/user/application_security/api_fuzzing/configuration | [
"doc",
"user",
"application_security",
"api_fuzzing",
"configuration"
] | customizing_analyzer_settings.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Customizing analyzer settings | null |
The API fuzzing behavior can be changed through CI/CD variables.
The API fuzzing configuration files must be in your repository's `.gitlab` directory.
{{< alert type="warning" >}}
All customization of GitLab security scanning tools should be tested in a merge request before
merging these changes to the default bra... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Customizing analyzer settings
breadcrumbs:
- doc
- user
- application... |
https://docs.gitlab.com/user/application_security/api_fuzzing/requirements | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_fuzzing/requirements.md | 2025-08-13 | doc/user/application_security/api_fuzzing/configuration | [
"doc",
"user",
"application_security",
"api_fuzzing",
"configuration"
] | requirements.md | null | null | null | null | null |
<!-- markdownlint-disable -->
This document was moved to [another location](../_index.md#getting-started).
<!-- This redirect file can be deleted after <2025-09-17>. -->
<!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects that point to docs in a different project o... | ---
redirect_to: ../_index.md
remove_date: '2025-09-17'
breadcrumbs:
- doc
- user
- application_security
- api_fuzzing
- configuration
---
<!-- markdownlint-disable -->
This document was moved to [another location](../_index.md#getting-started).
<!-- This redirect file can be deleted after <2025-09-17>. -->
<!-- Re... |
https://docs.gitlab.com/user/application_security/api_fuzzing/offline_configuration | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_fuzzing/offline_configuration.md | 2025-08-13 | doc/user/application_security/api_fuzzing/configuration | [
"doc",
"user",
"application_security",
"api_fuzzing",
"configuration"
] | offline_configuration.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Offline configuration | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
For instances in an environment with limited, restricted, or intermittent access to external resources through the internet, some adjustments are required for the Web API Fuzz testing job to successfully run.
Steps:
1. Host the Doc... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Offline configuration
breadcrumbs:
- doc
- user
- application_securit... |
https://docs.gitlab.com/user/application_security/vulnerability_archival | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/vulnerability_archival | [
"doc",
"user",
"application_security",
"vulnerability_archival"
] | _index.md | Security Risk Management | Security Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Vulnerability archival | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- Introduced in GitLab 18.0 [with a flag](../../../administration/feature_flags/_index.md) named `vulnerability_archival`. Disabled by default.
{{< /history >}}
{{< alert type="flag" >... | ---
stage: Security Risk Management
group: Security Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Vulnerability archival
breadcrumbs:
- doc
- user
- application_security
... |
https://docs.gitlab.com/user/application_security/gitlab_advisory_database | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/gitlab_advisory_database | [
"doc",
"user",
"application_security",
"gitlab_advisory_database"
] | _index.md | Application Security Testing | Vulnerability Research | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab Advisory Database | Security advisories, vulnerabilities, dependencies, database, and updates. |
The [GitLab Advisory Database](https://gitlab.com/gitlab-org/security-products/gemnasium-db) serves as a repository for security advisories related to software dependencies. It is updated on an hourly basis with the latest security advisories.
The database is an essential component of both [Dependency Scanning](../d... | ---
stage: Application Security Testing
group: Vulnerability Research
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: GitLab Advisory Database
description: Security advisories, vuln... |
https://docs.gitlab.com/user/application_security/exclusions | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/exclusions.md | 2025-08-13 | doc/user/application_security/secret_detection | [
"doc",
"user",
"application_security",
"secret_detection"
] | exclusions.md | Application Security Testing | Secret Detection | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Secret detection exclusions | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
- Status: Experiment
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/14878) as an [experiment](../../../policy/development_stages_support.md) in GitLab 17.5 [with a flag](../... | ---
stage: Application Security Testing
group: Secret Detection
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Secret detection exclusions
breadcrumbs:
- doc
- user
- application_s... |
https://docs.gitlab.com/user/application_security/remove_secrets_tutorial | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/remove_secrets_tutorial.md | 2025-08-13 | doc/user/application_security/secret_detection | [
"doc",
"user",
"application_security",
"secret_detection"
] | remove_secrets_tutorial.md | Application Security Testing | Secret Detection | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Tutorial: Remove a secret from your commits | null |
If your application uses external resources, you usually need to authenticate your
application with a **secret**, like a token or key. If a secret is pushed to a
remote repository, anyone with access to the repository can impersonate you or your
application. If you accidentally commit a secret, you can still remove i... | ---
stage: Application Security Testing
group: Secret Detection
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: 'Tutorial: Remove a secret from your commits'
breadcrumbs:
- doc
- us... |
https://docs.gitlab.com/user/application_security/detected_secrets | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/detected_secrets.md | 2025-08-13 | doc/user/application_security/secret_detection | [
"doc",
"user",
"application_security",
"secret_detection"
] | detected_secrets.md | Application Security Testing | Secret Detection | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Detected secrets | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
This table lists the secrets detected by:
- Pipeline secret detection
- Client-side secret detection
- Secret push protection
Secret detection rules are updated in the [default ruleset](... | ---
stage: Application Security Testing
group: Secret Detection
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Detected secrets
breadcrumbs:
- doc
- user
- application_security
- s... |
https://docs.gitlab.com/user/application_security/secret_detection | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/secret_detection | [
"doc",
"user",
"application_security",
"secret_detection"
] | _index.md | Application Security Testing | Secret Detection | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Secret detection | Detection, prevention, monitoring, storage, revocation, and reporting. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
Your application might use external resources, including a CI/CD
service, a database, or external storage. Access to these resources
requires authentication, usually using static methods l... | ---
stage: Application Security Testing
group: Secret Detection
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Secret detection
description: Detection, prevention, monitoring, stor... |
https://docs.gitlab.com/user/application_security/automatic_response | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/automatic_response.md | 2025-08-13 | doc/user/application_security/secret_detection | [
"doc",
"user",
"application_security",
"secret_detection"
] | automatic_response.md | Application Security Testing | Secret Detection | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Automatic response to leaked secrets | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
GitLab Secret Detection automatically responds when it finds certain types of leaked secrets.
Automatic responses can:
- Automatically revoke the secret.
- Notify the partner that issued the secret. The... | ---
stage: Application Security Testing
group: Secret Detection
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Automatic response to leaked secrets
breadcrumbs:
- doc
- user
- appl... |
https://docs.gitlab.com/user/application_security/push_protection_tutorial | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/push_protection_tutorial.md | 2025-08-13 | doc/user/application_security/secret_detection | [
"doc",
"user",
"application_security",
"secret_detection"
] | push_protection_tutorial.md | Application Security Testing | Secret Detection | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Tutorial: Protect your project with secret push protection | null |
If your application uses external resources, you usually need to authenticate your
application with a **secret**, like a token or key. If a secret is pushed to a
remote repository, anyone with access to the repository can impersonate you or your
application.
With secret push protection, if GitLab detects a secret in... | ---
stage: Application Security Testing
group: Secret Detection
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: 'Tutorial: Protect your project with secret push protection'
breadcru... |
https://docs.gitlab.com/user/application_security/secret_detection/client | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/secret_detection/_index.md | 2025-08-13 | doc/user/application_security/secret_detection/client | [
"doc",
"user",
"application_security",
"secret_detection",
"client"
] | _index.md | Application Security Testing | Secret Detection | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Client-side secret detection | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/368434) in GitLab 15.11.
- Detection of personal access tokens with a custom prefix was [introduced](https://g... | ---
stage: Application Security Testing
group: Secret Detection
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Client-side secret detection
breadcrumbs:
- doc
- user
- application_... |
https://docs.gitlab.com/user/application_security/secret_detection/pipeline | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/secret_detection/_index.md | 2025-08-13 | doc/user/application_security/secret_detection/pipeline | [
"doc",
"user",
"application_security",
"secret_detection",
"pipeline"
] | _index.md | Application Security Testing | Secret Detection | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Pipeline secret detection | null |
<!-- markdownlint-disable MD025 -->
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
Pipeline secret detection scans files after they are committed to a Git repository and pushed to GitLab.
After you [enable pipeline secret detection](... | ---
stage: Application Security Testing
group: Secret Detection
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Pipeline secret detection
breadcrumbs:
- doc
- user
- application_sec... |
https://docs.gitlab.com/user/application_security/secret_detection/tutorial | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/secret_detection/tutorial.md | 2025-08-13 | doc/user/application_security/secret_detection/pipeline | [
"doc",
"user",
"application_security",
"secret_detection",
"pipeline"
] | tutorial.md | Application Security Testing | Secret Detection | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Tutorial: Protect your project with pipeline secret detection | null |
<!-- vale gitlab_base.FutureTense = NO -->
If your application uses external resources, you usually need to authenticate your application with a secret,
like a token or key. If a secret is pushed to a remote repository, anyone with access to the repository can impersonate
you or your application.
Pipeline secret de... | ---
stage: Application Security Testing
group: Secret Detection
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: 'Tutorial: Protect your project with pipeline secret detection'
bread... |
https://docs.gitlab.com/user/application_security/secret_detection/configure | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/secret_detection/configure.md | 2025-08-13 | doc/user/application_security/secret_detection/pipeline | [
"doc",
"user",
"application_security",
"secret_detection",
"pipeline"
] | configure.md | Application Security Testing | Secret Detection | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Customize pipeline secret detection | null |
<!-- markdownlint-disable MD025 -->
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
Depending on your [subscription tier](_index.md#availability) and configuration method, you can change how pipeline secret detection works.
[Customize... | ---
stage: Application Security Testing
group: Secret Detection
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Customize pipeline secret detection
breadcrumbs:
- doc
- user
- appli... |
https://docs.gitlab.com/user/application_security/secret_detection/custom_rulesets_schema | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/secret_detection/custom_rulesets_schema.md | 2025-08-13 | doc/user/application_security/secret_detection/pipeline | [
"doc",
"user",
"application_security",
"secret_detection",
"pipeline"
] | custom_rulesets_schema.md | Application Security Testing | Secret Detection | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Custom rulesets schema | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
You can use [different kinds of ruleset customizations](configure.md#customize-analyzer-rulesets)
to customize the behavior of pipeline secret detection.
## Schema
Customization of pipeline secret dete... | ---
stage: Application Security Testing
group: Secret Detection
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Custom rulesets schema
breadcrumbs:
- doc
- user
- application_securi... |
https://docs.gitlab.com/user/application_security/secret_detection/secret_push_protection | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/secret_detection/_index.md | 2025-08-13 | doc/user/application_security/secret_detection/secret_push_protection | [
"doc",
"user",
"application_security",
"secret_detection",
"secret_push_protection"
] | _index.md | Application Security Testing | Secret Detection | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Secret push protection | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/11439) in GitLab 16.7 as an [experiment](../../../../policy/development_stages_support.md) for GitLab Dedicated customers.
- [... | ---
stage: Application Security Testing
group: Secret Detection
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Secret push protection
breadcrumbs:
- doc
- user
- application_securi... |
https://docs.gitlab.com/user/application_security/troubleshooting_dependency_scanning | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/troubleshooting_dependency_scanning.md | 2025-08-13 | doc/user/application_security/dependency_scanning | [
"doc",
"user",
"application_security",
"dependency_scanning"
] | troubleshooting_dependency_scanning.md | Application Security Testing | Composition Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting Dependency Scanning | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
When working with dependency scanning, you might encounter the following issues.
## Debug-level logging
Debug-level logging can help when troubleshooting. For details, see
[debug-level l... | ---
stage: Application Security Testing
group: Composition Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting Dependency Scanning
breadcrumbs:
- doc
- user
- a... |
https://docs.gitlab.com/user/application_security/static_reachability | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/static_reachability.md | 2025-08-13 | doc/user/application_security/dependency_scanning | [
"doc",
"user",
"application_security",
"dependency_scanning"
] | static_reachability.md | Application Security Testing | Composition Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Static reachability analysis | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
- Status: Beta
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/14177) as an [experiment](../../../policy/development_stages_support.md) in GitLab 17.5.
- [Changed](https://gi... | ---
stage: Application Security Testing
group: Composition Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Static reachability analysis
breadcrumbs:
- doc
- user
- applicat... |
https://docs.gitlab.com/user/application_security/experiment_libbehave_dependency | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/experiment_libbehave_dependency.md | 2025-08-13 | doc/user/application_security/dependency_scanning | [
"doc",
"user",
"application_security",
"dependency_scanning"
] | experiment_libbehave_dependency.md | Application Security Testing | Composition Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Analyze dependency for behaviors | Libbehave scans new dependencies added in merge requests for risky behaviors and assigns each behavior a risk score. Results are shown in the job output, merge request comments, and job artifacts. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
- Status: Experiment
{{< /details >}}
Libbehave is an experimental feature that scans your dependencies during merge request pipelines to
identify newly added libraries and their potentially risky behaviors. While tradit... | ---
stage: Application Security Testing
group: Composition Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Analyze dependency for behaviors
description: Libbehave scans new... |
https://docs.gitlab.com/user/application_security/migration_guide_to_sbom_based_scans | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/migration_guide_to_sbom_based_scans.md | 2025-08-13 | doc/user/application_security/dependency_scanning | [
"doc",
"user",
"application_security",
"dependency_scanning"
] | migration_guide_to_sbom_based_scans.md | Application Security Testing | Composition Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Migrating to Dependency Scanning using SBOM | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- The legacy [Dependency Scanning feature based on the Gemnasium analyzer](_index.md) was [deprecated](../../../update/deprecations.md#dependency-scanning-upgrades-to-the-gitlab-sbom-vul... | ---
stage: Application Security Testing
group: Composition Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Migrating to Dependency Scanning using SBOM
breadcrumbs:
- doc
- ... |
https://docs.gitlab.com/user/application_security/dependency_scanning | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/dependency_scanning | [
"doc",
"user",
"application_security",
"dependency_scanning"
] | _index.md | Application Security Testing | Composition Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Dependency Scanning | Vulnerabilities, remediation, configuration, analyzers, and reports. |
<style>
table.ds-table tr:nth-child(even) {
background-color: transparent;
}
table.ds-table td {
border-left: 1px solid #dbdbdb;
border-right: 1px solid #dbdbdb;
border-bottom: 1px solid #dbdbdb;
}
table.ds-table tr td:first-child {
border-left: 0;
}
table.ds-table tr td:last-child {
border... | ---
stage: Application Security Testing
group: Composition Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Dependency Scanning
description: Vulnerabilities, remediation, co... |
https://docs.gitlab.com/user/application_security/dependency_scanning/dependency_scanning_sbom | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/dependency_scanning/_index.md | 2025-08-13 | doc/user/application_security/dependency_scanning/dependency_scanning_sbom | [
"doc",
"user",
"application_security",
"dependency_scanning",
"dependency_scanning_sbom"
] | _index.md | Application Security Testing | Composition Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Dependency scanning by using SBOM | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
- Status: Beta
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/395692) in GitLab 17.1 and officially released in GitLab 17.3 with a flag named `dependency_scanning_using_sbo... | ---
stage: Application Security Testing
group: Composition Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Dependency scanning by using SBOM
breadcrumbs:
- doc
- user
- app... |
https://docs.gitlab.com/user/application_security/offline_deployments | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/offline_deployments | [
"doc",
"user",
"application_security",
"offline_deployments"
] | _index.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Offline environments | Offline security scanning and resolving vulnerabilities. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
{{< /details >}}
{{< alert type="note" >}}
To set up an offline environment, you must receive an [opt-out exemption of cloud licensing](https://about.gitlab.com/pricing/licensing-faq/cloud-licensing/#offline-cloud-licensing) prior to ... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Offline environments
description: Offline security scanning and resolv... |
https://docs.gitlab.com/user/application_security/security_inventory | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/security_inventory | [
"doc",
"user",
"application_security",
"security_inventory"
] | _index.md | Security Risk Management | Security Platform Management | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Security inventory | Group-level visibility of assets, scanner coverage, and vulnerabilities. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
- Status: Beta
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/16484) in GitLab 18.2 with a flag named `security_inventory_dashboard`. Enabled by default. This feature is in ... | ---
stage: Security Risk Management
group: Security Platform Management
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Security inventory
description: Group-level visibility of ass... |
https://docs.gitlab.com/user/application_security/vulnerability_report | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/vulnerability_report | [
"doc",
"user",
"application_security",
"vulnerability_report"
] | _index.md | Security Risk Management | Security Insights | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Vulnerability report | Filtering, grouping, exporting, and manual addition. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- Vulnerability Resolution activity icon [introduced](https://gitlab.com/groups/gitlab-org/-/epics/15036) in GitLab 17.5 with a flag named [`vulnerability_report_vr_badge`](https://gitla... | ---
stage: Security Risk Management
group: Security Insights
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Vulnerability report
description: Filtering, grouping, exporting, and ma... |
https://docs.gitlab.com/user/application_security/pipeline | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/pipeline.md | 2025-08-13 | doc/user/application_security/vulnerability_report | [
"doc",
"user",
"application_security",
"vulnerability_report"
] | pipeline.md | null | null | null | null | null |
<!-- markdownlint-disable -->
This document was moved to [another location](../detect/security_scanning_results.md).
<!-- This redirect file can be deleted after <2025-09-11>. -->
<!-- Redirects that point to other docs in the same project expire in three months. -->
<!-- Redirects that point to docs in a different... | ---
redirect_to: ../detect/security_scanning_results.md
remove_date: '2025-09-11'
breadcrumbs:
- doc
- user
- application_security
- vulnerability_report
---
<!-- markdownlint-disable -->
This document was moved to [another location](../detect/security_scanning_results.md).
<!-- This redirect file can be deleted af... |
https://docs.gitlab.com/user/application_security/gitlab_advanced_sast | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/gitlab_advanced_sast.md | 2025-08-13 | doc/user/application_security/sast | [
"doc",
"user",
"application_security",
"sast"
] | gitlab_advanced_sast.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab Advanced SAST | GitLab Advanced SAST uses cross-file, cross-function taint analysis to detect complex vulnerabilities with high accuracy. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- Introduced in GitLab 17.1 as an [experiment](../../../policy/development_stages_support.md) for Python.
- Support for Go and Java added in 17.2.
- [Changed](https://gitlab.com/gitlab-o... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: GitLab Advanced SAST uses cross-file, cross-function taint analy... |
https://docs.gitlab.com/user/application_security/sast | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/sast | [
"doc",
"user",
"application_security",
"sast"
] | _index.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Static Application Security Testing (SAST) | Scanning, configuration, analyzers, vulnerabilities, reporting, customization, and integration. |
<style>
table.sast-table tr:nth-child(even) {
background-color: transparent;
}
table.sast-table td {
border-left: 1px solid #dbdbdb;
border-right: 1px solid #dbdbdb;
border-bottom: 1px solid #dbdbdb;
}
table.sast-table tr td:first-child {
border-left: 0;
}
table.sast-table tr td:last-child {
... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Static Application Security Testing (SAST)
description: Scanning, conf... |
https://docs.gitlab.com/user/application_security/evaluation_guide | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/evaluation_guide.md | 2025-08-13 | doc/user/application_security/sast | [
"doc",
"user",
"application_security",
"sast"
] | evaluation_guide.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Evaluate GitLab SAST | Learn how to evaluate GitLab SAST by selecting a test codebase, configuring scans, interpreting results, and comparing features with other security tools. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
You might choose to evaluate GitLab SAST before using it in your organization.
Consider the following guidance as you plan and conduct your evaluation.
## Important concepts
GitLab SAST is designed to ... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Learn how to evaluate GitLab SAST by selecting a test codebase, ... |
https://docs.gitlab.com/user/application_security/troubleshooting | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/troubleshooting.md | 2025-08-13 | doc/user/application_security/sast | [
"doc",
"user",
"application_security",
"sast"
] | troubleshooting.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting SAST | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
The following troubleshooting scenarios have been collected from customer support cases. If you
experience a problem not addressed here, or the information here does not fix your problem, ... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting SAST
breadcrumbs:
- doc
- user
- application_security
... |
https://docs.gitlab.com/user/application_security/customize_rulesets | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/customize_rulesets.md | 2025-08-13 | doc/user/application_security/sast | [
"doc",
"user",
"application_security",
"sast"
] | customize_rulesets.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Customize rulesets | Customize SAST analyzer rules in GitLab by disabling, overriding, or replacing predefined rules. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Enabled](https://gitlab.com/gitlab-org/security-products/analyzers/ruleset/-/merge_requests/18) support for specifying ambiguous passthrough refs in GitLab 16.2.
{{< /history >}}
Yo... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: Customize SAST analyzer rules in GitLab by disabling, overriding... |
https://docs.gitlab.com/user/application_security/analyzers | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/analyzers.md | 2025-08-13 | doc/user/application_security/sast | [
"doc",
"user",
"application_security",
"sast"
] | analyzers.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | SAST analyzers | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Moved](https://gitlab.com/groups/gitlab-org/-/epics/2098) from GitLab Ultimate to GitLab Free in 13.3.
{{< /history >}}
Static Application Security Testing (SAST) use... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: SAST analyzers
breadcrumbs:
- doc
- user
- application_security
- sast... |
https://docs.gitlab.com/user/application_security/rules | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/rules.md | 2025-08-13 | doc/user/application_security/sast | [
"doc",
"user",
"application_security",
"sast"
] | rules.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | SAST rules | null |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
GitLab SAST uses a set of [analyzers](analyzers.md) to scan code for potential vulnerabilities.
It automatically chooses which analyzers to run based on which programming languages are fou... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: SAST rules
breadcrumbs:
- doc
- user
- application_security
- sast
---... |
https://docs.gitlab.com/user/application_security/advanced_sast_coverage | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/advanced_sast_coverage.md | 2025-08-13 | doc/user/application_security/sast | [
"doc",
"user",
"application_security",
"sast"
] | advanced_sast_coverage.md | Application Security Testing | Static Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | GitLab Advanced SAST CWE coverage | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
[GitLab Advanced SAST](gitlab_advanced_sast.md) finds many types of potential security vulnerabilities in code written in [supported languages](gitlab_advanced_sast.md#supported-languages).
GitLab assig... | ---
stage: Application Security Testing
group: Static Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: GitLab Advanced SAST CWE coverage
breadcrumbs:
- doc
- user
- applicat... |
https://docs.gitlab.com/user/application_security/container_scanning | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/container_scanning | [
"doc",
"user",
"application_security",
"container_scanning"
] | _index.md | Application Security Testing | Composition Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Container Scanning | Image vulnerability scanning, configuration, customization, and reporting. |
{{< details >}}
- Tier: Free, Premium, Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Changed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/86092) the major analyzer version from `4` to `5` in GitLab 15.0.
- [Moved](https://gitlab.com/gitlab-org... | ---
stage: Application Security Testing
group: Composition Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Container Scanning
description: Image vulnerability scanning, con... |
https://docs.gitlab.com/user/application_security/api_security | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/api_security | [
"doc",
"user",
"application_security",
"api_security"
] | _index.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | API Security | Protection, analysis, testing, scanning, and discovery. |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
API Security refers to the measures taken to secure and protect web Application Programming Interfaces (APIs) from unauthorized access, misuse, and attacks.
APIs are a crucial component of modern applica... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: API Security
description: Protection, analysis, testing, scanning, an... |
https://docs.gitlab.com/user/application_security/api_security/api_discovery | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security/_index.md | 2025-08-13 | doc/user/application_security/api_security/api_discovery | [
"doc",
"user",
"application_security",
"api_security",
"api_discovery"
] | _index.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | API Discovery | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/9302) in GitLab 15.9. The API Discovery feature is in [beta](../../../../policy/development_stages_support.md).
{{< /history ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: API Discovery
breadcrumbs:
- doc
- user
- application_security
- api_... |
https://docs.gitlab.com/user/application_security/api_security_testing | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/_index.md | 2025-08-13 | doc/user/application_security/api_security_testing | [
"doc",
"user",
"application_security",
"api_security_testing"
] | _index.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | API security testing analyzer | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Changed](https://gitlab.com/groups/gitlab-org/-/epics/4254) in GitLab 15.6 to the default analyzer for on-demand API security testing scans.
- [Renamed](https://gitlab.com/gitlab-org/... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: API security testing analyzer
breadcrumbs:
- doc
- user
- application... |
https://docs.gitlab.com/user/application_security/performance | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/performance.md | 2025-08-13 | doc/user/application_security/api_security_testing | [
"doc",
"user",
"application_security",
"api_security_testing"
] | performance.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Performance tuning and testing speed | null |
Security tools that perform dynamic analysis testing, such as API security testing, perform testing by sending requests to an instance of your running application. The requests are engineered to test for specific vulnerabilities that might exist in your application. The speed of a dynamic analysis test depends on the... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Performance tuning and testing speed
breadcrumbs:
- doc
- user
- appl... |
https://docs.gitlab.com/user/application_security/troubleshooting | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/troubleshooting.md | 2025-08-13 | doc/user/application_security/api_security_testing | [
"doc",
"user",
"application_security",
"api_security_testing"
] | troubleshooting.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Troubleshooting API security testing jobs | null |
## API security testing job times out after N hours
For larger repositories, the API security testing job could time out on the [small hosted runner on Linux](../../../ci/runners/hosted_runners/linux.md#machine-types-available-for-linux---x86-64), which is set per default. If this happens in your jobs, you should sc... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Troubleshooting API security testing jobs
breadcrumbs:
- doc
- user
-... |
https://docs.gitlab.com/user/application_security/api_security_testing/open_redirect_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/open_redirect_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | open_redirect_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Open redirect | null |
## Description
Identify open redirects and determine if they can be abused by attackers.
## Remediation
Unvalidated redirects and forwards are possible when a web application accepts untrusted input that could cause the web application to redirect the request to a URL contained within untrusted input. By modifying... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Open redirect
breadcrumbs:
- doc
- user
- application_security
- api_... |
https://docs.gitlab.com/user/application_security/api_security_testing/html_injection_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/html_injection_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | html_injection_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | HTML injection | null |
## Description
Check for XSS via HTML injection into all fields that support strings. This includes portions of the HTTP request such as path, query, headers and also body parameters such as XML fields, JSON fields, etc. Detection is performed by monitoring responses for the injected value in to known HTML enabled f... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: HTML injection
breadcrumbs:
- doc
- user
- application_security
- api... |
https://docs.gitlab.com/user/application_security/api_security_testing/authentication_token_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/authentication_token_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | authentication_token_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Authentication token | null |
## Description
Perform various authentication token checks such as removing the token or changing to an invalid value.
## Remediation
API tokens must be unpredictable (random enough) to prevent guessing attacks, where an attacker is able to guess or predict a valid API Token through statistical analysis techniques... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Authentication token
breadcrumbs:
- doc
- user
- application_security... |
https://docs.gitlab.com/user/application_security/api_security_testing/path_traversal_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/path_traversal_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | path_traversal_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Path traversal | null |
## Description
Many file operations are intended to take place within a restricted directory. By using special elements such as `..` and `/` separators, attackers can escape outside of the restricted location to access files or directories that are elsewhere on the system. One of the most common special elements is ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Path traversal
breadcrumbs:
- doc
- user
- application_security
- api... |
https://docs.gitlab.com/user/application_security/api_security_testing/cors_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/cors_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | cors_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | CORS | null |
## Description
Check for CORS misconfiguration including overly permissive white-lists of accepted Origin headers or failure to validate Origin header. Also checks for allowing credentials on potentially invalid or dangerous Origins and missing headers that could potentially result in cache poisoning.
## Remediatio... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: CORS
breadcrumbs:
- doc
- user
- application_security
- api_security_... |
https://docs.gitlab.com/user/application_security/api_security_testing/os_command_injection_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/os_command_injection_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | os_command_injection_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | OS command injection | null |
## Description
Check for OS command injection vulnerabilities. An OS command injection attack consists of insertion or "injection" of an OS command via the input data from the client to the application.
A successful OS command injection exploit can run arbitrary commands. This allows an attacker the ability to read,... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: OS command injection
breadcrumbs:
- doc
- user
- application_security... |
https://docs.gitlab.com/user/application_security/api_security_testing/xml_injection_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/xml_injection_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | xml_injection_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | XML Injection Check | null |
## Description
Check for XML serialization/injection vulnerabilities.
## Remediation
XML Injection is an attack technique used to manipulate or compromise the logic of an XML application or service. The injection of unintended XML content and/or structures into an XML message can alter the intend logic of the appl... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: XML Injection Check
breadcrumbs:
- doc
- user
- application_security
... |
https://docs.gitlab.com/user/application_security/api_security_testing/checks | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/_index.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | _index.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | API security testing vulnerability checks | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Renamed](https://gitlab.com/gitlab-org/gitlab/-/issues/457449) from **DAST API vulnerability checks** to **API security testing vulnerability checks** in GitLab 17.0.
{{< /history >}... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: API security testing vulnerability checks
breadcrumbs:
- doc
- user
-... |
https://docs.gitlab.com/user/application_security/api_security_testing/json_injection_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/json_injection_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | json_injection_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | JSON injection | null |
## Description
Check for JSON serialization/injection vulnerabilities.
## Remediation
JSON injection is an attack technique used to manipulate or compromise the logic of a JSON application or service. The injection of unintended JSON content and/or structures into an JSON message can alter the intend logic of the ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: JSON injection
breadcrumbs:
- doc
- user
- application_security
- api... |
https://docs.gitlab.com/user/application_security/api_security_testing/sensitive_information_disclosure_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/sensitive_information_disclosure_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | sensitive_information_disclosure_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Sensitive information disclosure | null |
## Description
Sensitive information disclosure check. This includes credit card numbers, health records, personal information, etc.
## Remediation
Sensitive information leakage is an application weakness where an application
reveals sensitive, user-specific data. Sensitive data may be used by an attacker
to explo... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Sensitive information disclosure
breadcrumbs:
- doc
- user
- applicat... |
https://docs.gitlab.com/user/application_security/api_security_testing/sql_injection_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/sql_injection_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | sql_injection_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | SQL injection | null |
## Description
Check for SQL and NoSQL injection vulnerabilities. A SQL injection attack
consists of insertion or "injection" of a SQL query via the input data from the
client to the application. A successful SQL injection exploit can read sensitive
data from the database, modify database data (Insert/Update/Delete)... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: SQL injection
breadcrumbs:
- doc
- user
- application_security
- api_... |
https://docs.gitlab.com/user/application_security/api_security_testing/insecure_http_methods_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/insecure_http_methods_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | insecure_http_methods_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Insecure HTTP methods | null |
## Description
Checks to see if HTTP methods like OPTIONS and TRACE are enabled on any target endpoints.
## Remediation
The resource tested supports the OPTIONS HTTP method. Usually, this is considered a security misconfiguration as it leaks supported HTTP methods leading to information gathering about a specific ... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Insecure HTTP methods
breadcrumbs:
- doc
- user
- application_securit... |
https://docs.gitlab.com/user/application_security/api_security_testing/framework_debug_mode_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/framework_debug_mode_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | framework_debug_mode_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Framework debug mode | null |
## Description
Checks to see if debug mode is enabled in various frameworks such as Flask and ASP.NET. This check has a low false positive rate.
## Remediation
The Flask or ASP .NET framework was identified with debug mode enabled. This allows an attacker the ability to download any file on the file system and oth... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Framework debug mode
breadcrumbs:
- doc
- user
- application_security... |
https://docs.gitlab.com/user/application_security/api_security_testing/dns_rebinding_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/dns_rebinding_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | dns_rebinding_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | DNS rebinding | null |
## Description
Check for DNS rebinding. This check verifies that the host checks that the HOST header of the request exists and matches the expected name of the host to avoid attacks via malicious DNS entries.
## Remediation
DNS rebinding allows a malicious host to spoof or redirect a request to an alternate IP ad... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: DNS rebinding
breadcrumbs:
- doc
- user
- application_security
- api_... |
https://docs.gitlab.com/user/application_security/api_security_testing/application_information_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/application_information_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | application_information_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Application information disclosure | null |
## Description
Application information disclosure check. This includes information such as version numbers, database error messages, stack traces.
## Remediation
Application information disclosure is an application weakness where an application reveals sensitive data, such as technical details of the web applicati... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Application information disclosure
breadcrumbs:
- doc
- user
- applic... |
https://docs.gitlab.com/user/application_security/api_security_testing/cleartext_authentication_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/cleartext_authentication_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | cleartext_authentication_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Cleartext authentication | null |
## Description
This check looks for cleartext authentication such as HTTP Basic auth with no-TLS.
## Remediation
Authentication credentials are transported via unencrypted channel (HTTP). This exposes the transmitted credentials to any attacker who can monitor (sniff) the network traffic during transmission. Sensi... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Cleartext authentication
breadcrumbs:
- doc
- user
- application_secu... |
https://docs.gitlab.com/user/application_security/api_security_testing/heartbleed_open_ssl_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/heartbleed_open_ssl_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | heartbleed_open_ssl_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Heartbleed OpenSSL vulnerability | null |
## Description
Check for Heartbleed OpenSSL vulnerability.
## Remediation
The Heartbleed vulnerability is a serious bug in the popular OpenSSL cryptographic library. OpenSSL is used to encrypt and decrypt communications and secure the Internet traffic. This vulnerability allows the attacker to steal protected info... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Heartbleed OpenSSL vulnerability
breadcrumbs:
- doc
- user
- applicat... |
https://docs.gitlab.com/user/application_security/api_security_testing/tls_server_configuration_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/tls_server_configuration_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | tls_server_configuration_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | TLS server configuration | null |
## Description
Check for various TLS Server configuration issues. Checks TLS versions, hmacs, ciphers and compression algs supported by server.
## Remediation
Insufficient transport layer protection allows communication to be exposed to untrusted third-parties, providing an attack vector to compromise a web applic... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: TLS server configuration
breadcrumbs:
- doc
- user
- application_secu... |
https://docs.gitlab.com/user/application_security/api_security_testing/xml_external_entity_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/xml_external_entity_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | xml_external_entity_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | XML external entity | null |
## Description
Check for XML DTD processing vulnerabilities.
## Remediation
XML external entity Attack is a type of attack against an application that parses XML input. This attack occurs when XML input containing a reference to an external entity is processed by a weakly configured XML parser. This attack may lea... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: XML external entity
breadcrumbs:
- doc
- user
- application_security
... |
https://docs.gitlab.com/user/application_security/api_security_testing/json_hijacking_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/json_hijacking_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | json_hijacking_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | JSON hijacking | null |
## Description
Checks for JSON data potentially vulnerable to hijacking. This check looks for a GET request that returns a JSON array, which could potentially be hijacked and read by a malicious website.
## Remediation
JSON hijacking allows an attacker to send a GET request via a malicious web site or similar atta... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: JSON hijacking
breadcrumbs:
- doc
- user
- application_security
- api... |
https://docs.gitlab.com/user/application_security/api_security_testing/session_cookie_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/session_cookie_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | session_cookie_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Session cookie | null |
## Description
Verify session cookie has correct flags and expiration.
## Remediation
HTTP is a stateless protocol, so websites commonly use cookies to store
session IDs that uniquely identify a user from request to request. Consequently,
each session ID's confidentiality must be maintained in order to prevent
mul... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Session cookie
breadcrumbs:
- doc
- user
- application_security
- api... |
https://docs.gitlab.com/user/application_security/api_security_testing/shellshock_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/shellshock_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | shellshock_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Shellshock | null |
## Description
Check for Shellshock vulnerabilities.
## Remediation
Shellshock vulnerability takes advantage of a bug in BASH, in which, BASH incorrectly executes trailing commands when it imports a function definition stored into an environment variable. Any environment which allows defining BASH environmental va... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Shellshock
breadcrumbs:
- doc
- user
- application_security
- api_sec... |
https://docs.gitlab.com/user/application_security/api_security_testing/sensitive_file_disclosure_check | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/sensitive_file_disclosure_check.md | 2025-08-13 | doc/user/application_security/api_security_testing/checks | [
"doc",
"user",
"application_security",
"api_security_testing",
"checks"
] | sensitive_file_disclosure_check.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Sensitive file disclosure | null |
## Description
Check for sensitive file disclosure. This check looks for files that may contain sensitive information. Examples include .htaccess, .htpasswd, .bash_history, etc.
## Remediation
Information leakage is an application weakness where an application reveals sensitive data, such as technical details of t... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Sensitive file disclosure
breadcrumbs:
- doc
- user
- application_sec... |
https://docs.gitlab.com/user/application_security/api_security_testing/overriding_analyzer_jobs | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/overriding_analyzer_jobs.md | 2025-08-13 | doc/user/application_security/api_security_testing/configuration | [
"doc",
"user",
"application_security",
"api_security_testing",
"configuration"
] | overriding_analyzer_jobs.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Overriding API security testing jobs | null |
To override a job definition, (for example, change properties like `variables`, `dependencies`, or [`rules`](../../../../ci/yaml/_index.md#rules)),
declare a job with the same name as the DAST job to override. Place this new job after the template
inclusion and specify any additional keys under it. For example, this ... | ---
type: reference, howto
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Overriding API security testing jobs
breadcrum... |
https://docs.gitlab.com/user/application_security/api_security_testing/variables | https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/user/application_security/api_security_testing/variables.md | 2025-08-13 | doc/user/application_security/api_security_testing/configuration | [
"doc",
"user",
"application_security",
"api_security_testing",
"configuration"
] | variables.md | Application Security Testing | Dynamic Analysis | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments | Available CI/CD variables and configuration files | null |
{{< details >}}
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
{{< /details >}}
{{< history >}}
- [Changed](https://gitlab.com/gitlab-org/gitlab/-/issues/450445) template name from `DAST-API.gitlab-ci.yml` to `API-Security.gitlab-ci.yml` and variable prefixed from `DAST_API_` to `A... | ---
stage: Application Security Testing
group: Dynamic Analysis
info: To determine the technical writer assigned to the Stage/Group associated with
this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
title: Available CI/CD variables and configuration files
breadcrumbs:
- doc
... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.