<p>GitHub has recently introduced push protection and secret scanning features for public repositories. Push protection allows developers to remove secrets from commits or bypass a block, while secret scanning detects and lists any leaked secrets. Secret scanning push protection is now mandatory for all pushes to public repositories, with users having the option to bypass the block if necessary. GitHub has already detected over 1 million leaked secrets on public repositories in the first eight weeks of 2024. Leaked secrets can pose a significant risk to reputation, revenue, and even legal exposure. In addition to the push protection feature, GitHub also offers several other security features for private repositories. The secret scanning feature identifies over 200 token types and patterns from more than 180 service providers and has recently added validity checks for popular services like AWS, Microsoft, Google, and Slack. These updates come after GitHub experienced an ongoing repo confusion attack with repositories containing obfuscated malware.</p>


Collections

GitHub has introduced push protection and secret scanning features for public repositories. Push protection allows developers to remove secrets from commits or bypass a block, while secret scanning detects and lists any leaked secrets. Leaked secrets can pose a significant risk to reputation, revenue, and legal exposure. The secret scanning feature identifies over 200 token types and patterns from more than 180 service providers and has added validity checks for popular services like AWS, Microsoft, Google, and Slack.

GitHub Introduces Default Secret Scanning Push Protection for Public Repositories