Beta: Mature GSS for Source Code
The Beta phase builds on the Experiment phase by enabling rule customization and generic secrets detection. We'll also deliver analytics comparing the Secret Detection CLI scanner's performance against Gitleaks on security projects. --- ### Phase 1: Migration & Cleanup #### [1.1 Switch Default Scanner](https://gitlab.com/gitlab-org/gitlab/-/work_items/602932) - Change ENV variable default to use CLI scanner - Update documentation to reflect new default #### [1.2 Remove Gitleaks](https://gitlab.com/gitlab-org/gitlab/-/work_items/602936) - Clean up conditional logic (remove Gitleaks branches) - Remove Gitleaks scanner from Dockerfile - Remove ENV variable and Gitleaks references from code - Remove Gitleaks package - Fix/delete any failing tests caused by Gitleaks removal - Remove Gitleaks-specific integration specs and unit tests - Verify all tests pass with CLI scanner as default #### [1.3 Enable analyzer in YAML](https://gitlab.com/gitlab-org/gitlab/-/work_items/602937) --- ### Phase 2: Enable Generic Secret Detection and Rule Exclusions #### [2.1 Generic Secret Detection](https://gitlab.com/gitlab-org/gitlab/-/work_items/602939) #### [2.2 Rule Exclusions](https://gitlab.com/gitlab-org/gitlab/-/work_items/602940) #### [2.3 Ignore Patterns and Paths](https://gitlab.com/groups/gitlab-org/-/work_items/22927) --- ### Phase 3: Telemetry #### [3.1 Apply telemetry instrumentation](https://gitlab.com/gitlab-org/gitlab/-/work_items/602941) --- ### Phase 4: Rollout - Restrict analyzer to be used by Ultimate customers only. Implement [option 1](https://gitlab.com/gitlab-org/gitlab/-/work_items/593053#note_3149073894) for Beta and ideally enhance to option 2 by GA - [Enable GSS for Secret Detection projects](https://gitlab.com/gitlab-org/gitlab/-/work_items/606245) - Roll out to gitlab-org/gitlab project - [Update pipeline SD docs to include beta GSS](https://gitlab.com/gitlab-org/gitlab/-/work_items/606360) — mark feature as "changed from experiment to beta" in documentation --- ### Phase 5: Post Rollout Validation - Performance Report: Measure scan speed, resource usage, and reliability - False Positive Analysis: Evaluate accuracy and false positive rates
epic