Secret Detection Category Direction
<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ## Secret Detection ~"group::static analysis" ~"Category:Secret Detection" Secret Detection aims to prevent that sensitive information, like passwords, authentication tokens, and private keys are unintentionally leaked as part of the repository content. It checks files and configuration to detect well-known variable names and files, and reports if there is something that is potentially risky to share. It doesn't target a specific language, but the ruleset can be applied to any project. * [Documentation](https://docs.gitlab.com/ee/user/application_security/sast/#secret-detection) * [Direction](https://about.gitlab.com/direction/secure/static-analysis/secret-detection/) * Priority: medium * Current ~"maturity::minimal" * PM Owner: @tmccaslin
epic