![]() ![]() The Secret Detection analyzer includes Gitleaks checks. It runs regardless of your app’s programming language. Secret Detection is performed by a specific analyzerĭuring the secret-detection job. In GitLab 14.0, Secret Detection jobs secret_detection_default_branch and secret_detection were consolidated into one job, secret_detection.If you’re using GitLab 13.0 or earlier and SAST is enabled, then Secret Detection is already enabled. In GitLab 13.1, Secret Detection was split from the SAST configuration into its own CI/CD template.Interaction with Vulnerabilities Access to Security Dashboard Configuration View identified secrets in the pipelines’ Security tab See the breakdown below for more details.ĭifferent features are available in different GitLab tiers,Ĭonfigure Secret Detection Scanners Customize Secret Detection Settings View JSON Report Presentation of JSON Report in merge request However not all features are available on every tier. To make Secret Detection available to as many customers as possible, we have enabled it for all GitLab tiers. Making Secret Detection available to all GitLab tiers See troubleshooting information for details. If you use your own runners, make sure the Docker version installed
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |