You 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 Unterstützte Scanmuster für Secrets.
Custom 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.
Next steps
To start using custom patterns, see Definieren von benutzerdefinierten Mustern für die Geheimnisüberprüfung.