<!--This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!--Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues.--> <!--Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.--> <!--Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/--> Currently, you can enable [**validity checks for Secret Detection**](https://docs.gitlab.com/user/application_security/vulnerabilities/validity_check): * On a project level: > 1. In the left sidebar, select **Secure** \> **Security configuration**. > 2. Under **Pipeline Secret Detection**, turn on the **Validity checks** toggle. * On group level, using a [GraphQL Mutation](https://docs.gitlab.com/api/graphql/reference/#mutationsetgroupvaliditychecks) This feature request proposes to introduce an **instance-level admin toggle** that controls the enabling of **validity checks for Secret Detection** across the entire GitLab instance.