Secret false positive detection

  • Tier: Ultimate
  • Add-on: GitLab Duo Core, Pro, or Enterprise
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

Secret false positive detection automatically analyzes secret detection findings to identify potential false positives. Dismissing secrets that are likely not actual security risks reduces noise in your vulnerability report.

When a secret detection scan runs, GitLab Duo automatically analyzes new findings to determine the likelihood that they’re false positives. Detection is available for all secret types detected by GitLab Secret Detection.

The GitLab Duo assessment includes information about each false positive detection result:

  • Confidence score: A numerical score indicating the likelihood that the finding is a false positive.
  • Explanation: Reasons why the finding may or may not be a true positive.
  • Visual indicator: A badge in the vulnerability report that shows the assessment result.

Results are based on AI analysis and should be reviewed by security professionals. This feature requires GitLab Duo with an active subscription.

You can’t trigger this flow by mentioning, assigning, or requesting a review from its service account. The flow runs automatically after security scans complete. To run it manually, on a vulnerability page, select AI actions, then select Check for false positive.

Prerequisites

Running secret false positive detection

The flow runs automatically in the following scenarios:

  • A secret detection scan completes successfully on the default branch.
  • The scan detects new vulnerabilities. Existing vulnerabilities are not analyzed again automatically.
  • GitLab Duo features are enabled for the project or group.
  • The vulnerability meets the severity threshold. Without a triage and remediation profile, only vulnerabilities with high or critical severity are analyzed. With a profile, the profile sets the severity threshold, run mode, and other criteria.

The flow can also run automatically on other tracked branches and tags. This option is controlled by a feature flag. For more information, see tracked branches and tags.

You can also manually trigger analysis for existing vulnerabilities:

  1. In the top bar, select Search or go to and find your project.
  2. In the left sidebar, select Secure > Vulnerability report.
  3. Optional. To find a vulnerability in another tracked branch or tag, filter by tracked ref.
  4. Select the vulnerability you want to analyze.
  5. In the upper-right corner, select AI actions, then select Check for false positive.