Secret Scanning Validity Checks Now Available for GitHub Enterprise Cloud with Data Residency
Allison details GitHub’s rollout of validity checks for secret scanning on Enterprise Cloud with data residency, providing a significant security upgrade for DevOps teams and security practitioners.
Secret Scanning Validity Checks Now Available for GitHub Enterprise Cloud with Data Residency
GitHub has expanded platform support for security features on its Enterprise Cloud with data residency, as well as the upcoming release of Enterprise Server. This rollout introduces several key security enhancements for organizations leveraging GitHub at scale.
Key Enhancements
- Validity Checks for Secret Protection:
- Now available for GitHub Advanced Security customers on GitHub Enterprise Cloud with data residency.
- Once enabled on a repository, GitHub will automatically verify secrets related to alerts for supported token types. See supported token patterns.
- Enterprise Server Support:
- Validity checks are planned for a future release of GitHub Enterprise Server. Details will be published in the GitHub changelog upon release.
Additional Validators
GitHub has expanded the scope of secret scanning by adding support for new token types:
| Provider | Pattern | Validity Check |
|---|---|---|
| Typeform | typeform_personal_access_token |
✓ |
| SSLMate | sslmate_api_key and sslmate2_api_key |
✓ |
Organizations can benefit from enhanced security and compliance, particularly when using GitHub in regulated industries or geographies that require data residency. These updates provide more automation and assurance when detecting and validating exposed secrets in code repositories.
For more details and a list of all supported token types, refer to the GitHub documentation.
This post appeared first on “The GitHub Blog”. Read the entire article here