{"meta":{"title":"Concepts for secret security","intro":"Learn core concepts for GitHub's secret security features.","product":"Security and code quality","breadcrumbs":[{"href":"/en/enterprise-cloud@latest/code-security","title":"Security and code quality"},{"href":"/en/enterprise-cloud@latest/code-security/concepts","title":"Concepts"},{"href":"/en/enterprise-cloud@latest/code-security/concepts/secret-security","title":"Secret security"}],"documentType":"subcategory"},"body":"# Concepts for secret security\n\nLearn core concepts for GitHub's secret security features.\n\n## Links\n\n* [Secret leakage risks](/en/enterprise-cloud@latest/code-security/concepts/secret-security/secret-leakage-risks)\n\n  Secrets like API keys, passwords, and tokens committed to repositories can be exploited by unauthorized users, creating security, compliance, and financial risk to your organization.\n\n* [Secret scanning](/en/enterprise-cloud@latest/code-security/concepts/secret-security/secret-scanning)\n\n  Prevent fraudulent use of your secrets by automatically detecting exposed credentials before they can be exploited.\n\n* [Public monitoring for secret scanning](/en/enterprise-cloud@latest/code-security/concepts/secret-security/public-monitoring)\n\n  Public monitoring detects credentials leaked by your enterprise members in public repositories across GitHub, giving you visibility into secret exposure beyond your enterprise's boundaries.\n\n* [Push protection](/en/enterprise-cloud@latest/code-security/concepts/secret-security/push-protection)\n\n  Secure your secrets by stopping them from ever reaching your repository with push protection.\n\n* [Secret security with GitHub](/en/enterprise-cloud@latest/code-security/concepts/secret-security/secret-security-with-github)\n\n  Learn how GitHub's security tools can help you identify, remediate, and prevent secret leaks.\n\n* [About secret scanning alerts](/en/enterprise-cloud@latest/code-security/concepts/secret-security/about-alerts)\n\n  Learn about the different types of secret scanning alerts.\n\n* [Custom patterns](/en/enterprise-cloud@latest/code-security/concepts/secret-security/custom-patterns)\n\n  Detect secret types specific to your organization with custom patterns.\n\n* [Validity checks](/en/enterprise-cloud@latest/code-security/concepts/secret-security/validity-checks)\n\n  Validity checks and extended metadata checks help you prioritize remediation of exposed credentials that pose immediate security risks.\n\n* [Delegated bypass for push protection](/en/enterprise-cloud@latest/code-security/concepts/secret-security/delegated-bypass)\n\n  Maintain your secret security while unblocking trusted actors with delegated bypass for push protection.\n\n* [Bypass requests for push protection](/en/enterprise-cloud@latest/code-security/concepts/secret-security/bypass-requests)\n\n  Learn how bypass requests work when push protection blocks commits containing secrets.\n\n* [Secret scanning for partners](/en/enterprise-cloud@latest/code-security/concepts/secret-security/secret-scanning-for-partners)\n\n  When secret scanning detects authentication details for a service provider in a public repository on GitHub, an alert is sent directly to the provider. This allows service providers who are GitHub partners to promptly take action to secure their systems.\n\n* [GitHub secret types](/en/enterprise-cloud@latest/code-security/concepts/secret-security/secret-types)\n\n  Learn about the different types of secrets used by GitHub.\n\n* [Secret scanning push protection metrics](/en/enterprise-cloud@latest/code-security/concepts/secret-security/push-protection-metrics)\n\n  Understand push protection's performance across your organizations.\n\n* [Push protection from the command line](/en/enterprise-cloud@latest/code-security/concepts/secret-security/command-line-push-protection)\n\n  Understand how GitHub uses push protection to prevent secret leaks from the command line.\n\n* [Working with push protection and the GitHub MCP server](/en/enterprise-cloud@latest/code-security/concepts/secret-security/push-protection-and-the-github-mcp-server)\n\n  Learn how you are protected from leaking secrets during interactions with the GitHub MCP server, and how to bypass a push protection block if you need to.\n\n* [Working with push protection from the REST API](/en/enterprise-cloud@latest/code-security/concepts/secret-security/push-protection-from-the-rest-api)\n\n  Learn your options for unblocking your push to GitHub using the REST API if secret scanning detects a secret in the content of your API request."}