Add setting to enable/disable AI false positive detection
Summary
Implement a setting that allows users to enable or disable AI-powered false positive detection for SAST vulnerabilities. This provides users with control over when the AI analysis is performed and allows them to opt-out if desired.
Problem to Solve
Users need the ability to control whether AI false positive detection is enabled for their projects or groups. Some users may want to disable this feature due to:
- Privacy concerns about sending vulnerability data to AI services
- Performance considerations
- Preference for manual vulnerability triage
- Compliance requirements
Proposal
Implement a setting that allows users to:
- Project-level Setting: Enable/disable FP detection at the project level
- Group-level Setting: Enable/disable FP detection at the group level (inheritable by projects)
- Default Behavior: Define appropriate default state (enabled/disabled)
- Setting Inheritance: Projects inherit group settings unless explicitly overridden
- UI Integration: Clear indication when FP detection is disabled
Potential Solution
There are two potential options to how we might want to implement this:
Option 1 (preferred option): Use the existing GitLab Duo settings as a way to implement the configuration, which helps it to be consistent with other AI similar features, code suggestions, duo chats, maybe others.
| Role | Settings |
|---|---|
|
Admins |
|
|
Group Owners |
|
|
Project Maintainers |
|
Option 2: Introduce a new AI setting configuration at the project level in the UI
- On the left sidebar, select Search or go to and find your project.
- Select Secure > Security configuration.
- Select AI Security Features card
- Instead the card, Sec Ai features are turned on by default for the project;
- They will need to turn it off per project that doesn't need/want to use the AI features provided, or is needed to stop/manage the use of credits for usage billing
Related Issues
- Parent Epic: &18977
- Design Issue: gitlab-org/gitlab#563032