Introducing secret scanning validity checks for major cloud services
Blog post from GitHub
GitHub has enhanced its secret scanning capabilities by making secret scanning and push protection free for public repositories, aiming to prevent credential leaks in open-source projects. This initiative includes the introduction of validity checks for GitHub tokens, which streamline the remediation process by allowing users to quickly determine if a token is active via the user interface, thus prioritizing remediation efforts more efficiently. The validity checks have now been extended to include tokens from AWS, Microsoft, Google, and Slack, addressing some of the most common secrets detected across GitHub repositories. This feature is part of a broader effort to expand token validation support through GitHub's secret scanning partner program, with periodic and manual verification options available to enterprise or organization owners and repository administrators. The enhancements aim to provide faster and more efficient triaging of alerts, with ongoing updates and community feedback encouraged through GitHub's Code Security community discussion and documentation resources.