{"meta":{"title":"Custom patterns","intro":"Detect secret types specific to your organization with custom patterns.","product":"Security and code quality","breadcrumbs":[{"href":"/en/code-security","title":"Security and code quality"},{"href":"/en/code-security/concepts","title":"Concepts"},{"href":"/en/code-security/concepts/secret-security","title":"Secret security"},{"href":"/en/code-security/concepts/secret-security/custom-patterns","title":"Custom patterns"}],"documentType":"article"},"body":"# Custom patterns\n\nDetect secret types specific to your organization with custom patterns.\n\nYou can define custom patterns to identify secrets that are not detected by the default patterns supported by secret scanning. For example, you might have a secret pattern that is internal to your organization. For a list of supported secrets and service providers, see [Supported secret scanning patterns](/en/code-security/secret-scanning/introduction/supported-secret-scanning-patterns).\n\nCustom patterns for secret scanning are defined as regular expressions, and can be created at the enterprise, organization, or repository level. You can also enable push protection for custom patterns, stopping those secrets from ever reaching your repository.\n\n## Next steps\n\nTo start using custom patterns, see [Defining custom patterns for secret scanning](/en/code-security/how-tos/secure-your-secrets/customize-leak-detection/defining-custom-patterns-for-secret-scanning)."}